Contents 3
Tables 6
About This Jeopardy
Report 7
History 7
Review 7
Introduction 7
Purpose 7
Description of
Jeopardy 7
Current Situation 7
Consequences of the
Jeopardy 7
The Available Options 7
Option 1 – <Title> 7
Option 2 – <Title> 7
Options Appraisal 7
Option 1 – <Title> 7
Step 1.Schedule Impact 7
Step 2.Resource Impact 7
Step 3.Product Functionality 7
Step 4.Risks 7
Step 5.Project Costs 7
Step 6.Dependencies 7
Step 7.Success Factors 7
Option 2 – <Title> 7
Step 1.Schedule Impact 7
Step 2.Resource Impact 7
Step 3.Product Functionality 7
Step 4.Risks 7
Step 5.Project Costs 7
Step 6.Dependencies 7
Step 7.Success Factors 7
Recommendations 7
Additional Information 7
<SECTION BREAK
to avoid header/footer and page setup problems do not remove the carriage
return following this line>
Table
1 Revision History 7
Table
2 Revision Review 7
<SECTION BREAK
to avoid header/footer and page setup problems do not remove the carriage
return following this line>
Author: <Author Name>
<Organization>
Change Authority: <Change
Authority>
Reference Number: <Document reference number>
Table 1 Revision History
|
Version No. |
Issue Date |
Status |
Reason for Change |
|
<1.0> |
<dd-mmm-yyyy> |
<Draft,
Released> |
<First
release, update, etc.> |
|
|
|
|
|
Table 2 Revision Review
|
Reviewer’s Details |
Version No. |
Date |
|
<Name> <Organization> |
<Version
number> |
<dd-mmm-yyyy> |
|
|
|
|
Change Forecast: <High/Medium/Low>
This document will be kept under revision
control.
A printed copy of this document is considered
uncontrolled.
<SECTION BREAK
to avoid header/footer and page setup problems do not remove the carriage
return following this line>
<A statement of the purpose of the Jeopardy
Report when functionality, time scales or costs for an approved phase or
project schedule are forecast to exceed their late finish dates. The following
is a “standard format” that may be used or adapted by the Project Manager.>
[example]
This document has been produced to notify the
Project Sponsor of a significant deviation from the approved project
schedule. Its purpose is to provide
sufficient information for the Project Executive to give direction, premature
closure of the project, creation of a revised project schedule or other
appropriate action.>
<SECTION BREAK
to avoid header/footer and page setup problems do not remove the carriage
return following this line>
<A full description of the jeopardy is to be entered here, with
details of the deviation and cause, being resource, product delivery,
functionality, time frame or cost etc., including why it is within the remit of
the project. If there are multiple jeopardy's at this time that are not linked,
then separate documents should be produced.
If the jeopardies are linked, and the resolution is common, then separate
sections may be used.>
Facts
Cause
Actions
Already Taken
Description
of Needed End Result
<The
impact the deviation has on the Phase, Project and any other interfaces.>
Impact
on schedule
Impact
on costs
Impact
on resources
Impact
on Products
Other
Impact
Document
references used for this jeopardy
<State
which documents, reports, meeting information, etc. the jeopardy is based.>
<A
list of the options that have been considered to get the phase or project
schedule back on course. A minimum of two options should be considered.>
<A
description of Option 1.>
<A
description of Option 2.>
<The
effect each option has on the original schedule, resources, product
functionality, the risks and project costs.>
<Firm recommendations by the Project Manager, based on the
information contained in this report.>
Description
of recommendations
Strategy/plan
of action proposed to overcome jeopardy
Deadlines
<Add any additional information to be
brought to the Project Executive's attention.>
<SECTION BREAK
to avoid header/footer and page setup problems do not remove the carriage
return following this line>