Software Project Vision & Scope document creation

by Janette Toral

(view the photo gallery for a bigger image size)

The output of the requirements management phase is the Vision and Scope document, or sometimes referred to as Project Charter or Statement of work. It is prepared by the requirements analyst and can contain the following, at the minimum:

1. Introduction

   Overview of the entire document that includes purpose, its association with other systems, and how it is organized.
   

2. Business requirements

1. Background
   History and rationale for the application being developed.
2. Opportunity
   Problem that the product intends to solve. Its fit to the overall direction of the company and alternatives in the market.
3. Business objectives
   Value it provides to the client that is quantifiable and measurable.
   
4. Success criteria
   Success parameters defined and method on how it will be measured
5. Customer or market needs
   
List client problem or needs that the new product will address. It must include who gets affected by the problem and its quantifiable impact.

6. Business risks
   Cite various risks that may affect the development of the product that needs to be mitigated.
   

3. Stakeholder and User Profiles

   List stakeholders who have influence to the project and at which phases do they get involved. List the users involved in the project, level of expertise, and training needed to participate effectively in the project. Clearly state who can  sign-off, request for change or enhancement, and approve.
   

4. Vision statement

   Summarize the purpose and intent of the project.
   

5. Product Overview

   Provide a perspective about the product that includes its relation to other systems. Write product features that emphasizes on its benefit to the user. Also include other requirements such as standards that need to be used, system requirements, environmental factors, security, among others.
   

6. Assumptions

   List assumptions that were made when creating this document.That if such factors will change, shall affect commitments made in this document.
   

7. Dependencies

   Cite factors that will influence the success of the project.
   

8. Scope and limitations 

1. Initial release
   Features included in the initial release.
   
2. Subsequent release
   Features included in future releases.
3. Limitations and exclusions
   Features that the client might anticipate but not included.

9. Documentation requirements

   Various documentation that may need to be developed for this project such as users manual, online help, installation guide, labeling of materials, and its proper packaging.
   

Note that in the deliberation process of this document, your approved minutes of the meeting must be on hand to back-up your assumptions for the project.