Executive Summary

The purpose of the Deliverables Management Plan is to facilitate the timely review and approval of the contractor deliverable; to ensure deliverable is tracked and all events are recorded; and to ensure a copy of each deliverable and all supporting materials are archived in the Project repository.

This Plan identifies the procedures used to coordinate the review and approval of a contract deliverable. The objectives of this Plan are to:

• Define the process for receiving, reviewing, and accepting deliverable

• Ensure deliverable is reviewed by the appropriate staff to promote quality

In the Agile world, each iterative sprint produces a usable outcome or deliverable. For a sprint to be called “DONE ,” it must produce a deployable work product (Minimum Viable Product (MVP)). This end product is what is called an “Agile Deliverable” in the Agile deliverable management approach.

Throughout the Project, the contractor must produce and provide to the state specific deliverables.

When the contractor submits a deliverable it will go through a series of review steps where it will be checked for completeness and correctness with respect to the contractual terms and conditions and sprint requirements.

Introduction

A Deliverable is a term used in project management to describe a tangible or intangible artifact produced that is intended to be delivered to a customer (either internal or external). A deliverable can be a software product, a design document, a training program, or other asset.

The Child Welfare Services – New System (CWS-NS) Deliverable Management Plan (hereafter called the “Plan”) outlines how a deliverable will be managed throughout its life cycle (from submission to closure).

Purpose

The purpose of this Plan is to facilitate the timely review and approval of the contractor^[1] deliverable; to ensure deliverable is tracked and all events are recorded; and to ensure a copy of each deliverable and all supporting materials are archived in the Project^[2] repository (SharePoint for the documents and GitHUB for the source code). Deliverable management is necessary to ensure the Project only accepts deliverable that meets contract requirements.
 

Scope

This Plan identifies the procedures used to coordinate the review and approval of a contract deliverable. In addition to documenting the approach to deliverable review and approval, the process covers the roles and responsibilities in the deliverable process, tracking, and the tools used to track the progress of the deliverable.

The objectives of this Plan are to:

• Define the process for receiving, reviewing, and accepting deliverable.
• Ensure deliverable is reviewed by the appropriate staff to promote quality.

Roles and Responsibilities

Before discussing the deliverable management process flow, it is important to understand various roles in the process and the responsibilities associated with those roles. Table 2.1 below depicts key roles and corresponding responsibilities pertaining to the deliverable management process.

[1] Generic name for supporting contracts, county consultants, and digital services

[2] Child Welfare – New System (CWS-NS) Project (hereafter called the “Project”)

Table 2.1: Deliverable Management Plan Roles and Responsibilities

[3] Ensures correctness of the deliverable, that is the deliverable meets the functional/utility requirements set forth in Statement of Work (SOW)/contract

Source: https://www.scrumalliance.org/community/articles/2008/september/what-is-definition-of-done-(dod)

Deliverables Management Process 

When the contractor submits a deliverable it will go through a series of review steps where it will be checked for completeness and correctness with respect to the contractual terms and conditions and sprint requirements.

Once a deliverable has been accepted and all related documentation has been imported into the repository, the DM will update the status of the deliverable in the deliverable tracking log as closed.

After the deliverable status has been recorded as closed, the DM will baseline or “lockdown” the electronic copy of the deliverable file in the repository.

The CWS-NS Project deliverable management process is based on an Agile approach. Figure 5.1 depicts the comprehensive deliverable management process for the Project.
 

Each rectangular box in the deliverable management process flowchart (Figure 5.1) corresponds to a step in the process and is identified by a numeric digit (1, 2, 3, and so on). Table 5.1 below provides a brief description of each of these process steps.
 

Table 5.1: Description of Deliverable Management Process Steps

Payment Processing

Covered in the Project Contract Management Plan document.
 

Tracking and Management Tools

To ensure accurate and consistent management of all project documents, all work products, and deliverables shall be stored on the appropriate Project repository as shown in Table 6.1 below.