Statement of work template

4,736 views
4,119 views

Published on

Published in: Business, Technology

Statement of work template

  1. 1. PROJECT NAME: PROJECT NAME PROJECT ID:DOCUMENT NAME: STATEMENT OF WORK VERSION:COMPANY/DIVISION: VERSION DATE: PAGE 1 OF 9STATEMENT OF WORK TEMPLATETemplate Revision HistoryVersion Number Release Date Effective Date Revision Purpose1.0 12/20/2006 12/20/2006 Baseline1.1 2/20/2007 2/20/2007 Add template header page1.2 04/02/2007 04/02/2007 Updated Template Use Instructions per PIR93Template Use InstructionsComplete all sections of the template. Do not delete any sections. If a section is not applicable or theanswer is “none,” enter “N/A” or “None” in that section. Sections may be added, but should be added atthe end of a subsection whenever possible.Instructions are provided in each section and subsection as hidden text. To view the hidden text, click the(Show/Hide) toolbar button. Hidden text instructions may be deleted or left hidden.This page must be deleted before this document is approved.
  2. 2. PROJECT NAME: PROJECT NAME PROJECT ID:DOCUMENT NAME: STATEMENT OF WORK VERSION:COMPANY/DIVISION: VERSION DATE: PAGE 2 OF 9Statement of WorkforPROJECT NAMEPrinted on: 4/28/2013Analyst Name: Requirement Analyst NameService Delivery Manager: Service Delivery Manager’s NameProject Sponsor: Initiative Sponsor’s NameBusiness Lead: Business Lead’s NameStrategic Services Manager: Strategic Services Managers NameAS/TS Manager: AS/TS Managers Name
  3. 3. PROJECT NAME: PROJECT NAME PROJECT ID:DOCUMENT NAME: STATEMENT OF WORK VERSION:COMPANY/DIVISION: VERSION DATE: PAGE 3 OF 9Table of ContentsStatement of Work Template......................................................................................................................11 Project Description....................................................................................................................................42 Project Stakeholders.................................................................................................................................43 Development Lifecycle Model...................................................................................................................44 Project Approach......................................................................................................................................45 High-Level Activities..................................................................................................................................46 Systems Affected......................................................................................................................................47 Pre-requisites Dependencies, Constraints and Assumptions...................................................................58 Schedules................................................................................................................................................. 59 Cost Spending Plan..................................................................................................................................610 Risk Analysis.......................................................................................................................................... 611 Resource Plan........................................................................................................................................612 Communications Management Plan.......................................................................................................713 Change Control.......................................................................................................................................814 Test Strategy Plan..................................................................................................................................815 Training Plan for Project Resources.......................................................................................................816 Revision History......................................................................................................................................9
  4. 4. PROJECT NAME: PROJECT NAME PROJECT ID:DOCUMENT NAME: VERSION:COMPANY/DIVISION: VERSION DATE: PAGE 4 OF 91 Project Description1.1 Project Background1.2 Business Benefits1.3 Project Scope2 Project StakeholdersStakeholder Role/Responsibilities3 Development Lifecycle Model4 Project Approach5 High-Level Activities6 Systems AffectedDescription DatesNeededAvailability Requirement Explanation
  5. 5. PROJECT NAME: PROJECT NAME PROJECT ID:DOCUMENT NAME: PROJECT PLAN VERSION:COMPANY/DIVISION: VERSION DATE: PAGE 5 OF 97 Pre-requisites Dependencies, Constraints andAssumptionsPre-requisitesDependenciesAssumptionsConstraints8 Schedules8.1 Milestone ChartMajor milestones and tollgates from the project schedule are listed below.Tollgates Estimated CompletionDateMajor MilestonesDiscoveryRequirementsDesignConstructionTestingTransitionDeploymentWarranty/Support8.2 Detailed ScheduleThe project schedule should be approved by the project team no later than the start of Requirements andDesign, and baselined upon that first approval. The project schedule should be created as early in theprocess as possible and progressively elaborated on as more is known about the project work. The latestdetailed approved project schedule will be located here: Enter Project Schedule Location Here8.3 Work Breakdown StructureThe work breakdown structure (WBS) for the project effort is typically contained within the projectschedule.Issued by: ADS Page 5 of 9OLCC-FIN-PO-00012-TMPL-003-00 Last Updated:04/07/2008This document and all information and expression contained herein are the property of the Family of Orange Lake Resorts and may not be used, duplicated or disclosed for any purpose without priorwritten permission from the issuer. All rights reserved./mnt/temp/unoconv/20130428023254/statementofworktemplate-130427213254-phpapp02.doc
  6. 6. PROJECT NAME: PROJECT NAME PROJECT ID:DOCUMENT NAME: PROJECT PLAN VERSION:COMPANY/DIVISION: VERSION DATE: PAGE 6 OF 99 Cost Spending Plan10 Risk AnalysisRisks for the project will be analyzed on a regular basis by the project team, discussed in weekly teammeetings, assigned to the appropriate person for mitigation, and maintained by the project manager. Thehighest probability and impact risks will be included in regular status reporting in order to be visible tomanagement. Risk will be continually re-assessed throughout the project.A summary of the current highest probability and impact risks for this project are shown below, includingthe response plan or mitigation if available.Name Priority Risk TypeCreationDate Probability Description MitigationPlease see the10.1 Issue ManagementIssues are those situations that may have started as a risk but have now occurred, requiring use of themitigation plan or response. Issues will be assigned to team members and maintained by the projectmanager. Issues that are overdue for action and resolution will be included in regular status reporting inorder to be visible to management.10.2 Action ItemsAction items, or those tasks or actions required for the project but not specified in the project schedule,will be tracked via spreadsheet in the following location: Enter PMO Drive Location HereAction items will be reviewed by the project team on a regular basis. Late and incomplete action items willbe escalated via regular status reporting.11 Resource PlanResource planning involves the identification of specific resources that will be required to complete theproject.Selection of individuals for the project team should be based upon the requirements of the role,the availability of the resource, technology and systems knowledge, business process knowledge, andother subject matter expertise.All resources and stakeholders required for the project are listed below. If the specific person assigned tothat role is not known, still include the business role.Business Role Name Project Roles and ResponsibilitiesIssued by: ADS Page 6 of 9OLCC-FIN-PO-00012-TMPL-003-00 Last Updated:04/07/2008This document and all information and expression contained herein are the property of the Family of Orange Lake Resorts and may not be used, duplicated or disclosed for any purpose without priorwritten permission from the issuer. All rights reserved./mnt/temp/unoconv/20130428023254/statementofworktemplate-130427213254-phpapp02.doc
  7. 7. PROJECT NAME: PROJECT NAME PROJECT ID:DOCUMENT NAME: PROJECT PLAN VERSION:COMPANY/DIVISION: VERSION DATE: PAGE 7 OF 9Business Role Name Project Roles and ResponsibilitiesIn addition to skilled project team members, project resources can include things such as projectworkspace and supplies, software, hardware and telecommunications facilities. Those physical resourcesare described in the table below.Resource Type Description Procurement Plan12 Communications Management PlanKey to the success of the project is the plan for how information will be disseminated to team members,project stakeholders, and other affected and interested parties. The communication plan provides aframework for informing, involving, and obtaining buy-in from all participants throughout the duration ofthe project, including those stakeholders who will be affected by the results of the project.CommunicationMeetings1. Weekly status meetings Initiator RecipientsForm/Type Frequency2. Steering committee meetings Initiator RecipientsForm/Type FrequencyDocumentation3. Meeting agendas Initiator RecipientsForm/Type Frequency4. Meeting minutes Initiator RecipientsForm/Type Frequency5. Executive Status report Initiator RecipientsForm/Type FrequencyInitiator RecipientsForm/Type FrequencyIssued by: ADS Page 7 of 9OLCC-FIN-PO-00012-TMPL-003-00 Last Updated:04/07/2008This document and all information and expression contained herein are the property of the Family of Orange Lake Resorts and may not be used, duplicated or disclosed for any purpose without priorwritten permission from the issuer. All rights reserved./mnt/temp/unoconv/20130428023254/statementofworktemplate-130427213254-phpapp02.doc
  8. 8. PROJECT NAME: PROJECT NAME PROJECT ID:DOCUMENT NAME: PROJECT PLAN VERSION:COMPANY/DIVISION: VERSION DATE: PAGE 8 OF 913 Change ControlThis section of the statement of work defines the Configuration (Scope Change) Management plan for theproject, including the approval process and configurable items required to support scope change withinthe project.All of the documentation and data produced by this project will be maintained in a centralized location asdescribed here: Enter PMO Drive or E-room Location13.1 Configuration Control Plan13.2 Identification of Configuration ItemsThe project’s Configuration Items (CIs), or work products associated with the project that shall be placedunder configuration control, are as follows:Configuration Item Description OwnerBusiness RequirementsDocumentFunctional RequirementsDocumentProject PlanSystem Design DocumentTest Plan14 Test Strategy PlanThe test strategy plan described here is a high level outline of the type of verification and testing that willbe done for the project deliverables. The detailed test plan is produced by the QA organization during theDesign tollgate (estimated delivery date -) and will be stored in the following location: Reference the QATest Plan Location Here15 Training Plan for Project ResourcesThe following skill training is needed in order for team members to be able to complete their assigneddeliverables on this project.Name Required Training Course Provided By Date TrainingNeededDate TrainingCompletedIssued by: ADS Page 8 of 9OLCC-FIN-PO-00012-TMPL-003-00 Last Updated:04/07/2008This document and all information and expression contained herein are the property of the Family of Orange Lake Resorts and may not be used, duplicated or disclosed for any purpose without priorwritten permission from the issuer. All rights reserved./mnt/temp/unoconv/20130428023254/statementofworktemplate-130427213254-phpapp02.doc
  9. 9. PROJECT NAME: PROJECT NAME PROJECT ID:DOCUMENT NAME: PROJECT PLAN VERSION:COMPANY/DIVISION: VERSION DATE: PAGE 9 OF 9Name Required Training Course Provided By Date TrainingNeededDate TrainingCompleted16 Revision HistoryDate Version Author Description of ChangesIssued by: ADS Page 9 of 9OLCC-FIN-PO-00012-TMPL-003-00 Last Updated:04/07/2008This document and all information and expression contained herein are the property of the Family of Orange Lake Resorts and may not be used, duplicated or disclosed for any purpose without priorwritten permission from the issuer. All rights reserved./mnt/temp/unoconv/20130428023254/statementofworktemplate-130427213254-phpapp02.doc
  10. 10. PROJECT NAME: PROJECT NAME PROJECT ID:DOCUMENT NAME: PROJECT PLAN VERSION:COMPANY/DIVISION: VERSION DATE: PAGE 9 OF 9Name Required Training Course Provided By Date TrainingNeededDate TrainingCompleted16 Revision HistoryDate Version Author Description of ChangesIssued by: ADS Page 9 of 9OLCC-FIN-PO-00012-TMPL-003-00 Last Updated:04/07/2008This document and all information and expression contained herein are the property of the Family of Orange Lake Resorts and may not be used, duplicated or disclosed for any purpose without priorwritten permission from the issuer. All rights reserved./mnt/temp/unoconv/20130428023254/statementofworktemplate-130427213254-phpapp02.doc

×