You can use the DA Browser to learn more about the options in the goal diagram of Figure 1.
Why This is 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.
- We need to do just enough requirements exploration so that we understand what we’re trying to achieve as a team.
- User stories and epics often need to be supplemented with other models to explore domain, user experience, and business process concerns.
- You should have a strategy to agree upon and manage quality requirements.
- Consider what techniques and tools you will need to prioritize and manage your work.