The Vision milestone is where you build a definition of the outcomes you want to achieve and problems to solve as a team. Vision describes where a product is going, and is broken down by release. When forming an MVP vision, product teams seek to solve the most important problems in their problem space. They should define MVP's in such a way that they are able to learn from them and vet high risk items in their product plans early and often. The vision helps the team stay aligned or decide how to adjust where their product is going.
Why is it valuable?
The value of this milestone is that it helps the team stay organized and focused, making sure everyone knows the plan and their role in it. For the product, it ensures that it meets customer needs and stands out in the market, increasing its chances of success.
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 vision milestone happens at the beginning of a project and then teams iterate on the vision deliverables constantly. Every time they perform a round of discovery, the vision 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 Vision
MMP Release-level Vision
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: