Content and scope of Step H

Step H is an important step to all DIRKS projects.

Overview
Aims of Step H
Summary of Step H
Why should you do Step H?
How is Step H scalable?
Relationship to other steps

Overview

This section is an introduction to Step H: Post implementation review. It:

outlines the aim of Step H
summarises the major elements of Step H
explains why it is important to undertake Step H for particular DIRKS projects
indicates how Step H is scalable, and
shows how Step H relates to the other steps in the DIRKS methodology.

Aims of Step H

The aims of Step H are to:

measure the effectiveness of the recordkeeping system or system components, after they have been implemented
identify and take corrective action where it is required
evaluate the efficiency and appropriateness of the system development process and implementation, and
establish and implement an ongoing monitoring regime for the duration of the system.

Summary of Step H

Step H involves the planning and implementation of both:

set reviews of the system and development process, and
ongoing monitoring regimes.

Planning involves deciding:

what is required for ongoing monitoring
how and who will perform ongoing maintenance
when post implementation reviews should be conducted
the scope of reviews
what criteria should be used in reviews for evaluation
how projects will be evaluated and by whom.

Measurement techniques for reviews or monitoring can include:

interviewing management, staff and other stakeholders
conducting surveys
examining documentation developed during the earlier phases of the systems development project, and
observing and randomly checking operations.

Ongoing changes to systems or tools should be documented when they are made. The findings from reviews should be documented in a manner that can be used for comparative purposes in the future. Needs for corrective action highlighted in ongoing monitoring or a review should be prioritised and acted on.

Why should you do Step H?

Your DIRKS project has involved an investment of resources, in terms of time, money, staff and goodwill. It is important to demonstrate to management and other stakeholders with a vested interest in organisational accountability that:

the developmental process has been conducted efficiently, and
the recordkeeping system has the capacity to deliver its stated benefits in the short and long term.

A post-implementation review can provide such assurance.

In addition, by completing the initial post-implementation review and developing ongoing monitoring strategies you will:

help guarantee a continuing return on the organisation's investment by maintaining the recordkeeping system to optimal levels of performance throughout the system's lifecycle
have objective proof that your organisation is creating and managing appropriate evidence of its business activities in accordance with operational, accountability and community expectations
minimise your organisation's exposure to risk through system failure, and
over time, anticipate significant changes in recordkeeping requirements and organisational needs that necessitate a new developmental cycle.

Tip: If you fail to plan, you plan to fail
If in the rush to implement a new system your organisation fails to realise the importance of planning for ongoing monitoring, measuring system effectiveness and the effectiveness of the development process, you can jeopardise the entire endeavour. Faults may go undetected or untreated and system users may become increasingly disgruntled. The project may ultimately fail as a result. In addition, lessons learnt and knowledge gained as part of the implementation may not be available to future projects. Strategies for review and ongoing monitoring are therefore essential.

How is Step H scalable?

The scale of the ongoing monitoring will depend on the scope of your initial project and what kinds of faults or problems are detected.

In terms of reviewing, you can choose to conduct a full review of all components of the system (people, processes, tools, technology) that you have implemented or you may decide to review elements of the project independently. The scale can be according to the needs, resources and priorities of your organisation.

Depending on the complexity of the system and the level of resources available, it may be appropriate to conduct risk assessments to determine the scope and emphasis of the post-implementation review.

Relationship to other steps