Work Product: Vision |  |
This artifact contains the definition of the stakeholders' view of the technical solution to be developed, specified in terms of the stakeholders' key needs and features. It contains an outline of the envisioned core requirements for the system.
Purpose
This artifact provides a high-level basis for the more detailed technical requirements. It captures the essence of the technical solution by describing high-level stakeholder requests and constraints that give an overview of the reasoning, background and context for detailed requirements. It serves as input for communicating the fundamental "what and why" for the project, and provides a strategy against which all future decisions should 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 therefore be visible to everyone on the team.
Relationships
Roles | Responsible: | Modified By: Analyst
Input To | Mandatory: None | Optional: Develop Technical Vision | External: None
Output From | Develop Technical Vision
Properties
Optional |
Planned |
Illustrations
Templates | Vision
Key Considerations
It is generally good practice to keep this artifact brief so you can release it to stakeholders as soon as possible, and to make it easy for stakeholders to read and understand. You can accomplish this by including only the most important features and avoiding details of requirements. Projects with a focus on product development may extend the marketing section and include a more detailed product position statement based on their needs and research.
Tailoring
Impact of not having | If this artifact is not used, there is a high risk that stakeholders and the development team will have different expectations. This could lead to cancellation of the project. Misunderstandings and miscommunication about the strategy may cause the project to move away from the original vision and create a discrepancy in stakeholder expectations.
Reasons for not needing | This artifact is generally recommended for all but trivial projects.
Representation Options | The vision is usually captured as a document. If key stakeholder needs are captured in a requirements management tool, then this part of the document may be generated using reporting capabilities. If the vision serves a set of projects or an entire program, the overall vision may be divided into several vision work products. The vision of the program then brings the visions together by providing program-specific content and referencing the subordinate visions.
More Information
Checklists | Vision