File 44417

8/8/2019 File 44417

http://slidepdf.com/reader/full/file-44417 1/4

Project Quality Plan

Project Details

Note: Additional document completion guidance is included as hidden text. The text can berevealed (or hidden) by selecting the Tools menu, Options and select the View tab. Under

Formatting marks, check the Hidden Text box.

Project Name

SRO (Sponsor)

Project Manager Group/Directorate Start Date Completion Date

Document Details

Version Status(Draft or Approved)

Date Author/Editor Details of changes

Purpose of the Project Quality PlanThis document defines the quality expectations the project must achieve and how they will be met.It describes the qualities that must be possessed by the project’s outputs in order that the desiredoutcomes are achieved. It also describes the quality aspects that apply to the processes to beused in the project to create the desired outputs and outcomes.

This document does not say precisely who is doing what activities on what day to manage quality:that information should be defined in the Project Plan (and/or more detailed Stage/Team Plans if they exist).

Quality expectations for this projectGeneral statement(s) about the standards and level of quality expected to be achieved by theproject. This will usually be defined by the Senior Responsible Owner/Sponsor during projectstart-up and may be drawn from the Project Brief.

Acceptance criteriaA set of specific, measurable criteria that the customer/user will use to measure whether or not theproject is complete and successful and will hence form the basis for signing acceptance.

of 4

8/8/2019 File 44417



Acceptance criteria

Deliverables and interim productsA list of the outputs from the project (it’s deliverables ) plus any ‘stepping stone’ interim productsthat must be built to enable the deliverables to be built (eg procurement documentation, test plans,submissions).

Standards that apply to deliverables and processesAll standards, specific technologies and approaches that must be complied with (plus anexplanation why standards that should apply have been waived for this project).Eg:Local site standards.Departmental standardsCorporate standardsNational standardsEuropean standardsInternational standardsBetter regulation standardsDocumentation standardsWeb site standards

IT standardsTesting and acceptance standardsProject/Programme management standardsProcurement standardsBuilding construction standardsFinancial management standardsGovernance standards

Quality ResponsibilitiesA list of who is responsible for monitoring and ensuring quality for different aspects of the project.This will include responsibilities of those in the project team plus any external qualityresponsibilities (eg external Quality Audit/Assurance).

Quality control and audit processes applied to deliverables

and interim products

of 4

8/8/2019 File 44417



Quality control and audit processes applied to deliverablesand interim products

- to ensure that the desired qualities are built in the products/deliverables (eg design techniques,development methodologies, peer reviews, interim quality reviews, proof reading)

- to test that products meet their quality criteria and are fit for purpose. (eg various type of testingincluding user acceptance testing, inspections, quality reviews)

- to obtain sign-offs from all relevant parties- to audit the product development and quality management processes.

Quality control and audit processes applied to project

management

Description of the processes that will be used:- to ensure that project documentation is reviewed by appropriate stakeholders at the

appropriate times in the project lifecycle (this will include a definition of which projectdocuments will be produced for this project based on local standards and the nature of theproject).

- ensure that the project is being managed with sufficient rigour (this might include use of mentoring, peer review of documentation, project assurance and informal health-checks).

- to audit the project management processes (eg might include Formal Project Audits and OGCGateways).

Quality control and audit processes applied to projectmanagement and suppliers

Description of the processes that will be used to ensure that:- requirements for any work to be done or products to be supplied under contract are properly

specified and that procurement processes are fit for purpose- suppliers are managed by the client with appropriate rigour

- suppliers are managing their work as agreed (eg they are following agreed standards andprocesses)

- suppliers are applying quality controls as agreed (eg quality audits, documentation audits)- suppliers are maintaining documentation and audit trails as agreed.

Change control procedures

of 4

8/8/2019 File 44417



Change control procedurestaking action on issues such as requests for changes and faults/off specifications. This should

include levels of authorities and delegated limits that the project board/project sponsor/SRO hasagreed for approving changes or fault fixes.

Where external suppliers are being used the procedures should differentiate betweenchanges/fixes that are purely within the client domain and those that must involve both client andsupplier in analysis and decision-making.

Document management proceduresA description of the ‘configuration management scheme that will apply in the project:

- which specialist documents need to controlled under the scheme- which other types of specialist products will have configuration records maintained under the

scheme (eg new physical assets purchased or developed by the project (eg specialistequipment), ICT components H/W and S/W)

- which project management documents will be formally controlled- where documents will be located

- how document will be identified (eg naming convention, types of status, versioning)- processes for such things as submission of new/updated items to the library, baselining,

version control, issuing copies to individuals, publication (eg via Intranet), security protection,updating, archiving, deletion

- who will have responsibility for management of the document library.

Tools and techniques to help manage quality (eg software,design techniques)Any specials tools, techniques or approaches appropriate to the types of product being developedin this project (eg tools to measure a web site against accessibility criteria).

of 4

File 44417

Documents

Transcript of File 44417