Directions for using template:
Read the Guidance (Arial blue font in brackets) to understand the information that should be placed in each section of this template. Then delete the Guidance and replace the placeholder within with your response. There may be additional Guidance in the Appendix of some documents, which should also be deleted once it has been used.
Some templates have four levels of headings. They are not indented, but can be differentiated by font type and size:
• Heading 1 – Arial Bold 16 font
• Heading 2 – Arial Bold Italic 14 font
• Heading 3 – Arial Bold 13 font
• Heading 3 – Arial Bold Italic 12 font
You ...view middle of the document...
The goal of the phase, represented by the content of the documentation, is to achieve team and customer agreement on the desired solution and overall project direction.
The Vision/Scope document is organized into four main sections:
• Business Opportunity: a description of the customer’s situation and needs
• Solutions Concept: the approach the project team will take to meet the customer’s needs
• Scope: the boundary of the solution defined though the range of features and functions, what is out of scope, a release strategy, and the criteria by which the solution will be accepted by users and operations
• Solution Design Strategies: the architectural and technical designs used to create the customer’s solution
Justification: Vision/Scope documentation is usually written at the strategic level of detail and is used during the planning phase as the context for developing more detailed technical specifications and project management plans. It provides clear direction for the project team; outlines explicit, up-front discussion of project goals, priorities, and constraints; and sets customer expectations.
Team Role Primary: Product Management is the key driver of the envisioning phase and responsible for facilitating the team to the Vision/Scope approved milestone. Product Management defines the customer needs and business opportunity or problem addressed by the solution.
Team Role Secondary: Program Management is responsible for articulating the Solution Concept, Goals, Objectives, Assumptions, Constraints, Scope, and Solution Design Strategies sections of this document.}]
[Description: The Business Opportunity section contains the statement of the customer’s situation. It is expressed in business language, not technical terms. This section should demonstrate Microsoft’s understanding of the customer’s current environment and its desired future state. This information is the overall context for the project.]
[Description: The Opportunity Statement section describes the customer’s current situation that creates the need for the project. It may contain a statement of the customer’s opportunity and the impact of capitalizing on that opportunity (product innovation, revenue enhancement, cost avoidance, operational streamlining, leveraging knowledge). It may contain a statement of the customer’s problem and the impact of solving the problem (revenue protection, cost reduction, regulatory compliance, alignment of strategy and technology). It should include a statement that connects the customer’s opportunity/problem to the relevant business strategy and drivers. The Opportunity Statement is written concisely using a business executive’s voice.
Justification: The Opportunity Statement demonstrates that Microsoft understands the customer’s situation from the business point of view and provides the project team and other readers with the strategic context for the remaining...