Flow Of Stakes In Software Project Management

Having said all this, where does it leave the software project manager? In order to have a "happy project" a software project manager should respect the flow of the stakes, as illustrated in the diagram below, and must ensure that stakes go "full cycle".

Uhhr, well, let's describe this "flow" in a few steps:

Links of Interest
3 Steps Towards Becoming An Agile Project Manager


  • Stakeholders have stakes

  • Stakeholders communicate their stakes by means of requirements to the process or the product

  • Project management should make every stakeholder a winner by accepting and inventing requirements that keep satisfying the stakes of individual stakeholders and are not conflicting with the general process and product

  • Project management should give continuos feedback on the state of the stakes

  • Based upon the feedback, the requirements might change. In this way, a new cycle starts.

You must know this flow!

Other posts in Introduction

July 22nd, 2007 | Category: Introduction | View Comments

View Comments

  1. Fifth Discipline: What To Do When All Your Projects Are Failing — Project Shrink March 2nd, 2009 2:01 pm

    [...] Mental models provide us with lenses to view the world. If we look through a depressing lens, we see depressing things and behave accordingly. By using different mental models, or mindsets, we can understand other people better, by adopting assumptions of the other person. Our Need For Metaphors Explaining PM Approaches Dealing With Cultural Differences In Projects Introducing The Fish Pond Flow Of Stakes In Software Project Management [...]

  2. Why Soft Skills Are Essential To Project Managers | Project Shrink July 27th, 2010 8:21 am

    [...] Or just follow the “Flow Of Stakes”: [...]

Leave a reply