Requirements-Driven Development For The Lose

[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]

Author: peter

Peter Saddington is an Organizational Scientist and Certified Scrum Trainer. You can find him at

7 thoughts on “Requirements-Driven Development For The Lose”

  1. 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 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.

  2. Pingback: Requirements-Driven Development For The Lose | Agile | Syngu
  3. 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!

Leave a Reply

Your email address will not be published. Required fields are marked *