when a ProJect fails (to meet the expectations of the Gold Owner or Goal Donor?)

more likely in Big Project

What's the appropriate criteria for defining Success/FailUre of a project (Feed Back after the fact)?

• the traditional widespread-failure stories define success as on-time, on-budget, on-spec

  • but as we move toward widespread Agile Software Development (need to form term that's not software-specific), the illusion of Fixed Price And Scope Contract games becomes ridiculous.

• I think the key baseline requirement is: "If I went back in time to the start of this project, would I (a) do the project, or (b) Just Say No?" (And "why?") (This question should be answered by lots of people, but esp the Gold Owner.)

  • Doing the project differently is not an option in this game.

  • Doing a very different project is also not (explicitly) on the list, because people tend to compare the actual outcome of the real project to the ideal other-project.

• If the previous test is passed, then you start adding other metrics...

  • could realistic changes in actions/decisions have increased the net value created via the project

  • what did we learn that will increase our future ability to create value?

  • ???

Sean Mc Grath thinks is just the stooge.

User Options Recent Changes Help Page