| 10 Evo Principles by Tom Gilb | Overview | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | Info |
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 .
| Example: | |
Development team |
Users |
|
| Monday |
|
|
| Tuesday |
|
|
| Wednesday |
|
|
| Thursday |
|
|
| Friday |
|
|
| Elaine L. May and Barbara A. Zimmer, HP Journal August 1996. | ||