Quality Plan for Sample Project

[Instructions for completing the quality plan are included in this template in italics. Delete these instructions before publishing your quality plan.]

Quality Requirements

[Explain what the measurable requirements are to ensure customer satisfaction. These requirements should have been determined with input from all stakeholders, especially those in the business areas.]


Quality Management & Organization

Quality management for this project conforms to the following organizational structure:

[Fill in the appropriate names and titles, and add additional positions as needed to show the structure of quality management for your project. Keep in mind that the QA reps should be outside the project team. It is not necessary, however, to have a quality manager outside the project team; in fact, the quality manager is usually the project manager.]

Quality Assurance Processes

[To complete this section of your quality plan, you must first define the quality checkpoints, based on the Princeton Development Methodology. Then you must determine what needs to be reviewed at each checkpoint and which review method will be used, and assign the reviewers. Be sure to include the appropriate business and technical resources in the reviews—for example, for the prototype review, be sure to include the business staff members who will be using the system; for the code review, be sure to include technical staff members who are familiar with the programming language and environment; for the database design review, be sure to include a data analyst or database administrator in addition to any programmer/analysts.

Use this template to document your quality assurance processes—explain the review methods on the first page, and list the deliverables, the chosen review methods, and the review participants and materials in the following table. A few review methods are described below, and a few sample entries have been made to show how it could be done for one deliverable. You can add additional review methods, change the sample review methods, or remove inappropriate review methods, as needed.]

There are several methods that will be used to ensure that the Sample Project project, and the application that results from it, adhere to appropriate quality standards:

·         Internal Project Reviews
These are project team work sessions in which the team reviews all deliverables for a phase before scheduling a methodology review.

·         Walkthroughs
These are group work sessions in which the walkthrough team validates the deliverable using previously defined scripts, presentations, question & answer sessions, and brainstorming sessions, if appropriate.

·         Inspections
These are reviews of a deliverable by the Executive Committee, or sometimes by an implementation team, for the purpose of inspecting and approving the deliverable.


QA Process


Presentation Materials


Validation Materials

Sign-off Authority

Sign-off Criteria


Application Blueprint

Project Team Review

Analysis team facilitator:

Application Blueprint, including models and descriptive documents; business cases

Project Team:

A script that can be used to demonstrate the business process.

Project Manager:

Application Blueprint should satisfy the business needs, and be ready to be presented to reviewers outside the project team.

Ready for outside walkthrough


Same as above

Methodology Review Team:

A script provided by the business team that can be used to demonstrate the business process.


Application Blueprint should be ready to be presented to the executive level for approval.

Ready for inspection


Project Manager:

Application Blueprint, including an executive overview, models and descriptive documents; business cases

Executive committee:

A script provided by the business team that can be used to demonstrate the business process.

Executive committee

The Application Blueprint defines a system that meets the business needs.

Ready for design stage

[Deliverable Name]









[Tip: To remove the italic formatting from the second paragraph in the three center columns, select the text and press the ctrl+spacebar keys. To delete the sample rows, use the Edit Cut command or button; Delete will only delete the text, leaving blank rows behind.]

Testing Strategy

This project will follow the standard Princeton testing strategy.

[If this project will not follow the standard testing strategy, include an overview here on what the strategy will be.]

Defect Repair Control

[Explain how you plan to minimize defects for your project. A defect is any occurrence contrary to specifications within a deliverable which has already been quality assured. A plan for efficient removal of defects could include such items as standardized reporting mechanisms, effective and up-to-date system documentation, etc.]


Configuration Management

[Describe the processes to be used for

Key Deliverables

[naming, storage, and maintenance of]

Software Storage

[what, where, how]

Security and Backups

[what, where, how, how often]

Version Control

[tool, process]

Integration Management

[Include information about integration requirements, such as security, job scheduling, output management, deployment issues, infrastructure, and architecture.]

Vendor Control

[This section is required only if you are working with a vendor, and would include purchasing and contracting conditions that must be met to ensure quality from the vendor.]



[This section is optional, and includes information on how team members will be trained in quality management techniques.]