I find this really interesting: In talking with many people who actually do make Software in the last years (not only talk about it *g*) I think I detected that many have a growing problem with the term "requirement". Martin Fowler sums it up greatly in his recent blog post. He makes a strong point in saying that the understanding that many people have about "requirements" is actually still very much driven by a waterfall-like understanding of the software engineering process.
Observation comes in...
- Seed: bring in a new feature, idea; probably only to a subset of customers, probably in variations for different customers
- Select: select the successful variations
- Amplify: eventually amplify the successful ideas and bring more of that sort
... and back to the Waterfall