10 Evolutionary Project Management Principles – Evo Principle 8 (#9 in the series 10 Evolutionary Project Management (Evo) Principles)
By Tom Gilb
Evo is about learning from hard experience, as fast as we can – what really works, and what really delivers value Evo is a discipline to make us confront our problems early – but which allows us to progress quickly when we really provably have got it right.
Evo may seem ‘slow’. But it is the fastest known way to get the right stuff delivered. This is especially true when you are pushing the envelope with new competitive ideas that are not yet proven in practice. Evo becomes your workbench and experimental lab. ‘Bill and Dave’ are curious to see how things are going between each Evo step. They expect working systems on the workbench continuously.
One of the criteria commonly used in setting priorities during this initial planning activity is: Features with greatest risk. The most common criterion used for prioritizing the development phase implementation cycles is risk. When adopting object technology, many teams are concerned that the system performance will not be adequate. Ease-of-use is another common risk for a project. The use scenarios that will provide the best insight into areas of greatest risk should be scheduled for implementation as early as possible.
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.