This Ten Top Tips series will explore how to create a statement of work or scope of work document, often also referred to as a SoW. It’s the third in our trio of project management foundations, and they go hand-in-hand with our previous series – creating timing plans and creating estimates.
If you haven’t already, bookmark this page and read our complete guide on how to create a Statement of Work. There you will find the best practices, some examples, and a handy checklist infographic. Just be sure to read through to the end of the post where you’ll find a FREE Statement of Work template.
The truth is, it’s tempting to not bother with a statement of work (SoW), and people can get a little over excited about a more agile approach to documentation – after all, who likes paperwork? As little as possible and only where really necessary sounds great doesn’t it! But does that mean we shouldn’t produce SoW’s? No.
Define the project
SoW’s provide the extra layer of detail that cost estimates and project plans can’t provide to describe exactly what needs to be done. The SoW provides high-level overarching project information and defines detailed deliverables, standards, criteria and requirements for each phase.
It’s where you put the meat on the bones of the project, and as you do, you get an opportunity to flesh out the details of what you’re going to deliver in your project. But it’s really a good thing. In creating a SoW you’ll probably end up adjusting your estimate and your timeline as you remember things that you should have added but forgot to.
This level of detail provides reassurance to the client as to what will be delivered and ensures that there really is a shared understanding on what the project will deliver and achieve. For those of you that always wanted to be a lawyer, this is as close as we get! For both the agency and the client the SoW becomes the bible in determining what’s ‘in scope’ and what’s ‘out of scope’. They matter because ultimately they serve as the reference point for determining what’s being paid for, and what’s not. If you’re able to get your SoW right, it’ll save you a world of pain later on in a project.
Strike a balance
The really challenging question for project managers when writing the statement of work is deciding how much detail should the SoW contain – too little detail and the client might they’re not getting what they paid for – too much detail in the SOW, and not only will it take you a long time to write and get approved but you can find it difficult to pivot the project when necessary as you’ve defined away any flexibility. So you need to strike the balance of making sure the SoW get signed off quickly while still ensuring that you’re raising the questions and covering off potential problem areas.
10 top tips for creating statements of work
The following 10 top tips blog series have been written as a guide for developing and creating statements of work and scope of work documents. We’ll look at the following 10 top tips for approaching creating statements of work:
- Break it up
- Break it down
- Paint it black & white
- Put it into context
- Be specific
- Make assumptions
- Make it simple
- Check it
- Share it
- Stick to it
What do you think?
What do you think we’re missing? In the next ten posts we’ll delve into the details of these tips but what else should PM’s be thinking about when developing a statement of work? We’d love to hear if you’ve got any tips too – why not share them using the comments below?