[Project Name]

Release 0.1
Integrated Testing Phase
Resolution Plan for Entry Criteria not Met

Developed By: [Author]

[Date]

Page 1 of 3 01/03/2011
Yourcompany Proprietary
How to Use This Document

This document is a template designed to assist in the development of a Resolution Plan.

A Resolution Plan will be developed when a Project is unable to complete established entry criteria for an
individual testing phase. Regular “checkpoint” meetings are established as part of the Entry/Exit Criteria
design and will be scheduled with the Project Teams to monitor progress prior to and during test
execution for each testing phase.

The intent of the Resolution Plan is to allow the Testing Support Team to understand what Entry Criteria
was not met by the Project Team, what steps are being taken to resolve the issues preventing the team
from completing all entry criteria, and what is the timeline for resolution. It will also allow both the
Project Team and the Testing Support Team to manage risks associated with entry criteria not met and
plan for contingencies.

The file should be named using the following naming standard:

• XXXX Resolution Plan MMDD.doc
• XXXX – Name of Project Team
• MMDD – Month and Day Resolution Plan submitted

Once the Resolution Plan has been competed by the Project Team, it should be emailed to the Testing
Support Group at testing support@yourcompany.com.

Page 2 of 3 01/03/2011
Yourcompany Proprietary
Entrance Criteria Not Met

List the entrance criteria that your Project was unable to complete. This may be taken from the Entry/Exit
Criteria checklist.

Defects/Issues Requiring Attention

State any issues outstanding that are preventing the Project from completing the entrance criteria. If there
are specific high priority defects that are preventing you to enter a test phase use this section to list and
give status on those defects.

Dependencies/Impacts

Specifically state all applications that will be affected by the inability of the Project Team to satisfy
entrance criteria for the testing phase. This list should include all internal and external interfaces.

Action Plan

List what activities the Project or Application Team is doing to meet the entrance criteria for the testing
phase. This section should specify specifically the actions taken by each team to resolve the issues and/or
defects listed in section 2. Status reporting methods for reporting progress to the Testing Support Team
must be included as part of the Project Team’s action plan.

Date for Resolution

Specify the target date in which all issues/defects preventing the Project from entering the test phase will
be resolved.

Date for Test Phase Entry

Specify the date in which the Project Team would like to begin testing in the Integrated Test Environment
(ITE). The Project Team will need to consider the Testing Calendar published by the Testing Support
team when proposing a date for entry into a test phase. Entry into a test phase will occur at the beginning
of a test cycle since code migration occurs prior to a testing cycle.

Communication Plan

The Testing Support Team will work with the individual Project Teams to identify risks of being
excluded from the release due to not meeting entry criteria for a test phase. Status will be reported on a
daily basis during the Daily Defect Meetings with the Testing Support team (time of which varies by
Release). The Testing Support Team will notify Release Planning of any Project Team that is unable to
enter a test phase. Specific impacts to the release based on outstanding issues or defects will be
communicated to Release Planning and escalated to the PMG (Program Management Group).

Page 3 of 3 01/03/2011
Yourcompany Proprietary