WinWin Negotiations

For the WinWin negotiation, there will be the following stakeholder roles:

Project Manager: The team member responsible for the Life Cycle Plan will represent concerns, such as schedule, personnel shortfalls, resources, risk management, etc...
(Prototypist and Architect) or (Developer1 and Developer2): The team members responsible for the System and Software Architecture and the Prototype will represent developer concerns, such as use of familiar packages, stability of requirements, availability of support tools, and technically challenging approaches
Customer : The team member responsible for the Feasibility Rationale will represent customer concerns, such as the need to develop an Initial Operational Capability in one semester, limited budgets for support tools, and low-risk technical approaches
User (can have more than one user, e.g., User1, User2): The team members responsible for the Operational Concept and System Requirements will work with their designated user-community representative to represent user concerns, such as particular multimedia access features, fast response time, friendly user interface, high reliability, and flexibility of requirements

For each WinWin negotation, the WinWin data should be stored in the following directory structure (adapt as necessary, e.g., if there are User1 and User2 stakeholders). We need to have the windb file for each stakeholder. Teams who do not keep the windb file for each stakeholder will be penalized.

          /WINWIN/ ........... WINWIN Data
                 /Customer/... The customer's Windb file
                 /User/....... The user's windb file
                 /Prototypist/ The prototypist's windb file
                 /Architect/.. The architect's windb file
                 /Manager/.... The project manager's windb file

For additional information, refer to the Guidelines