Example+Statement+of+Work.docx

This is an example Statement of Work for services under the State Contract - Software Reseller (VAR), #281.

Update and add items as necessary to align with the needed services. Change all blue text to black before execution or delete it if not applicable.

Statement of Work The parties to this Statement of Work (SOW) are the State agency or entity name (STATE), and Name of Business (CONTRACTOR). CONTRACTOR will complete the following services: Insert the services to be performed.

This SOW may not be modified, supplemented, or amended, in any manner, except by written agreement signed by both STATE and CONTRACTOR.

To the extent that there is any inconsistency between this SOW, the Participating Addendum or Master Agreement for Software Value-Added Resellers beginning on its effective date, control shall in this order of precedence: Participating Addendum, followed by the Master Agreement.

1. Deliverable 1: Project Kickoff Meeting

1. 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 core project team members, and level-set understanding and awareness of project objectives, scope, governance, schedule, and project risks and issues.

Expectations of CONTRACTOR:

0. CONTRACTOR shall provide content to STATE for a detailed agenda in advance of the meeting.

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 Plan

(e) Initial risk assessment Expectations of STATE:

0. STATE shall finalize agenda and send agenda to invitees.

STATE shall coordinate the logistics and co-facilitate the Kickoff Meeting.

STATE’s Project Sponsor and project team members shall participate in the Kickoff Meeting.

Completion Date:

CONTRACTOR shall start work with STATE within five (5) working days after the signing of this SOW to schedule the Kickoff Meeting.

Acceptance Criteria:

For the acceptance of this deliverable to occur, the Kickoff Meeting results in:

0. Facilitation of Kickoff Meeting using a clearly defined agenda An introduction of critical CONTRACTOR and STATE resources assigned to the project Review of STATE’s Project Charter to include project governance structure, roles and responsibilities, project purpose, objectives, and scope Discussion of communications approach and structure Discussion of known project risks and issues Deliverable 2: Project Plan

1. Description:

CONTRACTOR shall participate, contribute, and collaborate with STATE, led by STATE’s Project Manager, to develop a baseline Project Plan. The Project Plan will include the project schedule.

Expectations of CONTRACTOR:

0. CONTRACTOR shall participate, contribute, and collaborate with STATE to provide requested content for the Project Plan. Typical sections CONTRACTOR may be asked to contribute to are as follows:

(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) Communication management

(e) Quality Management

(f) Risk, issue, and action item management plans

(g) Implementation and transition plan Remove if this is a separate deliverable CONTRACTOR shall provide CONTRACTOR tasks and participate and collaborate with STATE on a detailed project schedule created in Microsoft Project. The project schedule will follow STATE best practices, including:

(h) Project has appropriate start date

(i) Project has appropriate Work Breakdown Structure

(j) All project tasks have appropriate predecessors and successors, with the exception of summary tasks

(k) All project tasks are auto-scheduled using predecessors to drive the task dates (dates are not manually entered)

(l) Minimal use of constraints

(m) Both STATE and CONTRACTOR tasks are included

(n) 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

(o) Project tasks have appropriate resources assigned with appropriate and reasonable allocation

(p) Schedule has appropriate working times and incorporates STATE and CONTRACTOR holidays and nonworking times CONTRACTOR shall provide written confirmation from an authorized individual confirming contents of the Project Plan.

Expectations of STATE:

0. STATE shall lead the project planning effort.

STATE’s Project Manager shall be responsible for the Project Plan.

The Project Plan shall follow STATE template and best practices.

STATE’s Project Manager shall incorporate STATE tasks into the project schedule.

STATE shall obtain written confirmation from an authorized individual at CONTRACTOR for the contents of the Project Management Plan.

Completion Date:

CONTRACTOR shall start work with STATE within five (5) working days after the signing of this SOW to create the Project Plan.

Acceptance Criteria:

0. For the acceptance of this deliverable to occur, CONTRACTOR shall provide requested content to STATE for the Project Plan regarding all services, tasks, and products delivered by CONTRACTOR.

