10 Evolutionary Project Management Principles - Evo Principle 3

October 19, 2008 | Author: PM Hut | Filed under: Agile Project Management, Project Management Best Practices

10 Evolutionary Project Management Principles - Evo Principle 3 (#4 in the series 10 Evolutionary Project Management (Evo) Principles)
By Tom Gilb

Evo steps deliver the specified requirements, evolutionarily

Discussion

Evo is NOT about doing a series of tasks to build a system. That is ‘incremental delivery’.

Evo is about two related ideas:

  • deliver real value to real stakeholders (value is defined by the requirements of those stakeholders)
  • and because we have tried to deliver real value, then at each step we should measure the results!
    • exactly what value was delivered?
    • exactly what did it cost compared to estimates?
    • did the stakeholder really get satisfied?
    • did new requirements get discovered?
    • did the technology work as expected?

And – what are you going to do NOW (next Evo step) about all this.

Evo is about feedback and learning. It is a ‘plan -> do -> study -> act cycle’ (Deming).

One important consequence of this is that the formal requirements are very important. If they are not unambiguously clear, if benefits and costs are not quantified – then we cannot use Evo in the rational engineering mode that is the expected mode of use.

Are your most critical improvement requirements and objectives quantified, so you can engineer your system – or are they stated without numbers?

Example

“In parallel with the development activities of the team, selected users or customers of the system are working with and providing feedback on the release from the previous cycle. This feedback is used to adjust the plan for the following cycles.”

Todd Cotton, HP Journal August 1996.

Tom Gilb is a freelance consultant, teacher and author serving clients mainly in Europe and the US. He has books in print: “Competitive Engineering”, “Principles of Software Engineering Management” and “Software Inspection”. He specializes in software engineering, systems engineering, and technical management. He resides in Norway and London. His most recent papers, book manuscripts and slides are available on www.gilb.com.

Share this article:
  • Digg
  • del.icio.us
  • Facebook
  • Google
  • blogmarks
  • LinkedIn
  • Reddit
  • StumbleUpon
  • TwitThis
  • Yahoo! Buzz

Related Articles

No comments yet.

feel free to leave a comment

Comment Guidelines: Basic XHTML is allowed (a href, strong, em, code). All line breaks and paragraphs are automatically generated. Off-topic or inappropriate comments will be edited or deleted. Email addresses will never be published. Keep it PG-13 people!

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

All fields marked with " * " are required.

Project Management Categories