Vision/Scope Approved Milestone

he Vision/Scope Approved Milestone is an opportunity for customers and the team to agree upon project scope and vision. Determining vision and scope are opposite activities, yet both are required for a successful project. Vision is the expansive view of what a solution can be. Scope defines what part(s) of the vision can be accomplished within the project constraints.

Vision Statement Draft

1. Customer Requirements – Gather information from the customer regarding processes and enhancements to the process.

2. Concept Presentation – This is conducted by the Project Manager and is for the purpose of introducing a project to Requirements Analyst and Developers. If current clients drive the project, the Customer Representative should be present to express client issues.

3. Scope Complete Estimation – The Project Manager estimates the duration of creating the scope document.

4. Scope Creation – The Project Manager prepares the scope document. The scope document should include:

Business Need

· Global Requirements

· User/Business scenarios

· Client Contacts

· Description of current functionality (Overall , Likes and Dislikes)

· Description of needed functionality including high level User Interface (UI) needs.

· Focus and usability group requirements. (Ease of learning, Ease of Use, Flexibility, Effectiveness, User Satisfaction, Memorable, Naturalness, Consistency, Non-Redundant, Supportiveness)

· Initial Protocycle (Complete Process and limited UI screens)

During this step the scope document may be presented to clients for feedback and acceptance.

Design Goals Draft

1. Scope Document Turnover – The Project Manager presents the scope document to the Requirements Analyst.

2. Project Schedule Draft – The Project Manager drafts the project schedule for functional requirements tasks or Proof of Concept tasks.

3. Preliminary Functional Requirements Review – The Requirements Analyst presents the preliminary functional requirements document to the Project Manager for review against the scope document. This step occurs until Project Manager and Requirements Analyst are prepared to present the project scope and functional requirements to the customer.

4. Preliminary Functional Requirements – The Requirements Analyst creates a preliminary functional requirements document.