CONTRACTOR and STATE agree upon the baselines scope, schedule, and management plans for the project.

The Project Plan shall adhere to the STATE template and STATE project management best practices.

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 Note: For additional deliverables use the following deliverable as a guideline.

Deliverable 3: Template

1. Description:

1. Expectation of CONRACTOR:

0.

1. Expectations of STATE:

0.

1. Completion Date:

0.

1. Acceptance Criteria:

For the acceptance of this deliverable to occur, the following criteria shall be met:

0.

Deliverable 4: Post-Implementation Report Some projects have objective measurements (typically identified in the Project Charter) that extend three to six months beyond the implementation of the product, and therefore, completion of the Post-Implementation Report may be delayed. In these cases, consider what is reasonable for the CONTRACTOR to provide for this deliverable and adjust the following language accordingly.

1. Description:

CONTRACTOR shall participate, contribute, and collaborate with STATE, led by STATE’s Project Manager, to provide content for the Post-Implementation Report.

1. Expectations of CONTRACTOR:

0. CONTRACTOR shall have project team members participate in the Post-Implementation Survey.

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

1. Expectations of STATE:

0. STATE’s Project Manager shall be responsible for the final product.

STATE’s Project Manager shall design and conduct the Post-Implementation Survey.

The Post-Implementation Report shall follow STATE template.

1. Acceptance Criteria:

0. 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 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 Deliverable 5: Project Closeout Meeting Some projects have objective measurements (typically identified in the Project Charter) that extend three to six months beyond the implementation of the product, and therefore, completion of the Project Closeout Meeting may be delayed. In these cases: 1) consider what is reasonable for the CONTRACTOR to provide for this deliverable and adjust the following language accordingly; 2) consider changing the name of this deliverable to “Post-Implementation Meeting,” with the goal of providing and discussing survey results, lessons learned, and success stories soon after implementation; and 3) schedule a separate Closeout Meeting with the agency at a later date to review the completed Post-Implementation Report (depending on project circumstances, the CONTRACTOR may or may not be included in that later Closeout Meeting, and that meeting may or may not be included in this Scope of Work).

1. 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.

1. Expectations of CONTRACTOR:

0. CONTRACTOR shall provide content to STATE for detailed agenda in advance of the meeting.

CONTRACTOR shall provide STATE any required information for STATE’s Project Manager to present the Post-Implementation Report.

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.

1. Expectations of STATE:

0. STATE shall finalize and send agenda to invitees.

STATE shall coordinate logistics and facilitate the Closeout Meeting.

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.

1. Acceptance Criteria:

For the acceptance of this deliverable to occur, the Closeout Meeting results in:

0. Completion and confirmation of the Post-Implementation Report deliverable Comprehensive lessons learned and success stories valuable to future projects Deliverable 6: Final Acceptance Note: This deliverable signifies the STATE’s acceptance of the product or service, and could be due either after user acceptance testing (signifying an approval to move into production) or after implementation (signifying an approval to move into maintenance mode), depending upon the project circumstances. Timing for this deliverable should take into consideration any warranty periods, rollouts, implementation risks, and phased implementations and/or testing.

1. 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.

1. Expectations of CONTRACTOR:

CONTRACTOR shall address any outstanding issues or completion of deliverables.

1. Expectations of STATE:

STATE shall alert CONTRACTOR to any outstanding issues.

1. 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 Project Deliverable Payment Schedule:

Align this table with the deliverables listed above and their associated deliverable value. Typical amounts for retainage are approx. 15%. and is retained by STATE until Final Acceptance has been approved by STATE.

The following table defines all payment points.

CONTRACTOR

[insert business]

BY: [Signature]

[Printed Name]

[Title]

Date:

STATE OF NORTH DAKOTA

Acting through its Insert Agency or Entity

BY: [Signature]

[Printed Name]

[Title]

Date: