Problem Resolution Plan: Version
Problem Resolution Plan: Version
<Project Name>
Problem Resolution Plan
Version <1.0>
[Note: The following template is provided for use with the Rational Unified Process. Text enclosed in
square brackets and displayed in blue italics (style=InfoBlue) is included to provide guidance to the author
and should be deleted before publishing the document. A paragraph entered following this style will
automatically be set to normal (style=Body Text).]
[To customize automatic fields in Microsoft Word (which display a gray background when selected), select
File>Properties and replace the Title, Subject and Company fields with the appropriate information for
this document. After closing the dialog, automatic fields may be updated throughout the document by
selecting Edit>Select All (or Ctrl-A) and pressing F9, or simply click on the field and press F9. This must
be done separately for Headers and Footers. Alt-F9 will toggle between displaying the field names and the
field contents. See Word help for more information on working with fields.]
<Project Name> Version: <1.0>
Problem Resolution Plan Date: <dd/mmm/yy>
<document identifier>
Revision History
Date Version Description Author
<dd/mmm/yy> <x.x> <details> <name>
Table of Contents
1. Introduction 2
1.1 Purpose 2
1.2 Scope 2
1.3 Definitions, Acronyms, and Abbreviations 2
1.4 References 2
1.5 Overview 2
5. Problem Tracking 2
1. Introduction
[The introduction of the Problem Resolution Plan provides an overview of the entire document. It includes
the purpose, scope, definitions, acronyms, abbreviations, references, and overview of this Problem
Resolution Plan.]
1.1 Purpose
[Specify the purpose of this Problem Resolution Plan.]
1.2 Scope
[A brief description of the scope of this Problem Resolution Plan; what Project(s) it is associated with and
anything else that is affected or influenced by this document.]
1.4 References
[This subsection provides a complete list of all documents referenced elsewhere in the Problem Resolution
Plan. Identify each document by title, report number if applicable, date, and publishing organization.
Specify the sources from which the references can be obtained. This information may be provided by
reference to an appendix or to another document.]
1.5 Overview
[This subsection describes what the rest of the Problem Resolution Plan contains and explains how the
document is organized.]
3. Problem Tracking
[Identify problem categories and where they are stored and tracked, for example:
• Product and process problems (defects) may be stored and tracked in a Change Tracking System.
• Project problems (issues) may be tracked in an issues list, which is a component of the Status
Assessment.
• Process problems (non-conformances) may be recorded in an audit report and then tracked in a
Change Tracking System (as a kind of Change Request).
• Review anomalies will be recorded in the Review Record and tracked from there; if the scope of the
problem requires it, a Change Request may be raised.]