36C77619Q0157-0001002.docx

<project> Deliverable Expectation Document – {DATE}

<NAME>

Deliverable Expectation Document Contract Number: <number> <associate CLINS/PWS>

Version 1 Date: No 14, 2017 This document includes data that shall not be disclosed outside the Government and shall not be duplicated, used, or disclosed in whole or in part except as provided in the contract between the Government and <contractor>.

Version # Date:

Author:

<NAME> Deliverable Expectation Document Introduction Purpose The purpose of the Deliverable Expectation Document (DED) is to outline <insert contractor name> proposal for the content and format of the <name of project/product/task> deliverable and the process for reviewing and finalizing the deliverable.

To mitigate cost and schedule risks associated with unclear expectations and rework, this document will be used to identify and document expectations before significant development begins.

Deliverable Details Deliverable Description <describe task>.

Deliverable Content

1. <describe the format of the deliverable>

a. Document

b. Task

c. Series of artifacts

2. What is in scope and/or out of scope

3. What CLINS are included.

Deliverable Format {example: Each facility will require a separate <name> PowerPoint and Summary of Results. The Debriefing PowerPoint Presentation will be delivered to IPS as a PowerPoint that includes the required content outlined above. The Summary of Results will be delivered to IPS as a PDF that includes the required content outlined above. The Assessment Data Workbook will be delivered to IPS as an Excel Workbook that includes the required content outlined above. The Assessment Process and Plan will be delivered to IPS as a Word Document that includes the required content outlined above.} Deliverable Submission The draft deliverable and the final deliverable will be sent to the following stakeholder for review:

Exhibit 1: Deliverable Distribution List

IPS poc 1

IPS poc 2

Deliverable Review Process and Schedule Each report will go through an internal peer review and quality control review before the deliverable is submitted to the VHA IPS stakeholders identified in Exhibit 1. When the deliverable is submitted to the VHA stakeholders, the VHA stakeholders will have <#> business days to review the deliverable and provide any comments or requests for changes. VHA stakeholders will review the document and use track changes and comments to communicate feedback to the <contactor> project team. The <contractor> team will create a feedback document (Excel table) with all VHA stakeholder comments, <contractor> response to comments, and how <contractor> intends to resolve the comment. This will be submitted to the VHA stakeholders, along with the revised documents, within <#> business days of receiving feedback. To resolve all feedback, the <contractor> team may request to collaborate with the VHA stakeholders via LYNC meetings and email to ensure that all comments and concerns are addressed and make appropriate changes to the document.

{sample further description: Since these deliverables are dependent on facility participation, there is not a date-specific schedule. The facility assessment takes approximately two weeks to complete. Upon assessment completion, it takes the <contractor> team approximately two weeks to complete assessment scoring, create the Debriefing PowerPoint and Summary of Results, and update the Assessment Data Workbook. Therefore, it is anticipated that these deliverables will be completed approximately <#> business days after completion of the assessment for each facility.}

Signed: _________________________________________________________________________ VHA Project Manager Date Signed: _________________________________________________________________________ Contracting Officer Representative (COR)

Change Request Summary The table below contains any changes to the baseline as approved by the IPS PM and the COR.

Exhibit 3: Change Request

Comments

Name of Request

[Comments]

Change Description

As needed

Justification

[Comments]

Impact

[Comments]

Requestor

[Comments]

**Status

[Comments]

*Change Number format

**Exhibit 3 Status Key In Review Approved Rejected