EasyWinWin Report Re-evaluation

Due Date 11/27/2002 at 2:00pm (no grade for late submission)

· Check the WinWin Tree according to the following structures given below:

- The structure of the WinWin Tree should be:

o Win Condition: Win condition number. [Section in XY chart] Win condition statement [taxonomy item(s)]

|__ Agreement: Agreement number. Agreement statement [who agreed - date] [related win condition(s)] [taxonomy item(s)]

o Win Condition: Win condition number. [Section in XY chart] Win condition statement [taxonomy item(s)]

|__Issue: Issue number. Issue statement [who raised] [related win condition(s)] [taxonomy item(s)]

|__ Option: Option number. Option statement [who resolved] [related option(s)] [taxonomy item(s)]

|__ Agreement: Agreement number. Agreement statement [who agreed - date] [related win condition(s) and option(s)] [taxonomy item(s)]

- Each Win Condition should be identified with its related taxonomy element, e.g.

i. W1 [LHF] The project should be done in 12 weeks. [Taxonomy 1.1]

- The role of the stakeholder who identified the Issue should be included EXPLICITLY (see page 108 in the EasyWinWin Guideline). Identify the Win Condition(s) involved in this issue. Identify the related taxonomy element.

i. I6 The schedule is very short and there are many requirements. [DEVELOPER] [W1, W10] [Taxonomy 1.1, 2.1]

- Identify each Option with the role of the stakeholder who comes up with the option (see page 112 in the EasyWinWin Guideline). Identify the Option(s) involved in this issue. Identify the related taxonomy element.

i. O8 The updates can be made on a weekly basis. [CUSTOMER] [I10] [Taxonomy 2.1]

- All Agreements to Win Conditions should identify the participating stakeholders and the date; the win conditions covered, and the applicable option if there is one; and the related taxonomy element.

i. A2 The system will be designed to provide weekly statistics. [ARCHITECT, DEVELOPER, CUSTOMER - 09/10/2000] [W9, O8] [Taxonomy 2.1]

Example structure of the WinWin Tool:

1. Application Capabilities

…

1.2 W5 [IWH] The program should have an expert system [Taxonomy 2.1]

1.2.1 I1 Complex if to be implemented in full. [DEVELOPER] [W5] [Taxonomy 2.1]

1.2.1.1 O1 Use predetermined models through program codes [CUSTOMER, DEVELOPER] [I1] [Taxonomy 2.1]

1.2.1.1.1 A2 An expert system will be implemented, but the models will be predefined [DEVELOPER, CUSTOMER, USER - 09/28/2000] [W5, O1] [Taxonomy 2.1]

…

1.7 W9 [MLR] Rendering a graph on the fly [Taxonomy 2.1]

1.3.1 A3 If time permits, we will include rendering graphs on the fly [CUSTOMER, DEVELOPER - 09/28/2000] [W9] [Taxonomy 2.1]

…

3. Level of Service

3.1 W4 [LHF] Secure system, only secure connections [Taxonomy 4.2]

3.1.1 A14 The system will be secure preventing any access points from being created [CUSTOMER, ARCHITECT- 09/28/2000] [W4] [Taxonomy 4.2]

…

Important Notes and instructions what to SUBMIT:

- You will use the EasyWinWin process guide to help you in completing this assignment.

- Each winwin artifact has a unique number, which is incremental for each different winwin artifact type (win condition, issue, option and agreement). Do not use the same identification number for the issue, option or agreement as it is in the win condition. You have to increment the number when a new winwin artifact type occurs for the same winwin artifact type.

- Please make the modifications (corrections and additions) into the missing steps of your EasyWinWin data directly using the EasyWinWin tool. You DON’T have to submit a hardcopy for this assignment. The assignment is going to be re-graded by checking the data in your team negotiation folder under the negotiation leaders account.

- After you are done, send an email to Hasan Kitapci (hkitapci@sunset.usc.edu), with your team number and name and the username and password of the negotiation leader who is the owner of the negotiation folder.

- If you have any questions, please contact Hasan Kitapci (hkitapci@sunset.usc.edu).