# Vision Milestone

## What is it?

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?

{% hint style="info" %}
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](/agile-training-portal/agile-handbook/agile-teamwork/day-to-day-on-an-agile-team/daily-life-on-agile-teams.md)".
{% endhint %}

The following duties are involved in this milestone. These duties are performed by anyone who commits to them on a cross-functional team. 

1. Product manager [duty](/project-portal/project-success-handbook/project-components/project-duties.md)

## When does it happen in a project?

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?

1. MVP # 1 Release-level Vision
2. 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: 

{% content-ref url="/pages/rrL8axHWzeoFB472tkP9" %}
[Web-Based Product Projects](/project-portal/project-success-handbook/project-types/web-based-product-projects.md)
{% endcontent-ref %}

{% content-ref url="/pages/qr2wC3zvv2TJ89tFJGMk" %}
[Service Design Projects](/project-portal/project-success-handbook/project-types/service-design-projects.md)
{% endcontent-ref %}

{% content-ref url="/pages/Ha6QpFcHulTlkkrCVzVs" %}
[Discovery Projects](/project-portal/project-success-handbook/project-types/discovery-projects.md)
{% endcontent-ref %}

{% content-ref url="/pages/QigGXvBeciy2sCjst5kj" %}
[Broken mention](broken://pages/QigGXvBeciy2sCjst5kj)
{% endcontent-ref %}

## Completing the Milestone

Here's the section to learn how to complete the milestone:

{% content-ref url="/pages/GwBWpHh0XtZijA6cWtZd" %}
[Completing Vision and Scope Milestones](/project-portal/project-success-handbook/keys-to-project-success/completing-vision-and-scope-milestones.md)
{% endcontent-ref %}

## Dashboard Reference

Here's all of the information associated with this milestone on the Milestones Dashboard.

{% embed url="<https://airtable.com/appMDxpNsGN2qyS8N/shrjepxWtkp5smh1A?detail=eyJwYWdlSWQiOiJwYWdiNWZoNzZ3M2E1ZWlTSCIsInJvd0lkIjoicmVjejV4UThjWENTYnRZWVQiLCJzaG93Q29tbWVudHMiOmZhbHNlLCJxdWVyeU9yaWdpbkhpbnQiOnsidHlwZSI6InBhZ2VFbGVtZW50IiwiZWxlbWVudElkIjoicGVsSk5EVnMyazRzOUFFN0QiLCJxdWVyeUNvbnRhaW5lcklkIjoicGVsckZSVWZTZFN1YXlsRzUifX0>" %}

## Head to the Next Lesson


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://guide.techfleet.org/project-portal/project-success-handbook/project-components/project-milestones/vision-milestone.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.