Quality Assurance Plan Template
Quality Assurance Plan Template
Quality Assurance Plan Template
Version <#.#>
This template contains a paragraph style called Instructional Text. Text using this paragraph style is
designed to assist the reader in completing the document. Text in paragraphs added after this help text is
automatically set to the appropriate body text level. For best results and to maintain formatting
consistency, use the provided paragraph styles. Delete all instructional text before publishing or
distributing the document Revision History.
This template conforms to the latest Section 508 guidelines. The user of the template is responsible to
maintain Section 508 conformance for any artifact created from this template.
Revision History
Date
Version
Description
Author
<Month> <Year>
Table of Contents
1.
Introduction..........................................................................................1
1.1.
1.2.
1.3.
1.4.
2.
3.
Purpose...............................................................................................................1
Scope...................................................................................................................1
Definitions, Acronyms and Abbreviations......................................................1
References..........................................................................................................1
Quality Objectives...............................................................................1
Management.........................................................................................1
3.1. Organization.......................................................................................................1
3.2. Reviews...............................................................................................................2
4.
5.
6.
Documentation....................................................................................3
Standards and Guidelines..................................................................3
Documentation Reviews.....................................................................3
6.1.
6.2.
6.3.
6.4.
6.5.
6.6.
6.7.
7.
8.
9.
10.
11.
Artifacts...............................................................................................................3
Review Plan........................................................................................................3
Review Schedule................................................................................................3
Organization and Responsibilities...................................................................3
Problem Resolution and Corrective Action....................................................3
Tools, Techniques and Methodologies............................................................4
Quality Records..................................................................................................4
<Month> <Year>
1. Introduction
Provide an overview of the entire document.
<Month> <Year>
Purpose
This Quality Assurance (QA) Plan details the overall approach to quality assurance activities for
<Project Name>. This QA Plan documents how the project defines, implements and assures
quality during the software development process.
This QA Plan is a communication vehicle for the entire project team, including the project
manager, development manager, developers, test analysts, SQA analysts, technical writers,
functional analysts, other project teams, and users.
<Month> <Year>
Scope
Provide a brief description of the scope of this document. Include what Project(s) it is associated
with and anything else that is affected or influenced by this document. This section should detail
what items are considered to be in scope for the Project(s) and what items are considered out of
scope for this QA Plan.
<Month> <Year>
List or reference the project-specific definitions that impact this document in this section. Enter
additional project-specific definitions that further help support this document. If possible, avoid
duplicating definitions defined elsewhere in your project deliverables.
<Month> <Year>
References
Provide a complete list of all documents and other sources referenced in the Quality Assurance
Plan including all referenced policies and procedures.
<Month> <Year>
2. Quality Objectives
Reference the section of the Requirements Artifacts that deals with quality requirements.
<Month> <Year>
3. Management
<Month> <Year>
Organization
Describe the structure of the organization responsible for Quality Assurance. Process
Management Services is responsible for the process component of Quality Assurance. The
evaluation of the product should be done within the project (most notably by an independent test
team) and by joint customer/developer review. The following organizational items should be
included or referenced here:
<Month> <Year>
Reviews
<Month> <Year>
4. Documentation
Reference the Project Artifact Summary here for the list of documentation the project will
produce.
http://vaww.oed.wss.va.gov/process/Lists/Activities_Production/Project_Artifact_Summary.aspx
10
<Month> <Year>
11
<Month> <Year>
6. Documentation Reviews
12
<Month> <Year>
Artifacts
Identify the project artifacts that will be the subject of the review. These may include Joint
Customer-Developer, Technical, Process Reviews, Internal Technical and Management Reviews.
Artifacts are pieces of information that are produced, modified, or used by a process; define an
area of responsibility, and are subject to version control. An artifact can be a model, a model
element, or a document. Artifact templates can be found at:
http://vaww.oed.wss.va.gov/process/home.aspx
13
<Month> <Year>
Review Plan
Develop a Review plan. The Review Plan specifies the schedule, resources, and methods and
procedures to use while conducting a project review. The Review Plan details the various types
of reviews and identifies any external agencies that are expected to approve or regulate the
artifacts produced by the project.
14
<Month> <Year>
Review Schedule
Detail the schedule for the reviews. This should include reviews scheduled at project milestones,
as well as reviews that are triggered by delivery of project artifacts. This subsection may
reference the project or iteration plan.
15
<Month> <Year>
10
List the specific groups or individuals involved in each of the identified review activities. Briefly
describe the tasks and responsibilities of each. Also, list any external agencies you expect to
approve or regulate any product of the project.
16
<Month> <Year>
11
Describe the procedures for reporting and handling problems identified during project reviews.
17
<Month> <Year>
12
Describe any specific tools, techniques or methodologies that are to be used to carry out the
reviews identified in this plan.
18
<Month> <Year>
13
Quality Records
Describe the quality records and documentation that will be maintained during the project.
Quality records include documentation established and maintained to provide evidence of
conformance to requirements and to the effective operation of the quality management system
Examples of quality records are meeting agendas, meeting minutes, email correspondence,
attendance sheets, training certificates, review results, evaluation of suppliers, and more.
Documentation includes artifacts that are maintained as evidence of the software development
lifecycle practices. Examples of documentation include baselined work products, issue resolution
logs, summary of work product reports, and more.
Quality records shall be archived for three years. Documentation shall be archived for seven
years. Some applications may have additional regulatory requirements that govern quality
record and documentation retention. For instance, if your application can be classified as a
medical device, additional record retention requirements may apply. (Example - The FDA
retention period is the life of the product plus two years).
19
<Month> <Year>
20
<Month> <Year>
21
<Month> <Year>
9. Configuration Management
Reference the Configuration Management Plan, if available or describe the configuration
management techniques applied to quality assurance activities.
22
<Month> <Year>
23
<Month> <Year>
Versio
n
Description
Author
February 2015
1.5
Process
Management
November
2014
1.4
Process
Management
April 2014
1.3
Process
Management
December
2013
1.2
Correction to headings
Process
Management
March 2013
1.1
Process
Management
January 2013
1.0
Initial Document
PMAS Business
Office
24
<Month> <Year>