10 Evolutionary Project Management Principles - Evo Principle 4

October 23, 2008 | Author: PM Hut | Filed under: Agile Project Management

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

We cannot know all the right requirements in advance, but we can discover them more quickly by attempts to deliver real value to real stakeholders

Discussion

It would be great if we could settle all requirements before we designed and implemented products.

But, all experience says we cannot.

Partly this is because the customers and other stakeholders do not consciously know that they need a particular requirement. Maybe they were never asked. Maybe they don’t have enough experience with the new system. Maybe they did not realize that they should articulate this as a requirement.

But the moment a real stakeholder is dealing with a real product, they can directly and indirectly voice their needs, especially if we are listening and analyzing carefully.

So – it is ‘better late than never’. Evo tries as early as possible to find out about requirements we never had specified. We try to find out in practice, with real stakeholders {internal staff like testers, documentation writers, users, customers}. Evo step delivery is in fact a powerful method for requirements analysis as well as requirements management.

Example

  Development Team Users
Monday
  • System test and release version n
  • Decide what to do for version n+1
  • Design version n+1
 
Tuesday
  • Develop code
  • Use version n and give feedback
Wednesday
  • Develop code
  • Meet with users to discuss action
    taken regarding feedback from
    version n-1
  • Meet with developers to discuss action taken regarding feedback from version n-1
Thursday
  • Complete code
 
Friday
  • Test and build version n+1
  • Analyze feedback from version n and decide what to do next
 

Elaine L. May and Barbara A. Zimmer, 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