ProjectConnections Print View
888-722-5235
7am-5pm Pacific
Monday - Friday
We'd love to talk to you.
Learn more about ProjectConnections and who writes our content.
Site Help
| Content Levels | |
 | Register for free access to papers, case studies, and almost 50 templates. |
 | Subscribe for complete access: $14.95 monthly or $149/year |
| Risk-free 15-day trial!
Compare levels View sample templates Corporate subscriptions | |
Project Definition - Statement of Work
Quick Summary
One approach to documenting high-level project objectives and key parameters in a concise document. This document should be only about 2 pages long.
What this is
One approach to documenting high-level project objectives and key parameters in a concise document. Helps make sure the team and all stakeholders understand agree upon the reasons for doing the project, what the project will produce, and various important constraints and assumptions. Such a document should be done before detailed requirements specs are written.
Why it's useful
Expressing project drivers concisely early on is important to making sure the full team and all stakeholders understand and agree upon the reasons for doing the project, what the project will produce, and various important constraints and assumptions. Such a document should be done before detailed requirements specs are written.
How to use it
- The project manager can draft a statement of work that the team then reviews and edits.
- Or the project manager can meet with the core cross-functional team and brainstorm the sections together to create a first draft.
- In the first draft, some items may be left blank if the team does not have the information yet. Or, if items are uncertain, the team can write in their initial information, but mark it as being an "open issue". This latter approach is useful for keeping the team focused on resolving questions.
- Update the SOW as the team proceeds through investigation and planning work. If scope, schedule, or resource tradeoffs are made during this time, the SOW should be updated.
- Have a signoff meeting where the team and major stakeholders officially confirms that this Statement of Work reflects the high-level plan the project.
- Keep the SOW visible during design reviews and project status reviews to ensure that individual functional work is staying true to what the SOW calls for.
©Copyright 2000-2008 Emprend, Inc. All Rights Reserved.
About us Site Map View current sponsorship opportunities (PDF)
Contact us for more information or e-mail info@projectconnections.com
Terms of Service and Privacy Policy