This Inception process goal describes how we will elicit and capture the initial requirements for our solution. We want to do just enough work to understand what our stakeholders want so that we can confidently begin Construction. To be effective, we need to consider several important questions:
- What level of detail do we need to capture?
- How will we explore the ways that people will potentially use the solution?
- How will we explore domain concepts, the business process(es) to be supported by the solution, UI requirements, and general requirements?
- How will we capture non-functional requirements?
- How will we approach modeling activities?
- How will changing requirements be managed throughout Construction?
Why is This Important?
There are several reasons why we need explore the initial scope in a bit more detail:
- We need to answer common stakeholder questions. Before providing funding for the rest of the effort, our stakeholders are likely to ask us fundamental questions such as: What are you going to deliver? How much will it cost? and When will you deliver it? To answer these questions we will need to work through what we believe the initial scope of our next release will be.
- We need to know what to work on initially. You want to do just enough requirements elicitation to understand what our stakeholders want so that we can confidently begin Construction.
- We want to set reasonable expectations as to what we’ll deliver. Both the team and your stakeholders need to come to an agreement around a reasonable scope for the current effort that is being funded so that you’re all working towards the same vision.
The strategies/practices referenced in the goal diagram above are described, including the trade-offs involved and considerations for when (not) to apply them, in the book Choose Your WoW! A Disciplined Agile Delivery Handbook for Optimizing Your Way of Working. If you want to succeed at enterprise agile you need choices, not prescriptions.