[Click for larger view]
“By starting design early, the team managed to paint a picture of what the system might actually do, and get important feedback that made the requirements better.”
Sounds Agile to me 
[HT: EvantageConsulting]
Requirements-Driven Development For The Lose
7 Responses to “Requirements-Driven Development For The Lose”
Trackbacks/Pingbacks
-
-
August 2, 2011
[...] Requirements-Driven Development For The Lose | Agile Scout すんげえ顔だｗ Requirements-Driven Development For The Lose | Agile Scout http://agilescout.com/?p=4439… Source: agilescout.com [...]
-
-
August 3, 2011
[...] to me [HT: EvantageConsulting] You just finished reading Requirements-Driven Development For… Read more… Categories: Agile Share | Related [...]
The final process is definitely much better than the start, for sure. I prefer, however, to build the detailed requirements as the project progresses (see http://wp.me/p1H2AQ-6b). As such, I would not rely on too much while still prototyping.
Also, I typically build the early prototyping and feedback into the first few iterations. The focus there being early validation that the concept will work and that the chosen technologies will work together. It also provides a way to measure velocity on a newly composed team before the development starts.
Great points here.
I am going to refer to this simply put agile picture…thanks!
Simple enough, with emoticons!
Hi Peter,
Agile is based on two main principles: iterative and incremental. But I don’t see this in Development box, which is the heart of the process!
Thanks,
Ahmed.