Scope of Work Template

Scope of Work (SOW)[Project Name]

Company Logo Goes Here

Revision 0.1

5Table of ContentsPurpose2Revision History2Introduction/Background3Scope of Work/Scope Statement3Period of Performance3Key Project Activities3Schedule/Milestones4Project Approach & Resource Plan4Acceptance Criteria5

Purpose The Statement of Work (SOW) is a document that describes the scope of work required to complete a specific project. It is a formal document and must be agreed upon by all parties involved. In order to be effective, the SOW must contain an appropriate level of detail so all parties clearly understand what work is required, the duration of the work involved, what the deliverables are, and what is acceptable.

Revision HistoryRevision DateVersionChanges

Introduction/BackgroundThis section should provide a general description of the project as well as highlight the projects background and what is to be gained by the project.

Scope of Work/Scope StatementThis section should provide a brief statement of what you expect to accomplish as a result of this scope of work. This section should highlight what is and is not included in the scope of the project in broader terms.

Period of PerformanceThis section should define the time period over which the project will occur. The timeframe for the project can be pre-determined or based on a completion date to coincide with some external requirement.

Key Project Activities This section should include a description of the actual tasks which the project will require. This should include what tasks need to be completed in order for successful completion of this project/contract. As with all other portions of the SOW, every effort should be made to include as much detail as possible.

Project Initiation/Planning:

Design Phase:

Build Phase:

Testing:

Implementation Phase:

Transition and Close:

Schedule/MilestonesThis section should define the schedule of deliverables and milestones for this project. It is imperative that all milestones, tasks, and schedule information are as accurate as possible.

The below list an example of these milestones:

MilestonesEnd Date

RFP/SOW ReleaseJanuary 2, 20xx

Vendor SelectionFebruary 1-28, 20xx

Vendor NegotiationMarch 1, 20xx

Business/Functional RequirementMarch 2, 20xx

DesignAugust 31, 20xx

Build/Unit TestNovember 30, 20xx

Integration TestingDecember 31, 20xx

System TestingFebruary 20, 20xx

UATFebruary 25, 20xx

Cut-overFebruary 25, 20xx

Project Completion ReviewFebruary 25, 20xx

Project Closure/Archives CompleteMarch 3, 20xx

Project Approach & Resource PlanThis section will have an overview of how the work will be executed against and what the identified resources are for the particular project. An outline of the team roles and responsibilities should be included.

Acceptance CriteriaThis section defines how the business will accept the deliverables resulting from this SOW. The acceptance of deliverables must be clearly defined and understood by all parties.

Executive Sponsor:

[Name][Title][Date]

Stakeholders:

[Name][Title][Date]

[Name][Title][Date]

[Name][Title][Date]