Sample Project Scope Document

Scope Statement Objectives Constraints Project Structure Role Definitions Project Team Assumptions

Deliverables Functional Requirements Project Change Control Future Projects Authorization Change History

---

Scope Statement

To implement (product name) including (list of modules) at (customer name) on or before (commencement date) and to provide three months of system commencement support at a price of (price).

---

Objectives

• Install the (product name) server and workstation components on the appropriate computers.
• Train the implementation team on all features and functionality necessary to make implementation and setup decisions.
• Convert data from (previous system).
• Develop customized reports.

---

Constraints

• Technical
  • Have the hardware requirements been met?
  • Is the operating system software up to date?
  • Is data readily availability from the current system?
• Financial
  • Is there any possibility of the reduction of withdrawal of budgeted money?
• Operational
  • What current operations of the business, month-end and year-end procedures could cause problems?
  • What is the accuracy of the data from the current system?
• Geographic
  • Are the team members geographically dispersed?
• Time
  • Is the commencement date realistic?
  • Will the customer's staff be available?
  • Are there vacations scheduled?
  • Is there a sick-day problem?
• Resource
  • Do the people working on the project have the necessary skills to perform their assigned tasks?
  • Is there physical space available for training to take place for multiple people?
  • Will an area be dedicated to project for meetings and system testing?
• Legal
  • Are there any legal obligations that must be met relating to the project, such as existing contracts with customers, equipment lease terminations, or changes in ownership taking place?
• Political
  • What are the internal political ramifications of the project?
  • Is anyone's job threatened by the success or failure of the project?
  • What policies and procedures will change, and who will be affected?
• Ethical
  • The question here is not "can we do this project?", but "should we do this project?".
  • Will this project provide value significantly exceeding its price?
  • Are there any other ethical concerns?

---

Project Structure

---

Role Definitions

  Executive Sponsor

• Provide senior management support for the project team
• Sign off on all deliverables and objectives
• Approve or reject change requests, and therefore the budget for the project
• Resolve resource, legal, and political disputes
• Oversee the Project Manager

  Project Manager

• Oversee all aspects of the project
• Maintain project documentation, including updates to the project plan, issues list, timeline, etc.
• Communicate progress of project deliverables, budget, and timeline, in relation to the scope document and project plan
• Provide expertise and guidance in the business and/or data processing areas of the project

  Project Owner

• Oversee all aspects of the project
• Communicate progress of project deliverables, budget, and timeline, in relation to the scope document and project plan
• Ensure that (customer name) resources are available as needed, including providing requirements, user acceptance testing, and training
• Provide expertise and guidance in the business and/or data processing areas of the project

  Team Leader (module)

• Manage resources and tasks
• Communicate system information to Team Members
• Test the system
• Validate and accept data, whether converted or entered manually
• Develop and implement the required user processes and procedures to support the new system
• Provide information regarding their areas of responsibility to the Project Manager

  Team Member (module)

• Learn the new functions and procedures of the system
• Test the system
• Provide system information to Team Leader

  Project Advisor

• Provide business and/or data processing expertise to the project team

  (product name) System Administrator

• Take responsibility for system maintenance, upgrades and security
• Act as principal technical contact during system commencement

---

(customer name) Project Team

---

Assumptions

• This project is subject to the three standard consulting assumptions:
  • Problem-solving requires valid data
  • Decision-making requires free choice
  • Implementation is best achieved through collaboration
• To be successful, the relationship between scope, cost, and time (commencement date) must be maintained. A change to any one of these three interrelated variables will affect the other two. For example, adding to the scope of the project will require an adjustment to the cost of the project and/or the commencement date.
• (product name) is the licensed property of (customer name). All data is the exclusive property of (customer name).
• Employees of (customer name) could perform all tasks on this project. Use of MKA Systems Consulting personnel is at the discretion of (customer name) because MKA Systems Consulting has knowledge and experience that is of value to (customer name) and will reduce the workload on (customer name) staff and increase the probability of success.
• Failure of (customer name) to note and communicate desired functionality or properly test system functionality as required will result in a system that does not perform as needed.
• The following table lists the percent of time a person will need to commit on any given week to the project based on the role(s) they assume. Times are cumulative; for example, if a person is the leader of one team and a member of another team, they will need to commit 75% of their time to the project.

  Role	Time
  Executive Sponsor	10%
  Project Manager	50%
  Project Owner	50%
  Team Leader	50%
  Team Member	25%
  Project Advisor	5%
  System Administrator	10%

---

Deliverables

• Project plan
• Training schedule
• Business project documentation
• Training manuals
• Issues list

---

Functional Requirements (per module)

Examples of quality requirements:

• (number) records spot-checked
• Report produces same grand totals as previous system
• Eliminate duplicate data entry
• Report finishes printing within (time limit)

---

Project Change Control

Any changes affecting project deliverables will require signed approval through the change control process. A Change Request Form must always be completed.

---

Future Projects

• (list of possible future projects)

---

Authorization

We have examined this document. We agree with and understand the necessary tasks, responsibilities, and milestones needed to complete this project successfully.

Authorized Representative of (customer name)		Project Manager
Title		Title
Date		Date

---

Change History