Document
Title:
Document Number
Version #:
Author
1.1
Problem Resolution Plan
1
Page Number
Kyle Martin
Active Date
1 of 3
26/08/2011
Problem Resolution Plan
Figure 3 and the following sections detail the SmartPosition Development Teams problem
resolution plan.
Identification of a
Problem
Escalate to Team
Leader
Solution found
NO
No
Escalate to Project
Manager
Solution found
Implement
solution
Figure 1 Problem Resolution Plan Flow Diagram
1.1.1 Problem Reporting
Any problem will be formally documented using the outlined problem reporting form
designed for this project. The form is to be submitted to the team leader and project manager
via email. It is up to the team leader to deal with the problem however if the team leader is
unable to appropriately deal with the problem the responsibility of resolving the problem will
then be escalated to the project manager.
1.1.2 Problem Analysis
Problems that have been reported will be analysed to determine the potential issues they
could cause the project and its resources, schedule and budget.
Each problem will be subjected to the risk analysis register found in section … and
appropriately given a risk categorisation number. If the risk of the problem has not been
identified in the risk analysis register the new risk will be added to the register.
WARNING: Google Project controls all documents. Printing this document will result in an uncontrolled copy and will not be updated.
Contact the Administrator if you require a hard copy document.
Document
Title:
Document Number
Version #:
Author
Problem Resolution Plan
1
Page Number
Kyle Martin
Active Date
2 of 3
26/08/2011
It is mandatory that the Project manager and Team leader be involved in the analysis however
team members will be involved in the analysis of the problem discussion of steps to find a
resolution.
If a core problem is found to be contributed to by an ill process that process will be subjected
to the quality assurance process improvement process found in section ….
1.1.3 Problem Prioritisation
Given the project is a university assignment the critical factor for the project will be time.
Any problems that arise will be prioritised based on their impact on the schedule; the
different levels of prioritisation are as follows:



Critical: The critical path will be impacted if not addressed
Moderate: Work activities are being impacted but the critical path will not be
affected.
Minor: One time impact and critical path will never be affected.
1.1.4 Problem Processing
Once the above sections have been completed a problem will be defined using Table 1
Problem Summary Template. Once a problem is defined this initiates the problem resolution,
problems will be dealt with in order of their problem priority detailed in section 1.1.3
Problem
ID
1.
Risk Index
(Priority)
Resolution Activities
Resources
Required
Table 1 Problem Summary Template
WARNING: Google Project controls all documents. Printing this document will result in an uncontrolled copy and will not be updated.
Contact the Administrator if you require a hard copy document.
Document
Title:
Document Number
Version #:
Author
1
Kyle Martin
Problem Resolution Plan
Page Number
Active Date
3 of 3
26/08/2011
WARNING: Google Project controls all documents. Printing this document will result in an uncontrolled copy and will not be updated.
Contact the Administrator if you require a hard copy document.