Writing a Scope Statement

not be included is critical to the successful completion of the project. The SOW is contained in a document referred to as a Statement of Work, which typically contains the following elements ( a sample is included in Appendix B):

• Project identification number

• Project sponsor or champion

• Project manager assigned to the project

• List of project stakeholder representatives

• List of project team members

• List of steering (management oversight) team members

• Description of corporate strategic objective driving the project

• Description of the project purpose

• List of sponsor and stakeholder expectations

• Description of how the project will achieve the stated purpose

• List of business benefits with defined validation measures

• List of special requirements (equipment, skills, knowledge, etc.)

• List of specific inclusions

• List of specific exclusions

• List of project deliverables

• List of project constraints

• List of project assumptions

• List of project critical success factors

• Preliminary project budget

• Preliminary project milestones

• Proposed readiness review date

Preparing a scope statement that includes this level of detail is necessary for strategic, mission-critical projects, and creating them can require a significant amount of time. Unfortunately, scope statements of this magnitude are rarely done, which is one of the primary causes of project failures. The lack of good project preparation is typically caused by pressures placed on the project manager to get started on the work of the project in order to meet deadlines imposed by management or the customer. Communicating the information contained within the project charter and the project scope statement to the project team and its stakeholders is an important next step. Holding a project kick-off meeting, especially for strategic initiatives implementing a PMCoE, is an ideal way to distribute this important communication.

0 0

Post a comment