SOW+template.docx
DOCX document 26 KB Posted
- Attached to
- IT - Operational Assessment
- Contract number
- 903
- Issued by
- North Dakota
About this file
This document is a Statement of Work (SOW) template for a project between the State of North Dakota and an unnamed contractor. The template outlines a structured approach for project management, detailing specific deliverables, expectations, and responsibilities for both the state agency and the contractor.
The SOW encompasses six primary deliverables: a Project Kickoff Meeting, a Project Management Plan, a Final Acceptance phase, a Post-Implementation Report, and a Project Closeout Meeting. The contract includes a payment schedule with invoicing tied to each deliverable, with 10% retention at each stage. While specific dollar amounts are redacted, the document indicates a comprehensive project management approach with detailed requirements for communication, scheduling, risk management, and post-project evaluation. The total project budget is specified but the exact amount is not visible in the provided document. The SOW emphasizes collaborative planning, structured project governance, and a methodical approach to project execution and closure.
View the file
Other files
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
STATEMENT OF WORK TEMPLATE
Sample Statement of Work – also FOUND at end of Contract The parties to this Statement of Work (SOW) are the State of North Dakota, Agency Name (STATE), and Name of Vendor (CONTRACTOR).
To the extent that there is any inconsistency between this SOW and the Operational Assessment beginning on Effective Date, the Contract shall control.
1. DELIVERABLE 1: PROJECT KICKOFF MEETING
a. Description:
CONTRACTOR shall coordinate with STATE to schedule a Kickoff Meeting in City Name, ND, with the core project and planning team. CONTRACTOR’s Project Manager shall lead the meeting. The Kickoff Meeting must facilitate the introduction of CONTRACTOR and STATE individuals, and level-set understanding and awareness of project objectives, scope, governance, schedule, and project risks and issues.
b. Expectations of CONTRACTOR:
1) CONTRACTOR shall provide content to STATE for a detailed agenda in advance of the meeting.
2) CONTRACTOR and STATE shall facilitate the meeting, and discuss and further define, at a minimum, the following:
(a) Effective project communication
(b) Project vision, background, purpose, and objectives
(c) Project governance structure, and project roles and responsibilities
(d) Approach to creating the Project Management Plan
(e) Initial risk assessment
c. Expectations of STATE:
1) STATE shall finalize agenda and send agenda to invitees.
2) STATE shall coordinate the logistics and co-facilitate the Kickoff Meeting.
3) STATE’s Project Sponsor and project team members shall participate in the Kickoff Meeting.
d. Completion Date:
CONTRACTOR shall start work with STATE within five (5) working days after the signing of this Contract to schedule the Kickoff Meeting.
e. Acceptance Criteria:
For the acceptance of this deliverable to occur, the Kickoff Meeting results in:
1) Facilitation of Kickoff Meeting using a clearly defined agenda
2) An introduction of critical CONTRACTOR and STATE resources assigned to the project
3) Review of STATE’s Project Charter to include project governance structure, roles and responsibilities, project purpose, objectives, and scope
4) Discussion of communications approach and structure
5) Discussion of known project risks and issues
2. DELIVERABLE 2: PROJECT MANAGEMENT PLAN
a. Description:
CONTRACTOR shall participate, contribute, and collaborate with STATE, led by STATE’s Project Manager, to develop a baseline plan. The Project Management Plan will include the project schedule.
b. Expectations of CONTRACTOR:
1) CONTRACTOR shall participate, contribute, and collaborate with STATE to provide content that includes, at a minimum, the following:
(a) Management plans to control cost, schedule, scope, and quality
(b) Governance structure for the project
(c) Roles and responsibilities of the project team
(d) Integrated change control process
(e) Communication management plan
(f) Risk management plan
(g) Issue management plan
(h) Human resources management plan
(i) Procurement management plan
(j) Implementation and transition plan
2) CONTRACTOR shall provide CONTRACTOR tasks and participate and collaborate with STATE on a detailed project schedule created in Microsoft Project. The Microsoft Project format and settings will be mutually agreed-upon, and the project schedule will follow STATE best practices, including:
(a) Project has appropriate start date
(b) Project has appropriate Work Breakdown Structure
(c) All project tasks have appropriate predecessors and successors, with the exception of summary tasks
(d) All project tasks are auto-scheduled using predecessors to drive the task dates (dates are not manually entered)
(e) Minimal use of constraints
(f) Both STATE and CONTRACTOR tasks are included
(g) Project tasks are broken down into timeframes that can be reasonably managed – STATE encourages a maximum task length of approximately 80 hours/two (2) weeks
(h) Project tasks have appropriate resources assigned with appropriate and reasonable allocation
(i) Schedule has appropriate working times and incorporates STATE and CONTRACTOR holidays and nonworking times
3) CONTRACTOR shall provide written confirmation from an authorized individual confirming contents of the Project Management Plan.
c. Expectations of STATE:
1) STATE shall lead the Project Management Planning effort.
2) STATE’S Project Manager shall be responsible for the Project Management Plan.
3) The Project Management Plan shall follow STATE template.
4) STATE’s Project Manager shall incorporate STATE tasks into the project schedule.
5) STATE shall obtain written confirmation from an authorized individual at CONTRACTOR for the contents of the Project Management Plan.
d. Completion Date:
CONTRACTOR shall start work with STATE within five (5) working days after the signing of this Contract to create the Project Management Plan.
e. Acceptance Criteria:
1) For the acceptance of this deliverable to occur, CONTRACTOR shall provide content to STATE for the Project Management Plan regarding all services, tasks, and products delivered by CONTRACTOR:
(a) Mutually agreed-upon detailed baseline scope and schedule for the project
(b) Management plans to control scope, schedule, cost and quality, including the variance
(c) Governance structure for the project
(d) Roles and responsibilities of the project team
(e) Quality assurance and quality control plans
(f) Integrated change control process
(g) Communication management plan
(h) Risk management plan
(i) Issue management plan
(j) Human resources management plan
(k) Procurement management plan
(l) Implementation and transition plan
2) The Project Management Plan shall adhere to the Project Management Body of Knowledge
3) For the acceptance of this deliverable to occur, approval must be obtained from STATE’s Executive Steering Committee (ESC).
3. DELIVERABLE 3: TEMPLATE
b. Expectations of CONTRACTOR:
1)
c. Expectations of STATE:
1)
d. Completion Date:
1)
e. Acceptance Criteria:
For the acceptance of this deliverable to occur, the following criteria shall be met:
1)
4. DELIVERABLE 4: FINAL ACCEPTANCE
a. Description:
Upon completion of all deliverables, and upon mutual agreement of STATE and CONTRACTOR, the project work will be considered complete and retainage paid to contractor.
b. Expectations of CONTRACTOR:
1) CONTRACTOR shall address any outstanding issues or completion of deliverables.
c. Expectations of STATE:
1) STATE shall alert CONTRACTOR to any outstanding issues.
d. Acceptance Criteria:
For the acceptance of this deliverable to occur, the following criteria must be met:
1) No outstanding or unfinished deliverables
2) No outstanding project or system issues
5. DELIVERABLE 5: POST-IMPLEMENTATION REPORT
CONTRACTOR shall participate, contribute, and collaborate with STATE, led by STATE’s Project Manager, to provide content for the Post-Implementation Report.
b. Expectations of CONTRACTOR:
1) CONTRACTOR shall have project team members participate in the Post-Implementation Survey.
2) CONTRACTOR shall participate, contribute, and collaborate with STATE, led by STATE’s Project Manager, to develop a Post-Implementation Report that provides, at a minimum, the following:
(a) Key project metrics related to schedule, cost, scope, and quality
(b) Business metrics related to project objectives and measurements as defined in the Project Charter
(c) Comprehensive lessons learned valuable to future projects
(d) Success stories from the project
(e) Results of the Post-Implementation Survey
c. Expectations of STATE:
1) STATE’s Project Manager shall be responsible for the final product.
2) STATE’s Project Manager shall design and conduct the Post-Implementation Survey.
3) The Post-Implementation Report shall follow STATE template.
d. Acceptance Criteria:
1) For the acceptance of this deliverable to occur, CONTRACTOR shall participate in the Post- Implementation Survey and provide content to STATE for the Post-Implementation Report regarding all services, tasks, and products delivered by CONTRACTOR:
(a) Key project metrics related to schedule, cost, scope, and quality
(b) Business metrics related to project objectives and measurements as defined in the Project Charter
(c) Lessons learned from the project
(d) Success stories from the project
2) For the acceptance of this deliverable to occur, approval must be obtained from STATE’s Executive Steering Committee (ESC). Remove if not a major project
6. DELIVERABLE 6: PROJECT CLOSEOUT MEETING
a. Description:
CONTRACTOR shall coordinate with STATE to schedule a Closeout Meeting in City Name, ND with the core project team and interested stakeholders. STATE’s Project Manager shall lead the meeting, though CONTRACTOR may be asked to present on certain agenda items. The Closeout Meeting must present a completed Post-Implementation Report and facilitate discussion of the project closeout.
b. Expectations of CONTRACTOR:
1) CONTRACTOR shall provide content to STATE for detailed agenda in advance of the meeting.
2) CONTRACTOR shall provide STATE any required information for STATE’s Project Manager to present the Post-Implementation Report.
3) CONTRACTOR shall expand upon the success stories and lessons learned captured from the Post-Implementation Survey, and discuss details related to the lessons learned to provide comprehensive information to future projects.
c. Expectations of STATE:
1) STATE shall finalize and send agenda to invitees.
2) STATE shall coordinate logistics and facilitate the Closeout Meeting.
3) STATE shall expand upon the success stories and lessons learned captured from the Post- Implementation Survey and discuss and further document details related to the lessons learned to provide comprehensive information to future projects.
d. Acceptance Criteria:
For the acceptance of this deliverable to occur, the Closeout Meeting results in:
1) Completion and confirmation of the Post-Implementation Report deliverable
2) Comprehensive lessons learned and success stories valuable to future projects
7. PROJECT DELIVERABLE PAYMENT SCHEDULE:
The following table defines all payment points.
Deliverable
Deliverable Value To be Retained (10%)
Invoice
| 1 |
| Project Kickoff Meeting |
| $amount |
| $amount |
| $amount |
| 2 |
| Project Management Plan |
| $amount |
| $amount |
| $amount |
| $amount |
| $amount |
| $amount |
| $amount |
| $amount |
| $amount |
| X |
| Final Acceptance |
| $Total Retained |
| $amount |
| $Total Retained |
| Project Deliverable Total |
| $amount |
8. PROJECT TOTAL
The total budget for the project portion of this Contract is $amount
File details come from the government source that posted it. Updated .