Fulfilling Requirements
From AgileOpenNorthwest
Contents |
Fulfilling Requirements in the Long Run
Hosted by: Bruce Winegarden
This was a workshop session aimed at understanding how can we can extend Agile Development by leveraging knowledge, expertise and practices of related disciplines, to address real concerns of larger enterprises?
When I talk to people about Agile Development, I often hear, “Our customers demand that we tell them what new features we are going to deliver a year or two from now.” Their perception is, “Agile Development won’t really work for us.”
Our challenge was to figure out how Agile Development can outperform traditional development approaches while working with the talented people in other specialized disciplines that many larger organizations have to offer.
Premise
Agile Development doesn’t have all the answers
In this session we identified other disciplines and started mapping the Interactions and Responsibilities between Development and other disciplines.
- Interactions – shared topics that 2 or more roles need to talk about
- Responsibilities – specific value added items or information delivered or communicated from one role to the next
Mutual Goals for All Disciplines in typical Development Value Network
- Best requirements to satisfy customers and win market share
- Predictability of fulfilling requirements in a one or two year time horizon
- Accuracy of requirements to reduce rework caused by incomplete or incorrect requirements
Types of Requirements
- Features, functions, and capabilities
- Non functional requirements
- Technology selection; OS, Deployment Architecture
- Constraints; time, cost, content
Value Map
During the session we created the value map shown in the following picture
J.D. Krise also made a PowerPoint diagram which we hope to continue developing sometime soon.
References
The concept for this value map is adapted from an article by Verna Allee “Value Network Analysis and value conversion of tangible and intangible assets” Value Network Analysis Article
