10 Evolutionary Project Management Principles – Evo Principle 5 (#6 in the series 10 Evolutionary Project Management (Evo) Principles)
By Tom Gilb
Evo is holistic systems engineering – all necessary aspects of the system must be complete and correct – and delivered to a real stakeholder environment – it is not only about programming – it is about customer satisfaction
Evo forces us to plan and complete all aspects of the product that are necessary for all stakeholders’ satisfaction. We have to go beyond software ‘functionality’; and even beyond software quality and performance. We have to consider the hardware, the training, the documentation, the testing, the help desks, the fixing process, the marketing and customer information, future extensions – anything that stands in the way of success if not properly dealt with.
Evo forces us to deal with these ultimate realities because every Evo step is an attempt to hand over our total product to a real environment – not usually the final ‘all-customers’ environment – but as real as we can make it before we finally hand over. The environment is like field trials – except we do them early (the first week of the project) and frequently (maybe 50 times in a row). If we are going to get some bad news, we’d like it as early as possible! We can also deal with a wide variety of internal and external stakeholders, one by one, on their special turf (like integration testing, bug fixing, translations, actual user learning).
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.