Published: April 25, 2008

In this process, the project team writes the vision/scope document and performs a risk assessment.

Figure 5. Write the vision/scope document

Activities: Write the Vision/Scope Document

During this process, the project team completes the first draft of the vision/scope document and distributes it to the team, customers, and stakeholders for review. During the review process, the document undergoes multiple iterations of feedback, discussion, and change.

The vision/scope document is usually written at a strategic level of detail and the project team uses it during planning as the context for developing technical specifications and project management plans in greater detail. It provides clear direction for the project team; outlines explicit project goals, priorities, and constraints; and sets customer expectations.

Project vision and project scope are distinct concepts, and successful projects require both. Project vision is an unlimited view of the solution. Project scope identifies the parts of the vision that a project team can accomplish within its constraints. The vision/scope document defines both concepts.

Another key activity of this process is for the team to assess and document the project risks. This is done using the Risk Template.

The following table lists the activities involved in this process. These activities include:

• Writing the vision/scope document.
• Assessing and documenting project risks.

Table 5. Activities and Considerations for Writing the Vision/Scope Document