Scope shows the list of outcomes that you want to produce within a single release. These are not solutions! Outcomes describe the end result, and “how” someone gets there details the solution. When scoping releases, you should always describe the outcome to achieve based on problems you want to focus on solving and value you want to bring.
Why is it valuable?
The value of this milestone is that it helps the team stay organized and focused, ensuring everyone knows what to do and when. For the product or service delivery, it means having a clear plan that guides development, making sure it meets the goals and is delivered on time.
Who’s involved?
DID YOU KNOW?
Agile teams do not have specific departments! They all float across different duties. So, this means that a UX designer can perform discovery work, and play any other kinds of duties they desire. See how this works in the Agile Handbook's "Daily Life on Agile Teams".
The following duties are involved in this milestone. These duties are performed by anyone who commits to them on a cross-functional team.
The scope milestone happens at the beginning of a project and then teams iterate on the scope deliverables constantly. Every time they perform a round of discovery, the vision and scope itself evolves and needs to be adjusted. Teams learn new things in research that shift their understanding of the problems they should be solving in MVP and MMP.
What deliverables are involved?
MVP #1 Release-level Scope
MMP Release-level Scope
Types of Projects That Complete the Milestone
Here are the types of projects that complete the milestone. Click on each of them to learn more: