The Importance of Quality Assurance (QA) in IT Project Implementation

There is a Nigerian proverb that says ‘the tortoise cannot make any progress until it sticks its neck out’ I am sticking my neck out to share this article with you and hope to have your comments so that I make more progress.

IT project implementation quality assurance refers to the tools, processes, practices that are independently applied during or after implementing an IT project, to ensure that the project is delivered within scope, budget, time and agreed quality standards will be met. As the old adage says, ‘ prevention is better than cure’, preventive quality assurance is better than ‘after implementation’ QA.

Quality refers to the extent to which the project is fit for purpose from the users’ perspective. Two quality dimensions are important, the project output and the project delivery process which are the core concerns of the end user and project management respectively. Process quality is a major contributor to output quality, and is the focus of this article.

The independence of the assurance ‘consultant’ is key as it contributes to objectivity and focuses on helping the customer mitigate risks associated with project delivery. Risk based QA considers areas with highest risk as determined by each organisation. IT project implementation QA is typically made up of the following components:

Project Management
Technical installation and configuration of the application software
Hardware and network installation and management
Skills transfer and Stakeholder Management

Based on our experience with many customers across Africa, IT project implementation quality assurance is an absolute must. The size of the project, technology stack or application software does not matter. The work can be performed by external consultant or by internal resources who are not involved in the project. Some large organisations have project management offices that provide QA to their own projects. Effective QA usually requires specialist knowledge of the software and products being implemented, underlying business processes and testing best practices.

The Importance of QA is to;

Helps customers understand risks associated with implementing solutions that have complex applications and products.
Mitigate the proactively identified risks
Help to ensure successful implementation
Provides early detection of unexpected problems that may increase project costs

QA helps answer questions that include:

1. Project Schedule and Budget

Will the project deliver on schedule?
Does the schedule show all key tasks and deliverables in a logical sequence?
How do you identify and mitigate risks?
Is the budget adequate and available for the project?
Is project governance adequate and appropriate considering the complexity and risk associated with the project?

2. Business Needs

Is the problem to be solved by the implementation clear?
Does the system design support business requirements?
Is the system adequately tested?
Are there adequate internal controls built into the system and processes? This will include system access, segregation of duties

3. Stakeholder Management and Training

Are all key stakeholders aware, supporting and committed to the success of the project?
How is the change brought about by the project communicated?
What training is required?
How will the system be supported?

4. Technical Infrastructure