win win spiral model advantages and disadvantages[click here to know more]

Win-Win Spiral Model

The Win-Win Spiral Model is a model of process based on Theory W' which is a management theory and approach "based on making winners of all the system's key stakeholder as necessary and sufficient for the project success."

"The original spiral model uses a cyclic approach to develop increasingly detailed elaborations of a software system's definition, culminating in incremental releases of the system's operational capability.

The win-win spiral process explicitly emphasizes continuous collaborative involvement of a software product's stakeholder in it's early definition and development stages.

win-win spiral model

Features of win-win spiral process model



  • It provides an explicit set of goals for collaborative software definition and development.
  • It embeds collaborative activities explicitly within a robust life-cycle model the spiral model.


The resulting process uses the "Theory W" of win-win model approach to converge on a system's next level objectives, constraints, and alternatives.

The win-win spiral model process uses two steps:

1. Identifying the system's stakeholders and their win conditions.
2. Reconciling win conditions through negotiations to arrive at a mutually satisfactory set of objectives, constraints, and alternatives for the next level.

There are following seven steps in a win-win spiral model.


Step 1. Identifying the next-level stakeholders.

  • In this step you identify the next level stakeholders.
  • These are the peoples who you need to make happy after the current phase of development.


Step 2. Identify stakeholder's win conditions

  • In this step, the stakeholders' "goals and concerns" or objectives are documented.


Step 3. Reconcile win conditions. Establish next level objectives, constraints, alternatives.

  • In this step, it is made sure that win conditions are consistent and can begins planning for the next level.


Step 4. Evaluate product and process alternatives, resolves the risks.

  • In this step, the current project is examined carefully to consider alternatives and to resolves any risks that may have been found.
  • If they have not been found but later cause problems, blame someone no longer on the project.


Step 5. Defining next level of product and process, Including partitions


  • At this step,  the next level is further defined and may partition the system into subsystem that can be developed in parallel cycles.
  • This is particularly useful if a system can be broken into easy part and hard part because you can delegate the hard part of someone else.


Step 6. Validate Product and Process Definition

  • Most of the peoples don't like this step because of the "evil" connotations of the step 6, especially when repeated, but unfortunately it is an necessary step.


Step 7. Review Commitment

  • In this final step, all the work is reviewed that's been done so far and make sure that the product is still feasible and worthwhile.

Post a comment

0 Comments