[Your Project Name]

Project Scope Statement

[version date]

[Adapt this Project Scope Statement template to your project’s specific needs and culture.
Some options are included in the header names; choose the one that best suits your team. A
scope statement should be considered dynamic, updated and redistributed periodically
throughout the project’s lifecycle as the agreed-upon scope changes. Keep it to about three
pages or less. If it threatens to get any longer, consider referencing attachments instead.]

Summary

[A short, clear sentence or two clarifying what the project is.]

Objectives

[Why are you doing it?]

 [Three to five bullets clarifying the project’s purpose. Money? Fame? Networking? Art
for its own sake? A means to work independently? A supporting component for another
project?]

Deliverables/Components

 [List the major components of the work—around five, or so.]

Acceptance Criteria/Success Metrics

 [Describe the criteria for success. Is there an important deadline? Quality standard?
Preparedness for something? What are your metrics for the project to be considered
“good?”]

Exclusions or Is/Is Not List

[Clarify what the work is and is not, particularly if there is likely confusion.]

Is: Is Not:
Constraints

[Enter major budget items, including anticipated resources (funding you have) and
expenses (costs). Attach a more detailed report, and reference it here. For “Status,” indicate
the funding source, or whether it is secure or not.]

Budget: See “Appendix A. Budget”

Item Amount Comment Status

Resources

Total Resources:

Expenses

Total Expenses:

Milestones:

[List the major important dates or points of accomplishment. In “Status,” indicate whether
it is started, assigned, on track, in trouble, complete, etc.]

Date Description Status

Assumptions

[List any parameters that you are hoping will be true, for purposes of moving forward, but
if they prove not to be, you need to reconsider some important dimension of the strategy.
Indicate the person who will be vigilantly tracking this circumstance to determine whether
action is needed.]

Item Tracked By Status Mitigation Plan

-2-
(cc) Jonathan Feist, 2013. For related materials and information, visit http://www.projectmanagementformusicians.com
Dependencies

[List any project component that relies on the completion of any other project component before
it can be done.]

Stakeholders/Project Team

[List the members of your project team. For “Distribution List,” indicate anyone who should
receive updated copies of this scope statement, whenever there are changes made to it. If you
know of a role but haven’t fulfilled it yet, indicate “Needed” in the name. You might keep a
simpler chart here and reference a more detailed one, such as a RASCI chart, as an attachment.]

Distribution Name and Roles and Comment

List Contact Responsibilities

Attachments

[List supplementary documents.]

 [Attachment A. Budget]

Version History

[List previous versions and dates, and indicate the major changes and decisions. If it’s
useful for you to do so.]

-3-
(cc) Jonathan Feist, 2013. For related materials and information, visit http://www.projectmanagementformusicians.com