Impact Analysis Report 1.0.0

Sope

This document resumes all data generated with the Impact Analysis Report; in order to

produce a clear statement destined to Risk Analysis (Quantitative) assessment and then to give a proper answer the issue’s proposer (see post ). It will be distributed to all concerned parties for either the Change Board or reviewing the existing plans for producing the Exception Report.

In the Risk Governance document (see template) there will be set the threshold value for starting the second phase of this process (see post ).

Quality

The effectiveness can be measured with these parameters:

  1. Accuracy. All information is linked to its sources
  2. Clarity. Beside the indication of the actual status, a brief explanation has to be integrated with specific erences (verifying that those documents were updated and accessible to the reader)
  3. The following checks need to be strictly integrated with the existing documentation both on product and on plan – especially resources (skills, availability, costs).

Document structure

Distribution list

The content of this report shall be made public, being ready to offer all necessary explanations for the decisions taken.

Process description

This document will supply information for creating the Impact Analysis Report. After that, it depends upon the sort of “issue” (e.g. Request for Change or Off Specification  – see post ) for the next step. Usually as follows:

  1. Request for Change will be dealt by the Change Board
  2. Off-Specification requires some probations possibly in the production process (e.g. Plans), then reviewing test within the Quality (Acceptance Criteria).

RACI (who does what)

Operation desc./Roles [1] Spr PM BA SME TL Prd Stkhd
Chairing the “Issue & Risk” meeting

I

A

R

C

C

I

C
Asking (formally) for supporting documentation and or technical estimations

I

A

R

C

C

C

C
Chairing the meeting with stakeholders (customers, users, technical people)

I

A

R

C

I

I

C
Analyzing the status of items in order to evaluate the next step (Impact Analysis Register)

C

A

R

C

C

I

C
Describing the result of the completed analysis through the Impact Analysis Report

I

A

R

I

I

I

I
Making decisions about the next step (Change Management or Exception Report[i])

C

A

R

I

C

I

C

Registrar section

These are the key fields

Impact Analysis ID
Issue ID
Issue Type. RFC/OS (see post)
Issue’s Author
Stakeholders People involved in the process
Issue Description As stated / modified by the author
Priority To be set (see post about Triage ).
Severity To be set (based on the available allowances either time or budget)
Status Working / Pending / Close
Areas involved Notes
Quality impact: Reviewing the Test plans-Quality Management Strategy
Other requirements affected: Prioritization (Kano Model )
Other tasks affected: Both from the delivery date and resource allocation
Integration issues: Listing all components to be reworked and tested as described in the Impact Analysis Report
Life cycle cost issues The reference is made to the TCO
Strategical view Documents required
Involved/Reviewed Benefit: Business Case and/or Benefits Review Plan[ii]
Involved/Reviewed Risk: Risk Management Strategy[iii] / Quality strategy
Estimated costs Measurement Unit Notes
Estimated total effort: Labor hour / currency Including LoE
Estimated lost effort: Labor hour / currency Reworked items
Estimated schedule impact: Delay on delivery date Within tolerances
Additional cost impact: currency If any
Situation Resuming what has been assessed in the previous sections
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
  6. Resource allocation plans

Financial / Commercial domains

  1. Business Case (e.g. time to market)
  2. Cash flow
  3. Suppliers’ contracts
  4. Customer’s contract

Notes

References

This page has been produced on the basis supplied by:

www.processimpact.com/process_assets/impact_analysis.doc

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

[i] If the output – impact amount -  exceeds the set tolerances, the Exception Report http://www.magnone.eu/prince2-templates/exception-report needs to be more descriptive of the technical and commercial aspects).

[ii] It view notes about Prince2 (new) templates

[iii] It view notes about Prince2 (new) templates