Skip to main content

Project Statement of Work (SOW)

The project statement of work (SOW) is a description of products or services to be delivered by project.

The Statement of Work, or SOW, is the bible for the work the project must produce. The SOW is a key governance tool whether it is being used to direct work for a vendor or contractor, or used to direct the work internally, the SOW must contain a description of all the work that is expected. The description need not be at the detail level, indeed for large projects capturing detail in the SOW is not practical, but should be comprehensive and include work that produces the projects deliverables as well as administrative work such as project reporting.

The SOW will form a key part of the contract if the work is being done by a vendor or contractor. Work captured in this document is part of the vendor's contractual obligation to you. Work not contained in the SOW will only be done if it is mutually agreed upon, or introduced to the project through a change request. The SOW is also important to the internal team, although there are no legal implications, because resourcing will be planned to accommodate only that work described in the SOW.

The SOW contains:

Scope of work: A detailed description of the work, the software and hardware to be used, and the exact nature of the work.

Location of the work: Where the location of the work to be done would be other than a standard location. This would be applicable to an SOW for work to be performed offshore.

Period of performance: The start and finish date for the project, maximum billable hours per time period, etc.

Deliverables schedule: Due dates for the deliverables of the project. This would include completion dates for development, QA testing, User Acceptance Testing, etc.

Applicable standards: Industry standards or other standards imposed on the project deliverables. These should include any standards such as ISO, CMM, CMMI, etc.

Acceptance criteria: These would include any quality standards that must be met, for example zero priority 1 defects. They should also include any other conditions that must be met such as number of test cases, number of test cases executed, etc.

Specialised requirements: These will include any special qualifications for the workforce, such as a PMP certified Project Manager.

Your next step will be to have your project sponsors, or the customer for the project, approve the SOW. The SOW will now become the official scope baseline for your project. Anything detailed in the SOW must be present in the final product.

Guidelines for developing SOW:

     1. Link requirement with approach 

     2. Develop scope 

     3. Identify concrete and measurable steps 

     4. Estimate resources and budget needs 

     5. Identify risks 

     6. Define project success 

     7. Identify responsibilities 

     8. Have clear project priorities 

     9. Open communication and cooperation 

     10. Basis for acceptance and authorization

     11. Use clear language

     12. Be Specific   

     13. Review regulations, Policies and other documents

The sample SOW document table of content is provided below:

DOCUMENT HEADING

REVISION HISTORY

DEFINITIONS 

TABLE OF CONTENTS

I.        REQUEST      

II.       BACKGROUND

1.       History of the Project         

2.       Business or IT Objectives of the Project    

3.       Critical Success Factors of the Project      

III.      PROJECT SCOPE      

1.       In-Scope      

2.       Out of Scope 

IV.      MANAGEMENT APPROACH   

1.       Plan Management    

2.       Communications Management       

3.       Team communications        

4.       Customer communications  

5.       Issues Management 

V.       QUALITY ASSURANCE

VI.      TECHNICAL ENVIRONMENT  

1.       Development Environment  

2.       Testing Environment 

3.       Middle-Tier Environment     

4.       Access & Security    

VII.     WORK APPROACH AND DELIVERABLES      

1.       Work Approach       

2.       Deliverables (& Milestones)  

VIII.    ROLES & RESPONSIBILITIES

1.       Project Organization Chart  

2.       Project Roles and Responsibilities Table     

·         Executive Project Sponsor   

·         Project Customer     

·         Project Manager      

·         Business Analyst      

·         Data Architect

·         Programmer 

·         Testing Lead  

·         Testers        

·         Project Role  

·         Project Officer        

·         SME

IX.      PROJECT PLAN        

X.       RISK MANAGEMENT  

XI.      CHANGE MANAGEMENT       

XII.     ACCEPTANCE MANAGEMENT

·         Acceptance Procedure        

·         Final Acceptance      

XIII.    APPROVED BY 

Comments

Post a Comment

Popular posts from this blog

Scaled Agile Framework (SAFe)

The Scaled Agile Framework (SAFe) is a set of organizational and workflow patterns for implementing agile practices at an enterprise scale. The framework is a body of knowledge that includes structured guidance on roles and responsibilities, how to plan and manage the work, and values to uphold. Scrum is a simple, flexible approach to adopting Agile that's great for small teams. SAFe is an enterprise-wide Agile framework designed to help bring Agile beyond the team and into the company as a whole. Scaled Agile has built a comprehensive level that includes all the four layers called the team, program, large solutions, and portfolio level. 4 Layers: Portfolio - Strategy, Vision, Roadmap, Strategy goal, Decision making, Budget, Portfolio level metrics,  Program - Align multiple teams towards a common mission, Bring together all the Agile teams, transparency, collaboration, and synchronisation, Scrum of Scrums, Product Owners to define the overall vision. Large Solutions - ar...
Post a Comment
Read more

Risk Register

A project risk register is a tool project managers use to track and monitor any risks that might impact their projects. Risk management is a vital component of project management because it's how you proactively combat potential problems or setbacks. Risk Description Impact Risk Response Risk Level Risk Owner Automation Testing Software licence delay Delay in starting testing and project schedule impact As we have one licence. Planned to start automation testing in 2 shifts. Planned to get one more licence in 2 weeks’ time. High IT team Frequent Disruption in dependency API services Delay in development of integration and unit testing Dependency API service is down, and the team is working on resolving the issue. Continuously working with API team High External Team/ Project Manager There is chance of new requir...
Post a Comment
Read more

Delivering a project within budget

 Here are some tips for delivering a project within budget: Set a realistic budget Define the project's scope and necessary resources, and create a budget that's realistic. Cost estimate Segment the project into smaller tasks and milestones to plan how to use resources and provide clarity. Divide the project plan Break down the project into tasks to avoid late deliverables and over-budget projects. Monitor progress Regularly track the project's progress to identify and prevent cost overruns. Use progress reports to compare actual costs to the budget. Anticipate and revise changes Communicate with stakeholders to identify and assess risks, and assign owners to each risk. Consider different scenarios Estimation can be difficult for complex projects with many potential outcomes. Tracking: Tracking time spent on tasks, Tracking expenses per project, and Using project management software. Use Historical Data Your project is likely not the first to try and accomplish a specific o...
Post a Comment
Read more