Professional Documents
Culture Documents
In this file, you can ref useful information about quality management procedures such as quality
management proceduresforms, tools for quality management procedures, quality management
proceduresstrategies If you need more assistant for quality management procedures, please
leave your comment at the end of file.
Other useful material for quality management procedures:
qualitymanagement123.com/23-free-ebooks-for-quality-management
qualitymanagement123.com/185-free-quality-management-forms
qualitymanagement123.com/free-98-ISO-9001-templates-and-forms
qualitymanagement123.com/top-84-quality-management-KPIs
qualitymanagement123.com/top-18-quality-management-job-descriptions
qualitymanagement123.com/86-quality-management-interview-questions-and-answers
To describe how the quality of the project will be managed and what is required to
achieve this.
Quality Requirements
Quality Objectives
The following quality objectives will have to be fulfilled by the project.
Project related quality objectives:
The project will be completed according to the approved schedule as defined within the PMP
and any approved Change Requests.
The project will be conducted according to any and all associated contracts between Flinders
University and third party suppliers.
All project deliverables, including documents, code, test results, implemented systems and
hardware will be presented to the relevant project stakeholders for review and approval
according to approved delivery schedule.
The relevant project stakeholders will review deliverables in a timely manner allowing
updates and final approval within the approved delivery schedule.
Product related quality objectives:
The project stakeholder review is intended to ensure that the project deliverables meet all
approved specifications.
Procedure Requirements
The following table defines the Project Management procedures and deliverables that will be
used in the running of the project. Collectively these processes and procedures form the basis of
the quality plan that will be used on the project.
The Project Manager is responsible for ensuring that all relevant the project management
deliverables listed in the table below are created and applied for the project.
Procedure / Deliverable
Name
Project Management
Plan
Procedure Description
To capture the essence of the project in terms of project
profile, conditions, and planning and success criteria of
the project.
To clearly state the project scope boundaries for the
solution to be delivered (what is included, what is
excluded), and the related responsibilities.
Also includes:
Business Case
Identification of Stakeholders
Communication Plan
Deliverable Review and Acceptance Procedure
Work Break Down Structure
Project Organisation Structure and definition of
Roles and Responsibilities
Release Plan
Deliverable Review and Approval Process
To manage the scope of the project throughout its
lifecycle
To define the communication activities, roles and
responsibilities, frequency etc that are to occur
throughout the project.
To define the process in which procurement is
undertaken for the project. The procurement plan is
contained within the PMP.
To define the assignment for each individual on the
project Team.
To evaluate the success of a resource's assignment.
To serve as a reference for individual performance
assessment
To serve as a mechanism to record actual effort
spent on project tasks and for estimating effort
remaining to complete tasks.
To support project tracking of delivery schedule
and cost
To specify who will be responsible for managing
the project's risks and issues.
To specify the project's risk and issue management
process.
To specify the parameters to be used when
evaluating and classifying the project's risks and
issues
To rate the project in terms of pre-defined categories.
To record and track the financial performance of the
project.
Procedure / Deliverable
Name
Work Break Down
Structure
Key Decision Log
Change Requests
Change Request Register
Risks and Issues
Work Schedule
Project Completion
Report
Human Resource Plan
Development Process
Implementation Plan
Procedure Description
Refer PMP
To record and centralise key decisions
To formally document changes the project.
To provide information to facilitate stakeholders
making a decision regarding a change request
To formally document and keep track of a
requested change to the project.
To describe project risks, and document the
analysis and decisions taken on them.
To describe project issues, and what was done, is
being done, and will be done about to resolve them.
To track the project risks and issues.
To record, assign severity, assess and analyse, assign to
resources, record resolution and track defects found
throughout the testing process of a project.
To formally document and keep track of defects raised
throughout a project.
To provide an overall status on project performance
based on pre-established performance indicators, at
a pre-established frequency.
To facilitate the project control and decisionmaking processes
To organize and assign work items in accordance
with the selected release strategy identified in the
Master Plan
To establish the project schedule baseline and
progress tracking items
To communicate responsibilities for identified
deliverables
To evaluate the project with regard to its initial
success parameters.
To provide feedback to the client, stakeholders, and
members of the project team
To list the responsibilities of each resource within
the project team.
To describe when and how human resources will be
brought on and taken off the project team.
To identify the competency required for each
identified role.
To establish and communicate the activities that
will take place to develop the expected competence
from team members
To define the process to be followed to produce the
project deliverables. This process identified the quality
reviews actions that are to be undertaken and who
undertakes these reviews.
This process is defined within the PMP.
To plan production implementation and postimplementation activities.
To describe and quantify resources required to
implement the system.
To describe and quantify resources and that will
use, operate, support, and maintain the system once
implemented
This process is defined within the PMP.
==================
1. Check sheet
The check sheet is a form (document) used to collect data
in real time at the location where the data is generated.
The data it captures can be quantitative or qualitative.
When the information is quantitative, the check sheet is
sometimes called a tally sheet.
The defining characteristic of a check sheet is that data
are recorded by making marks ("checks") on it. A typical
check sheet is divided into regions, and marks made in
different regions have different significance. Data are
read by observing the location and number of marks on
the sheet.
Check sheets typically employ a heading that answers the
Five Ws:
2. Control chart
3. Pareto chart
5.Ishikawa diagram
Ishikawa diagrams (also called fishbone diagrams,
herringbone diagrams, cause-and-effect diagrams, or
Fishikawa) are causal diagrams created by Kaoru
Ishikawa (1968) that show the causes of a specific event.
[1][2] Common uses of the Ishikawa diagram are product
design and quality defect prevention, to identify potential
factors causing an overall effect. Each cause or reason for
imperfection is a source of variation. Causes are usually
grouped into major categories to identify these sources of
variation. The categories typically include
People: Anyone involved with the process
Methods: How the process is performed and the
specific requirements for doing it, such as policies,
procedures, rules, regulations and laws
Machines: Any equipment, computers, tools, etc.
required to accomplish the job
Materials: Raw materials, parts, pens, paper, etc.
used to produce the final product
Measurements: Data generated from the process
that are used to evaluate its quality
Environment: The conditions, such as location,
time, temperature, and culture in which the process
operates
6. Histogram method