3. Change management
Staffing
Roles and responsibilities
Depending on the author and company, additional headers may be
included such as budget, success measures, related projects, and a methodology
for handling change requests. Traditionally the project manager is asked to prepare
the SOW and the document is then presented to the project sponsor and other stakeholders who
review and approve it.
The biggest issue with this approach is that the focus is always on the document rather than what it
represents; and it is typically always written in a hurry, often within a week. The sponsor reads the
document and validates that all the information you would expect to see is there and that the
timeline and budget are within bounds of acceptability and then accepts the document.
What is seldom done is for the stakeholders to formally put aside time to workshop the completed
SOW to subject it to a rigorous level of due diligence. This workshop should ask questions such as:
1. Is there a common understanding of the project purpose? Even if there is a purpose statement,
does everybody interpret it the same way?
2. Is there agreement on what success looks like?
3. Does each stakeholder understand and accept what is expected
from them throughout the course of the project and more importantly, after the project?
4. Is the risk table complete? Does it include project and business risks? Are the mitigation
strategies considered practical or are they merely a cut‐and‐paste from the last statement of work?
5. How will risks be managed? Merely writing them into the SOWis not managing them.
6. Is the change management plan aligned to the risk plan?
7. Does the resource plan make sense?
8. Does the budget have contingency? How is it calculated?
The sponsor should allow ample time for this workshop. The desired outcome is confidence
that the project is considered and that the stakeholders are fully enlisted in the project. Not just
engaged, but enlisted. That is, they are fully and actively committed to its success.