Issue Management report 1.0.0

Scope

Completing the “Issue Management” process with the effective communication about the state of the current item, whenever the issue could have an impact on the existing plans and/or processes (e.g. Quality, learned lesson). For the other processes (e.g. Risk and Chance Management) this document can be spared, namely the stakeholders will be kept in the loop using the procedured set for the specific domain.

The effectiveness can be measured with these parameters:

  • Timeliness (no later than the same day of the Issue Management meeting). Earlier communications about the status are made either through the “Issue Management Register” and/or via e-mail.
  • Clarity. Beside the indication of the actual status, a brief explanation has to be integrated with specific references (verifying that those documents were updated and accessible to the reader)

RACI (who does what)

Operation desc./Roles[1] Spr PM BA SME TL Prd Stkhd
Assessment of the Impact analysis I A C C R C C
Acting within the existing plan C A C C R I I
Compiling the Report C A R I I I C

Document structure

Distribution list

This kind of information can be considered sensitive. Therefore, it depends upon the implemented “profiling policy” (see post). However, it is suggested to inform all the interested stakeholders as described in the “Communication Management Strategy”.

Registrar section

These are the key fields

Issue report ID
Issue ID
Impact Analysis ID
Issue Type. RFC/OS/PC (see post)
Date Of the report
Date of last update. Making references to document history
Author
Description As stated / updated by the author
Priority (see post about Triage ).
Severity As per Impact Analysis report
Status
  1. Accept
  2. Reject
  3. Defer or Grant Concession
Recommendation What it has been suggested for solving the problem or at least reducing the impact.
Decision Brief and clear explanation of what has been decided. Whether the decision is just about to escalate, all references shall be complete and updated
Approved by

Technical domains

  1. Integrated Master Plan / Schedule
  2. Stage / Work-package plan
  3. Product Description
  4. Quality management strategy
  5. Risk management strategy

Financial / Commercial domains

  1. Business Case (time to market)
  2. Cash flow
  3. Suppliers’ contracts

References

Notes

[1] Spr Sponsor, PM Project manager, BA Business Analyst, TL Technical Leader, Prd Producer, Stkhd Stakeholder