This artifact provides a high-level basis for more detailed technical requirements. It captures the technical solution by describing the high-level stakeholder requests and constraints that give an overview of the reasoning, background, and context for detailed requirements. The vision serves as input for communicating the fundamental "what and why" for the project and provides a strategy against which all future decisions can be validated.

The vision should rally team members behind an idea and give them the context for decision-making in the requirements area. The vision must be visible to everyone on the team.

It is good practice to keep this artifact brief, so you can release it to stakeholders as soon as possible, and to make the artifact easy for stakeholders to read and understand. You can accomplish this by including only the most important features and avoiding details of requirements.

Projects that focus on product development might extend the marketing section and include a more detailed product position statement that is based on their needs and research.