10 Evolutionary Project Management Principles - Evo Principle 9

November 16, 2008 | Author: PM Hut | Filed under: Agile Project Management, Project Management Best Practices

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

Evo leads to early, and on-time, product delivery - both because of selected early priority delivery, and because we learn to get things right early.

Discussion

Evo allow us consciously to select things for early and complete delivery. These things cannot be ‘late’. We also can select high risk items for early Evo steps because then we have time to deal with the risks, and to remove them from future steps.

Example

  • Obtaining early market and technical feedback results in increased feature evolution and customer satisfaction.
    • but this increases schedule estimation error.
    • but early market feedback increases bugginess.
  • High-level architecture specification provides for more flexible product development measured in terms of feature evolution.
  • Evolutionary development allows flexibility in product development allowing the project team to make requirements, functional changes and add code for new features late into the project.
  • Design reviews identify any consistency problems earlier than the later testing activities that require a running product.
  • Running regression tests, each time developers check changed or new code into the project build, improves product quality.
  • If the project team has enough time for final product stabilization phase, then they have completed the project on time. This results in lower schedule estimation error.

The project team may decide to spend time on final product stabilization versus making late design changes that incorporate market and technical feedback. This may result in increased % of original features implemented in the final product.

Hypothesis supported by research on HP Projects

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