Page 9 - ADTM v 3.12_Neat

ADTM Risks & Risk Mitigation

th
(Ver 1.6, Last Update 16 July 2018)

The purpose of this document is to identify all Risks involved during the Life Cycle of the
Software Project.

The document is prepared based on Vendors experience with Clients and is aligned to the
ADTM.

Having identified the Risks, the Client and the Vendor have to jointly work out a plan to
overcome such Risks.

Risks once mitigated prevent project failure, delayed projects and cost over runs.

This document covers business continuity planning to some extent and the formulation of the
IT policy.

Risks Impact Solution
Non appointment of the No one is really Appoint Steering Committee
Steering committee or responsible and Vendor has after consulting all Senior
appointing employees with no authority over Management
no real commitment to the Clients Staff to implement
IT project project

During the Gap Analysis Project Delayed due to lack The Steering Committee
the key operational staff of information & thereafter should ensure all relevant
are not consulted software modifications and employees participate
re testing needed. especially operational staff
familiar with the manual
processes

Client not signing the Gap Vendor will develop However busy the client maybe
Analysis Software based on it is essential that he takes the
requirements that the time to meet the Vendor’s
Client has not agreed or development team and sign off
possibly not looked at. This the Gap Analysis
is similar to building a
house which an architect
has designed but the Client
has not agreed on the
design.

No Data Back ups In case of data losses due The IT policy must define the
to any reason the Client frequency of Data backups
will have no means to (most Organizations perform it
continue with the system. daily) and keep backups
This can lead even to a outside the Office.
complete halt in business

© Datama tion Systems (Pvt) Ltd. – 2019(Version 3.12) Page 8 of 11