Project Delivery Process D488

Blog: Biz-Performance, David Brown

D488 Final Gap Analysis

DEFINITION

Analysis of the “gap” between the final design and the original requirements.

SUMMARY

A final analysis of the business solution that evolved during the prototyping process in comparison with the originally stated business needs. Consequences of any shortfall will be analysed and agreed. Any appropriate action will be reviewed and agreed.

PATH PLANNING GUIDANCE

Optional

DEPENDENCIES

Prerequisites (Finish-Finish):

Completion of all design tasks (D3xx / D4xx)
Consolidate prototyping results (D471)
Resolve outstanding policy issues (D481)

Dependent procedures (Finish-Start):

Finalisation of development (D6xx / D7xx)
Systems Testing (D8xx)

RECEIVABLES

All design information – Implementation Papers
Definition of Requirements (DoR)
Approved Change Requests

DELIVERABLES

Final Gap Analysis

TOOLS

none)

DETAILED DESCRIPTION OF TASKS

When all aspects of the design have been finalised, the results from the prototyping processes have been consolidated and outstanding issues resolved, a final analysis is performed to catalogue any defined requirement which will not be fully addressed in the overall business solution. Normally there will be no further action identified at this time as the design would not have been finalised if known design shortfalls had not either been addressed or accepted by the client organisation.

The overall design is mapped against the defined requirements in the Definition of Requirements (as modified by any authorised changes). Any aspects not fully addressed are listed along with a brief explanation of the issues involved and the reason behind their omission.

The Final Gap Analysis should be presented to the project sponsor for approval. There should be no surprises as all decisions should already have been agreed by the client organisation. If actions are identified, they should be addressed immediately before finalising the Final Gap Analysis.