QUALITY ASSURANCE 1.
Purpose of Quality Assurance The focus of theQuality Assurance is on the processes used in the project. The QualityAssurance aims to ensure that the processes in the project are used effectivelyto develop quality project deliverables. It involves following and meetingstandards, continuously improving project work, and correcting project defects. 1.2. The following Quality Assurancelog 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 howthe quality assurance log should look like and how the data represented withinthe Quality assurance log should be represented. This will be used as areference in the case that another individual within the project is assigned toQuality 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 Projecttimeline check will be conducted in order tomeasure the application of the approved Project Plan and discover deviationsthat can be negative for the project, such as whether the deliverables weredone on time or whether an issue has been caused by a deliverable. Frequency and date of check: TBA Result: Recommendedactions.Participants: Name – roleComments: Reasons of why issue ordelivering of a functionality wasn’t metDocumentation: see Project Timeline Check Report 1.3.2. Project Review Project Reviews will be conducted in orderto discover any deviations from and/or risks related to time, schedule, scopeetc. which can threaten the project and/or the outcome of the project.
Frequency and date of check: TBAResult: Recommendedactions.Participants: Name – roleDocumentation: see Project Review Report 1.3.3. Quality Check Quality Check will be conducted in order tomeasure the deliverables to the application of the approved Quality Plan and tocheck whether there are issues or deviations that can be bad for the projectand/or the outcome of the project. Frequency and date of check: TBAResult: Recommendedactions.Participants: Name – roleDocumentation: see Quality Check Report 1.
3.4. ReviewA Review may be called for by anyone in theproject in order to verify that a process or activity is sufficient for itspurpose and is applied and followed, the following procedures will be followedto ensure that the Review Report produces the correct recommended actions.The Review Report will be logged. Date of the Review: TBAResult: Recommendedactions.Participants: Name – roleDocumentation: see Review Report