[Client]

[Project]
Done Checklist
<Date>

Our Services were performed and this Report was developed in accordance with our Statement of Work dated Date and are subject to the terms and conditions included therein.
Our Services were performed in accordance with Standards for Consulting Services established by the American Institute of Certified Public Accountants ("AICPA"). Accordingly, we are
providing no opinion, attestation or other form of assurance with respect to our work and we did not verify or audit any information provided to us.
Our work was limited to the specific procedures and analysis described herein and was based only on the information made available through Date. Accordingly, changes in circumstances
after this date could affect the findings outlined in this Report.
This information has been prepared solely for the use and benefit of, and pursuant to a client relationship exclusively with Client. PwC disclaims any contractual or other responsibility to
others based on its use and, accordingly, this information may not be relied upon by anyone other than Client .

Confidential information for the sole benefit and use of PwC's Client.
USING THIS TEMPLATE
Provide detailed instructions for the completion of this template in the section "Instructions for Completing This

INSTRUCTIONS FOR COMPLETING THIS TEMPLATE

Field Name

Final Line of Page

Confidential Information for the sole benefit and use of PwC's Client.
n of this template in the section "Instructions for Completing This Template" below. Consider the following: explanation o

TEMPLATE

Description / Instructions

Confidential Information for the sole benefit and use of PwC's Client.
owing: explanation of key field

Confidential Information for the sole benefit and use of PwC's Client.
 Definition of Done Checklist Tool

Team Name: <<Team>>

Criteria Detailed Criteria

State Auto Confidential Page 5 of 8

721675530.xlsx

Definition of Done criteria Example Deliverable Definition Frequency Tool

1. Test Pass rate >=85%
2. Test Coverage Analysis
3. Zero critical, high or medium defects remain open Test Data Sets Test Data Sets Quarterly QA Tool
1. Zero critical or high defects remain open SharePoint & QA
2. Test cases executed to requirements Functional Test Results Monthly Tool
1. Zero critical or high defects remain open SharePoint & QA
2. Test cases executed to requirements Performance Test Results Quarterly Tool

Tasks which have been checked into the source

1. Zero critical or high defects remain open code management tool describing what changed
2. Test cases executed to requirements Build/Release Notes and tracing back to why it was changed Weekly SharePoint & eMails

Scripts to build, create executables, deploy the

Automated Build, Deployment and executables to the correct environments and Daily, weekly, and
Code versioned and stored in repository smoke test scripts execute a smoke test / with results on schedule monthly QA Tool

The data model and the product extensions are

defined within the product.
• Any new subject areas/domains, entities,
relationships, and attributes must be labeled in the
data model.
• Any changes to existing subject area/domain,
entities, relationships, and attributes must also be
labeled in the data model.
• For configuration management purposes, data
model comparison reports should be produced to
Physical Data Model Extension indicate and validate changes between data models Version Control
Code versioned and stored in repository Changes and versions Adhoc Software, Application
Source Code, including configuration Source code, configuration files that are pulled into Daily, weekly, and VersionControl
Code versioned and stored in repository files a build monthly software
Scripts to create the Physical Database, Scripts that apply the changes to the production VersionControl
Code versioned and stored in repository grant permissions ect… databases Monthly software
Data layouts, technical design and development
Design reviewed & approved Interface Specifications specifications for each interface. Monthly SharePoint
Data elements, screen mockups to define changes VersionControl
Design reviewed & approved Configuration Templates before they are developed. Monthly software

FMEA Performance Test Cases Performance Test Cases Quarterly QA Tool

Page 6 of 8
721675530.xlsx

- Prioritized User Stories and Estimates for the

Product.
- Grouped into Sprints and Releases Agile Management
Product Owner signs off on sprint review Product Backlog - Product backlog managed by the Product Owner. Monthly tool

- One of the paths within a Narrative for a business

process
- Reflects the need of stakeholders in the process-
such as a claim handler, supervisor, customer, etc.
- One to many User Stories for Narrative Stories
- User Stories are the Source of the Product backlog Agile Management
Product Owner signs off on sprint review User Story (Task) managed by the Product Owner. Monthly tool

Prioritized User Stories and Estimates for the Agile Management

Product Owner signs off on sprint review User Story (Task) Product Monthly tool

Prioritized User Stories and Estimates for the Agile Management

Product Owner signs off on sprint review Task Board Product Monthly tool

- High level business processes

- Frames the process and helps identify
stakeholders and actors
Agile Management
Product Owner signs off on sprint review Epics and Release Plan Monthly tool
Defines the complete Claims Next Generation
Program Release Schedule (Themes) and Sprint
Relevant artifact stored in project library Sprint / Release Plan Plans Reference Sharepoint
Architecture Document used for supporting the
Relevant artifacts stored in project library Architecture strategy document systems Reference Sharepoint
Relevant artifacts stored in project library Disaster Recovery Plan Define if Client has in place Reference Sharepoint

Relevant artifacts stored in project library Security Architecture / Model Reference Visio & Sharepoint

Spreadsheet which feeds the product configuration

of the Claims Organization regions, offices, etc…
and how they can be drilled in to within the claims
Relevant artifacts stored in project library Organizational Hierarchy center product Reference Sharepoint
Service level agreements with all of our internal
Relevant artifacts stored in project library Service Level Agreements and external service providers Reference Sharepoint

End User Training CBTs, communication and Sharepoint or other

Relevant artifacts stored in project library Training Material training classes Reference training systems

Page 7 of 8
721675530.xlsx

A run book is a written set of operating procedures

for the operation of a computing system. It is
collectively written, maintained and used by all
vested parties including application and
environment support personnel. Typically, a run
book contains procedures for starting, stopping,
and monitoring systems, handling special requests,
Project Control Document, Quality averting problems and handling problems
Relevant artifacts stored in project library Strategy (exceptions). Adhoc Sharepoint
Relevant artifacts stored in project library Coding Standards Reference Sharepoint
Relevant artifacts stored in project library Design Standards Reference Sharepoint

Relevant artifacts stored in project library Source Control Management Policies Reference Sharepoint
Sharepoint & Agile
Requirements reviewed and signed off BSD (Buisness Spec Document) Functional req. / specification design documented. Monthly Management Tool

Specification of the system use for a subset of a

User Story.
- Actors, Preconditions, Post-conditions
- Main Flow
- Alternate Paths
- Business Rules
- Error Messages
- Data Definitions/Validation Rules
Use Case, Business Requirements - Glossary
Requirements reviewed and signed off Documentation Monthly SharePoint
Test cases executed to requirements Unit test cases and results Unit test cases and results Weekly QA Tool
Test Cases reviewed and approved User Acceptance Test Cases User Acceptance Test Cases Monthly QA Tool
Test cases stored in Quality Center System Test Plan System Test Plan Monthly QA Tool

The document would list the test results for UAT

including but not limited to the following metrics:
1. Total Number of Defects Discovered, 2. Total
Number of Defects Resolved, 3. Total Number of
Defects Outstanding. For any Defects outstanding,
provide an executive summary of the resolution
plans. It must also include the location of Test
Results and Defect Log. Signatures must be
retained.
Test pass rate >=95% User Acceptance Test Results Signoff UAT Sharepoint
Traceability matrix updated:
1. Sprint work to original scope Traceability between the requirements, the test
2. Designs to requirements Traceability Matrix Updated cases Monthly QA Tool
Zero critical or high defects remain open Functional Test Cases Functional Test Cases Monthly QA Tool

Page 8 of 8