Statement of Work: What It Is/What It Does
Statement of Work: What It Is/What It Does
Statement of Work: What It Is/What It Does
The purpose of a Statement of Work (SOW) is to establish a written contract for work to be performed, i.e., when and how.
Use it to start a project effort or start a subsequent phase of a project. A project can have one or more SOWs.
The amount of work agreed to in a SOW should be the amount of work you can clearly describe. If the customers request is
broad, complex, multi-organizational, or very large, use one SOW to cover early requirements gathering and analysis.
Subsequent SOWs can cover design, development and implementation. You can use multiple SOWs for requests that spawn
multiple projects. In this case, use one SOW for project investigation, then one SOW for each project that follows.
ProjectName:
Theprojectnamethatwillconsistentlybeusedfordiscussingthisproject.
BusinessOwner(s):
Thenameoftheperson(s)fromthebusinessorganizationwhohasultimateresponsibilityfordefiningandaccepting
resultsofthisproject.
ProjectManager(s):
Thenameoftheindividual(s)responsibleformanagingtheproject.
ProjectName:
Theprojectnamethatwillconsistentlybeusedfordiscussingthisproject.
MeasuresofSuccess:
Providemeasuresofsuccessthatwillbeusedtoassesssuccess.Measuresofsuccessshouldbestatedinmeasurable
andquantifiableterms.Clearlystatethegoal,notactivities,inbusinessterms.
RequestSummary(AttachDocuments,ifNecessary):
Asummaryoftheneedorproblemexpressedinbusinessterms.Includeadescriptionofthechronologyofevents
leadinguptotherequestforservice.IfthisisaSOWthatfollowsapreviousSOWforthisproject,summarizethe
outcomeoftheworkfromthepreviousSOW.
BusinessBenefits:
Statethespecificbusinessbenefitsthatthisprojectwillprovide.
ScopeofSOW:
Summarizethekeybusinessfunctionsand/ormajordeliverablesofthiseffort.Identifyanycurrentmanualor
automatedproceduresinvolved.Identifyworkeffortboundaries;whatisincludedandexcludedinthiseffort.Identify
dependenciesonotherworkefforts.
DevelopmentandImplementationApproach
BasicApproach:
Whatisthestrategybywhichatechnicalsolutioncanbefound?Howwilltheoptionsofbuild,buy,orreusebe
analyzedandweighed?Arethereanyspecialtechnicalcircumstancesthatneedtobetakenintoaccountwhen
managingthetechnicalaspectsofthisproject?Willtherebespecializedmethodologiesneeded?IftheSOWcovers
multiplereleasesoffunctionality,describethatapproachhere.
SummaryTasks/Deliverables:
ListkeysummarytasksanddeliverablesforthisSOW.Summarytasksshouldappearasmajortasksontheproject
plan.
ProjectPlan(Attach,ifNecessary):
Theprojectplanisatahighlevel,reflectingthebasicapproach,summarytasksanddeliverablesratherthandetailed
information.Identifymajortasksandcompletiondatesformajordeliverables.Iftherewereanydependencies
identifiedintheScopesection,includeaplanitemtotracktheirprogress.Thismilestonelevelprojectplancanbe
carriedforwardformanagementtracking.
2007 gantthead.com 2
gantthead.com Statement of Work
ProjectName:
Theprojectnamethatwillconsistentlybeusedfordiscussingthisproject.
ProjectOrganization:
Highleveldescriptionofprojectorganization(e.g.,hierarchy,matrix).Highlightexternalparticipation(e.g.,vendor).
Thissectionmaybetextoragraphicorganizationchartformat.
MajorRolesandResponsibilities(AttachProjectRolesandResponsibilitiesMatrix,ifNecessary):
Describewhatisexpectedofthevariousresources(identifiedintheProjectOrganizationsection)andwhen.It
includes,forexample,theoverallresponsibilitiesoftheprojectmanager,businesspartner,businessareaandany
otherswhosecommitmentiscritical.MayusetheProjectRolesandResponsibilitiesMatrixinthetemplatetodefine.
ManagementReviewProcess(HowWillProjectStatusBeTrackedandReported?):
Checkasmanyasapply:
ProjectPlanProjectSlateScheduledStatusMeetingsSteeringCommitteeMonthlyStatusReports
Other(Explain):
Assumptions/Constraints/Risks:
AssumptionsareconditionsthatyouexpecttobeinplacethatpertaintotheeffortcoveredbythisSOW.Ariskisan
eventthathasareasonableprobabilityofoccurringthat,ifitoccurs,candeterprojectsuccess.Identifyknown
barriersorboundariesastheyrelatetotheworkeffortcoveredbythisSOW.Identifypotentialrisksandhowtheywill
bemanaged.Mentiononlyrisksthatarelikelytohappen,noteverythingthatcouldpossiblygowrong.
AcceptanceProcedure:
Establishtheacceptancecriteriaforthedeliverablesdiscussedaboveandtheprocedureforachievingcustomer
acceptance.
ChangeofScopeProcedure:
EstablishtheprocedureforhandlingchangesoutsidethescopeasdefinedbytheStatementofWork.Specifywho
authorizeschanges.Achangeofscopetotheprojectis:(1)Anadditionaldeliverablenotdefinedinthisdocument;(2)
anadditionaldeliveryorstepnotdefinedinthisdocumentforaplanneddeliverable:(3)furtherchangestoan
accepteddeliverable;or(4)acontradictiontoitem(s)orassumption(s)statedinthisdocument.
EstimatedResourcesandCosts
2007 gantthead.com 3
gantthead.com Statement of Work
NonStaffingCosts:
HighlevelestimateofnonstaffcostsfortheworkbeingcoveredbythisSOW.Costsareorderofmagnitudeand
shouldnotbetoospecific.
Staffing Number Costs Comments
Totalfulltimeequivalent
businessemployees,
systememployeesand
outsideconsultants
requiredforthescopeof
thisSOWandthecostfor
thissupport.
2007 gantthead.com 4
gantthead.com Statement of Work
Statement of Work
Deliverable Review Form
ProjectTitle: <ProjectTitle>
Date: <MM/DD/YYYY>
ProjectNumber: <ProjectNumber>
Client: <Name>
2007 gantthead.com 5
gantthead.com Statement of Work
Statement of Work
Quick Cover Sheet
ProjectName:
ProjectNumber:
ProjectManager: Date:
Thefollowingdeliverablesareattached:
MilestoneDates:
Staffing:
Cost:
BillingOption:
CustomerApprovalAuthority: Date:
2007 gantthead.com 6