QUALITY and date of check: TBA Result: Recommended

QUALITY ASSURANCE

 

1.    
Purpose of Quality Assurance   

The focus of the
Quality Assurance is on the processes used in the project. The Quality
Assurance aims to ensure that the processes in the project are used effectively
to develop quality project deliverables. It involves following and meeting
standards, continuously improving project work, and correcting project defects.

 

1.2. The following Quality Assurance
log identifies:

 

The deliverable/project
processes subject to quality assurance.
The quality standards and
stakeholder expectations for that process.
The quality assurance
activity –  A suitable review for
the project/deliverable process will be executed to monitor that the
selected processes are properly followed to an adequate standard.
When will quality assurance
activity will be performed and how often it will be performed.
The name of the person within
the project that is responsible for carrying out and reporting on the
quality assurance activity.

 

The following log is a description of how
the quality assurance log should look like and how the data represented within
the Quality assurance log should be represented. This will be used as a
reference in the case that another individual within the project is assigned to
Quality Assurance Log.

 

Project
Process/ Deliverable Process

Process
Quality Standards/
Customer
Expectations

Quality
Assurance Activity

Frequency of Quality assurance check

 
Participants

Example:
Review functionality of X added into the system

System requirements specification.
 
Requirements of the system have completely and
accurately captured

Code Review of functionality of X

At regular intervals during the collection of stages
that a new functionality is added

Name – Role

 

1.3.               
Quality Assurance Activities

 

 

1.3.1.      Project timeline check

 

Project
timeline check will be conducted in order to
measure the application of the approved Project Plan and discover deviations
that can be negative for the project, such as whether the deliverables were
done on time or whether an issue has been caused by a deliverable.

 

Frequency and date of check: TBA  

Result:  Recommended
actions.

Participants:      Name – role

Comments: Reasons of why issue or
delivering of a functionality wasn’t met

Documentation: see Project Timeline Check Report

 

1.3.2.      Project Review

 

Project Reviews will be conducted in order
to discover any deviations from and/or risks related to time, schedule, scope
etc. which can threaten the project and/or the outcome of the project.

 

Frequency and date of check: TBA

Result:  Recommended
actions.

Participants:      Name – role

Documentation: see Project Review Report

 

 

 

 

1.3.3.            Quality Check

 

Quality Check will be conducted in order to
measure the deliverables to the application of the approved Quality Plan and to
check whether there are issues or deviations that can be bad for the project
and/or the outcome of the project.

 

Frequency and date of check: TBA

Result:  Recommended
actions.

Participants:      Name – role

Documentation: see Quality Check Report

 

 

1.3.4.            Review

A Review may be called for by anyone in the
project in order to verify that a process or activity is sufficient for its
purpose and is applied and followed, the following procedures will be followed
to ensure that the Review Report produces the correct recommended actions.
The Review Report will be logged.

 

Date of the Review: TBA

Result:  Recommended
actions.

Participants:      Name – role

Documentation: see Review Report