1.

Quality Management in Agile Projects

1.1 Purpose

The quality plan consists of procedures, techniques and tools used to ensure that a product
meets the requirements specified in the software requirements specification. This plan:

1. identifies the responsibilities of the project developer,

2. lists the activities, processes and work products that will be reviewed and audited
3. Identifies the work products.

The portions of software life cycle covered by this plan are:

1. Software requirements specification

2. System architecture design
3. System detailed design
4. Encoding
5. Testing and Integration
6. User’s Manual

Software quality assurance will be implemented throughout the entire life cycle of the project,
until the release of the software product.
Figure 14 Software Quality Assurance Throughout Project

1.2 Responsibilities

The responsibilities of the developer (contractor) include:

1. Developing all the necessary documents involved in the software life cycle. This
includes developing the software requirement specification, the quality plan and cost
estimation of the project.
2. Developing the design plan of the project.
3. Implementing and testing the solution
4. Presenting documents and artefacts at the end of each phase to all stakeholders for
review.

1.3 Documentation

The essential documents required are described below:

1. Software requirements specification:

The software requirements specification lists the requirements of a system and it should
correctly describe the system requirements. It specifies the functionality and performance of
the project in terms of speed, reliability etc. It describes how the system interacts with the
people using it and also specifies the design constraints and standards to be followed.

2. Software verification & validation plan

The purpose of this document will be to develop and record formal procedures for the
verification and validation of the software.

3. Software architecture (design) document

This document describes the overall structure of the software. An object model will be
constructed using rational rose which will describe the various classes used in the project.

4. User Documentation

The user documentation will consist of:

 User manual, which will identify all error messages and program limitations along with
their corrective measures.
  Source code and testing code along with any other files used

The following documents will be provided at the end of each phase by the developer
(contractor):
Phase I : Software Requirement
1. Project Overview
2. Software Requirements Specification
3. Gantt chart of Project plan
4. Cost Estimate
5. Prototype of the software
6. Software quality assurance plan

Phase II: Software Design

1. Formal Requirement Specification

2. Architecture design
3. Test plan
4. Implementation plan

Phase III: Software Implementation

1. User Manual
2. Testing Evaluation
3. Project Evaluation
4. Source Code

1.4 Reviews and Audits

Quality Assurance for this project will include at least one review of all current work in each
stage of development of Requirement, Design, and Implementation. There will be timely
reviews of the current work. There will be three formal presentations held at the end of each
phase of requirement, design and implementation.

1.5 Tests
A software test plan will be developed which will outline the test activities required for testing.
Test results will be documented and they will be sufficient to demonstrate that the software
requirements have been met.