Shopping insurance

Quality Assurance/ Quality Control (QA/ QC)

Posted on 08. May, 2010 by admin in Uncategorized

Quality Assurance/ Quality Control (QA/ QC):

 

GUIDELINES FOR THE POME QUALITYASSURANCE PLAN CHECKLIST:

This checklist is provided as part of the evaluation process for the Quality Assurance Plan.  The checklist assists designated reviewers in determining whether specifications meet criteria established in POME’S Project Development Methodology (POMEPDM).  The objective of the evaluation is to determine whether the document complies with POMEPDM requirements.

Mentioned below is the DOCUMENT REVIEW CHECKLIST.  Its purpose is to assure that documents achieve the highest standards relative to format, consistency, completeness, quality, and presentation.

Submissions must include the following three documents, and must be presented in the following order:  (First) Document Review Checklist, (Second) the Quality Assurance Plan Checklist, and (Third) the Quality Assurance Plan.

 

The Quality Assurance Plan (QAP) presents a framework for activities, which when followed, will ensure delivery of quality products and services.  The SDM provides the project standards and procedures to be used as the basis for the QA group’s reviews and audits.

Document Review Checklist:

 

To be completed by Author

To be completed by Reviewer

REQUIREMENT

AUTHOR X‑REFERENCE Page #/Section #

AUTHOR COMMENTS

COMPLY

REVIEWER COMMENTS

Y

N

1.0  GENERAL INFORMATION

1.1

Purpose: Describe the purpose of the Quality Assurance Plan.

 

 

 

 

 

1.2

Scope: Describe the scope of the Quality Assurance Plan as it relates to the project.

 

 

 

 

 

1.3

System Overview: Provide a brief system overview description as a point of reference for the remainder of the document, including responsible organization, system name or title, system code, system category, operational status, and system environment and special conditions.

 

 

 

 

 

1.4

Project References: Provide a list of the references that were used in preparation of this document.

 

 

 

 

 

1.5

Acronyms and Abbreviations: Provide a list of the acronyms and abbreviations used in this document and the meaning of each.

 

 

 

 

 

1.6

Points of Contact:

 

 

 

 

 

 

1.6.1         Information: Provide a list of the points of organizational contact (PoCs) that may be needed by the document user for informational and troubleshooting purposes.

 

 

 

 

 

 

1.6.2         Coordination: Provide a list of organizations that require coordination between the project and its specific support function (e.g., installation coordination, security, etc.).  Include a schedule for coordination activities.

 

 

 

 

 

Quality Assurance Plan Checklist:

 

To be completed by Author

To be completed by Reviewer

REQUIREMENT

AUTHOR X‑REFERENCE Page #/Section #

AUTHOR COMMENTS

COMPLY

REVIEWER COMMENTS

Y

N

2.0  SCHEDULE OF TASKS AND RESPONSIBILITIES

 

Based on the tasks described in your Project Plan, provide a schedule of the QA activities for the duration of the project.  Tasks may include, but are not limited to, those listed below:

 

Identify Standards and Guidelines
Evaluate Software Tools
Evaluate Facilities
Evaluate Software Products Review Process
Evaluate Project Planning, Tracking, and Oversight Processes
Evaluate Requirements Analysis Process
Evaluate Design Process
Evaluate Code and Unit Testing Process
Evaluate Integration Testing Process
Evaluate Acceptance Testing Process
Evaluate Release Process
Evaluate the Corrective Action Process
Evaluate Media Certification Process
Certify Non-deliverable Software
Evaluate Storage and Handling Process
Evaluate Deviations and Waivers Process
Evaluate Configuration Management Process
Evaluate Software Development Library Control Process
Evaluate Non-developmental Software
Perform Configuration Audits
Evaluate Risk Management Process

 

 

 

 

 

Quality Assurance Plan:

 

To be completed by Author

To be completed by Reviewer

REQUIREMENT

AUTHOR X‑REFERENCE Page #/Section #

AUTHOR COMMENTS

COMPLY

REVIEWER COMMENTS

Y

N

3.0  SYSTEM DOCUMENTATION

3.1

Documents by Phase: List and briefly describe the documentation expected to be produced during this project.  Depending on the size of your project, this may include, but is not limited to, the documents in the following subsections:

 

 

 

 

 

 

3.1.1         Initiate Phase:

Needs Statement
Project Plan (including WBS)
Configuration Management Plan
QualityAssurance Plan
Feasibility Study
Cost/Benefit Analysis
Risk Analysis

 

 

 

 

 

3.1.2         Define Phase:

System Support and Acquisition Plan (initial)
Functional Requirements Document
Data Requirements Document
System Security and Privacy Plan
Internal Audit Plan
Project Plan (updated)

 

 

 

 

 

3.1.3         Design Phase:

System/Subsystem Specifications
Database Specifications
Program Specifications
System Support and Acquisition Plan (final)
Validation, Verification, and Testing Plan (initial)
Training Plan (initial)
Project Plan (updated)

 

 

 

 

 

 

 

To be completed by Author

To be completed by Reviewer

REQUIREMENT

AUTHOR X‑REFERENCE Page #/Section #

AUTHOR COMMENTS

COMPLY

REVIEWER COMMENTS

Y

N

 

3.1.4         Build Phase:

Installation and Conversion Plan (initial)
Test Plan
User’s Manual
Operations Manual
Maintenance Manual
Validation, Verification, and Testing Plan (final)
Training Plan (final)
Project Plan (updated)

 

 

 

 

 

3.1.5          Evaluate Phase:

Test Results and Evaluation Reports
Installation and Conversion Plan (final)
Project Plan (updated)

 

 

 

 

 

3.1.6         Operate Phase:

Pilot Test Results
Training Material
Project Plan (updated)

 

 

 

 

3.2

Discipline for Documentation Standard Practices: Describe the criteria that will be applied during review and evaluation of all lifecycle documents.

 

 

 

 

 

 

 

To be completed by Author

To be completed by Reviewer

REQUIREMENT

AUTHOR X‑REFERENCE Page #/Section #

AUTHOR COMMENTS

COMPLY

REVIEWER COMMENTS

Y

N

4.0  REVIEWS AND AUDITS

4.1

Review Process: Define the steps of the review process and the procedures that will be used to conduct reviews.

 

 

 

 

4.2

Formal Reviews and Audits:

 

 

 

 

 

4.2.1         Lifecycle Reviews: Identify the types of SDM associated lifecycle or non-lifecycle reviews that will be conducted within each project lifecycle phase.  Include a schedule of reviews and include how the results of each review will be used on the project.

 

Typically, the lifecycle reviews include:

Requirements Review
Design Review
Specification Review
Preliminary Design Review
Critical Design Review
Test Readiness Review
Formal Qualification Review
Production Readiness Review
Acceptance Test Review
Post-Implementation Review

 

 

 

 

 

4.2.2         Audits: Describe the audits that will be conducted on the project and when they will be scheduled.

 

 

 

 

4.3

Informal Reviews: Outline the types of informal reviews that will be conducted.

 

 

 

 

4.4

Review Reports: Identify QA reports that will be produced throughout the project lifecycle and their uses.

 

 

 

 

4.5

Review and Audit Metrics: Describe the metrics that will be used to capture management information, and how they will be analyzed and reported.

 

 

 

 

 

 

 

 

To be completed by Author

To be completed by Reviewer

REQUIREMENT

AUTHOR X‑REFERENCE Page #/Section #

AUTHOR COMMENTS

COMPLY

REVIEWER COMMENTS

Y

N

5.0  TESTING

Identify the roles and responsibilities of the QA function in relation to testing throughout the various stages of the project.

 

 

 

 

6.0  PROBLEM REPORTING AND CORRECTIVE ACTION

Discuss QA responsibilities and activities concerned with the reporting and tracking of project-related problems and resolutions.

 

 

 

 

6.1

Problem/Issue Documentation: Explain how problems and issues will be documented.

 

 

 

 

6.2

Report Metrics: Describe how metrics from the above reports will be collected and analyzed to determine and coordinate corrective actions.

 

 

 

 

7.0  TOOLS

 

Describe the tools that will be used for QA and the methodology employed to implement usage of the mentioned tools.

 

 

 

 

8.0  PROJECT CONTROLS

8.1

Product Control: Identify how QA will monitor the methods and tools used to maintain and store controlled versions of system products.

 

 

 

 

8.2

Supplier Control: Describe the provisions for assuring that products provided by suppliers meet established requirements.

 

 

 

 

9.0  TRAINING

 

Identify the training activities that will be provided to meet the needs of QA on this project.

 

 

 

 

 

 

 

 

 

 

CHECKLIST FOR MANAGING OVER ALL PROJECT QUALITY

 

Yes

No

N/A

Remarks

Has the Quality Assurance role been identified and assigned an appropriate level of authority?

 

 

 

 

Are project standards and procedures being defined for each area of the project to ensure consistent delivery in accordance with the quality requirements?

 

 

 

 

Do the standards and procedures make reference to material in the knowledge base and simply note any project-specific additions, exceptions, or enhancements?

 

 

 

 

Are the standards and procedures in place prior to the commencement of the work to which they apply?

 

 

 

 

Are all team members adequately trained in the tools and standards and procedures for the project environment (or will additional start-up training be required)?

 

 

 

 

Is each member of the team personally committed to abide by the standards and procedures?

 

 

 

 

Is the team involved in the ongoing development and adoption of the standards (to promote a sense of ownership by the team)?

 

 

 

 

Are formal structured walk-throughs and reviews being conducted in accordance with the standards and procedures (e.g., the proper people attend, minutes are taken and distributed, and action items are assigned and followed up)?

 

 

 

 

Are appropriate test plans and procedures in place and being followed?

 

 

 

 

Will the deliverables being produced meet the user’s requirements?

 

 

 

 

Are records being kept by the Quality Assurance role of quality problems, recommendations and actions?

 

 

 

 

Are effective measurement techniques being used to identify the levels of quality and productivity being achieved and to provide a baseline for continuous improvement?

 

 

 

 

Is project data being analyzed to determine trends and norms and to identify when quality threshold or target levels are not being achieved?

 

 

 

 

Have quality improvement sessions been conducted between the Quality Assurance Manager and the project team to develop solutions to delivery problems and to explore opportunities for improvement?

 

 

 

 

Are corrective actions being monitored for effectiveness in eliminating the cause of problems?

 

 

 

 

In any cases where corrective action is not taken or is ineffective, has the problem been escalated to the Quality Management function outside the project team?

 

 

 

 

 

Subject

Quality Audit

Purpose

To manage project risk and provide suggestions for improvement through periodic review of progress and compliance with engineering methodology

Scope

All projects & renewals shall undergo quality audit to a level and frequency determined in accordance with this procedure

 

STEP

WHO

STEP NOTES

INPUT

-

Completed Engineering Methodology Qualification Tool, Engineering Balanced Scorecard template, Engineering Schedule, Engineering Plan, Risk Management Plan

1

Project Manager / Project Engineer

Determine scope & timing of planned audits

Refer to the completed Engineering Methodology Qualification Tool for the project to identify if Engineering Quality Audits are mandatory or optional for the project.  The qualification tool determines this based upon the assessment of technical risk & complexity and project duration.  Where audits are required, use the following guidelines to determine the broad scope of planned audits for the project.  Once agreed, identify the proposed Audit regime / dates in the Project or Engineering Schedule.

Notwithstanding the following guidelines, planned Quality Audits: Should not be performed more frequently than once per month
Are generally triggered by achievement of selected milestones
Scope and frequency should be based upon an assessment of engineering risk, agreed between the Project Manager and Project Engineer

For projects that are large AND either technically complex OR technically high risk (as determined by the Methodology Qualification Tool:
At each major milestone gate i.e.

Milestone Gate 1 – After Release of Scope to Design phase i.e. planning completed, design commenced
Milestone Gate 2 – After initiating the build process i.e. after commencing significant build, configuration or programming activities
Milestone Gate 3 – After initiating the Installation Process i.e. after commencing one or more significant installation activities

For any of the lesser milestones deemed at risk e.g.: Upon completion of Concept Design & Review
Upon completion of Functional Design & Review
Upon completion of Detailed Design & Approval
Start or completion of Head End Set up
Start or completion of Static Graphics
Start or completion of  Programming
Start or completion of off-site Assembly & Manufacture
Start or completion of Database (point) Building
Start or completion of Head End Configuration
Start or completion of Graphics Programming (dynamic point allocation)
Before commencement of Staging & FAT
During the Installation phase i.e. at key milestones through installation process
Before commencement of commissioning
Upon completion of Customer Acceptance testing
Upon project completion

For projects that are small AND technically “standard” AND low risk (as determined by the Methodology Qualification Tool)
Planned Quality Audits are optional
It is recommended that Project Managers select a random sample of projects and/or project engineers/technicians to be audited to give confidence that these types of projects are following appropriate engineering practice, and to help grow the engineering competency of team members who may not have benefited from recent involvement in large, high risk project audits.

Unplanned Quality Audits

Unplanned Quality Audits may occur at any stage in response to an undesirable event or major change e.g. Major process failure
Customer complaint
Change of key personnel
Major design change

2

Project Manager / Project Engineer

Identify suitable auditor

The selection of auditor should be agreed with the Team Leader, provided the Team Leader is not also the Project Manager for the project, or other local Operations Manager.  When selecting auditors, the following should be considered:

Independence - NOT directly involved in delivery of the project (e.g. not the Project Manager or Engineer for the project) and is not likely to be influenced
Competence - recognised for their knowledge and skill in the type of activities being audited
Observant & perceptive - able to identify things of greatest concern, to understand and adapt to the particular project circumstances
Persistent & thorough – but not pedantic or single-minded, able to evaluate efficacy of alternative approaches
Will often be a Project Manager, Team Leader or nominated Auditor from a similar business, but NOT from the project

For long duration, high risk projects, it may be beneficial to use a number of different auditors throughout the project life cycle.

Once the auditor has been agreed, ensure that they are informed of and available for the planned audit schedule / dates.

3

Project Engineer

Prepare for Audit

Gather the audit documentation and reference material including: Completed Engineering Qualification Tool and the Balanced Scorecard template for the project – to use to record the audit outcomes
Completed Balanced Scorecard from previous audit/s (where relevant) – to identify prior corrective actions or suggestions for improvement that should be reviewed
Copies of relevant procedures or procedure flow charts – to use as a prompt for things to look for, questions to ask, and to capture observations during the audit
Copy of the up-to-date project or engineering schedule – to show the current progress of the project and thus indicate the main focus of the audit

Ensure the Auditor receives the above information well in advance of the audit
Confirm the date and place where the audit is to take place and the persons to be in attendance
Ensure that those to be in attendance understand the scope of the audit and make arrangements to be able to provide the necessary evidence of conformance with relevant procedures & standards at the time of the audit

4

Auditor / Project Engineer

Conduct engineering audit

The Engineering Balanced Scorecard shall be used as the basis of recording the outcomes of the engineering audit, including:

Who conducted the audit
Which procedures were audited – the scope
Overall performance assessment against the requirements of relevant procedures
What objective evidence was sighted
Major observations, Corrective Actions or Suggestions for Improvement

For 2nd and subsequent audits, the Balanced Scorecard worksheet should be copied to a new tab in the workbook so that there is a separate scorecard worksheet for each audit performed.

The Scorecard is not an exhaustive list of questions & issues but should be used as an aide memoir or prompt to the auditor.  Likewise, copies of procedures and procedure flow charts should also be used as aids to memory; to help ensure that essential issues are not overlooked.  Where necessary the auditor may need to deviate from the content of the Scorecard to investigate an issue or concern with a view to establish if any corrective action is required.

The auditor should:

Review all outstanding Corrective Actions and Suggestions for Improvement form previous audits
Seek and record objective evidence of conformance with the requirements of the relevant procedures
Assess and score overall performance against each procedure relevant to the current audit.  Note that procedures targeted for the audit would be expected to include: All procedures identified as ‘applicable to the project’ AND included in the most recently completed milestone/s
Procedures identified as ‘applicable to the project’ AND included in the next or subsequent incomplete milestones WHERE the input or initiating event for the procedure has occurred.  In such cases, the procedure should be marked as ‘applicable to current project status’ and assessed accordingly.

Identify Corrective Actions or Suggestions for Improvement.  These should be recorded and used in a constructive manner to assist the project to effectively manage risk and deliver customer satisfaction.
Identify Best Practice examples and significant opportunities to improve the engineering procedures, tools and/or processes

5

Project Manager

Presentation of audit results & recommendations

The completed Audit Scorecard should be forwarded to the Engineer’s manager and the Project Manager.
Where the overall audit result falls below the accepted benchmark value, a Corrective Action OFI should be raised against the Engineer and the scorecard attached to the OFI.  The Scorecard prompts for this action when the result falls below the accepted benchmark.
Suggestions for improvement of the Engineering Methodology should be forwarded to the relevant Procedure Owner.  Suggestions for improvement will often arise from cases where the audit has identified performance as ‘above standard’ or ‘best practice’.

OUTPUT

-

Audit plan confirmed, Completed Engineering Balanced Scorecard, Suggestions for improvement of Engineering Methodology, Corrective Action OFI raised where appropriate.

 

Subject

Calibration (Inspection, Measuring and Test Equipment)

Purpose

Provide a means of calibration and maintenance of test and measuring equipment, to ensure that correctly performed measurements and inspections will yield accurate results.

Scope

Applies to all site  locations using Inspection, Measurement and Test Equipment.

 

Step

Who

Steps/Notes

1

Location Management Team

Identify resources in each location to manage and monitor the equipment Calibration Status Register and process.

2

Process Owner

Determine the equipment used for Inspection, Measuring and Testing for the location and include in the Calibration Status Register.  The Calibration Status Register includes the following information:

Model Number / Description
Serial Number
Date Checked / Date Due
Equipment Owner
Storage Location

Note that equipment used for “Indication Purposes Only” is not required to be recorded in the Calibration Status Register.  These items shall be marked as “Indication Purposes Only – Not Calibrated” or similar.  Adhesive labels are available from SETON for this purpose.

3

Process Owner

Any equipment found to be faulty is to have a Company Reject Tag affixed.

Equipment repairs are conducted in-house or sent to a subcontractor for repair is repair is a commercially viable option.

4

Process Owner

Remove test equipment from service if found to be beyond repair.

Faulty equipment is to be recycled, destroyed or disposed of by an approved method.

Update the Calibration Status Register and retain records of disposal for a minimum of two years.

5

Process Owner

Calibration shall be performed:

Periodically on or before the due calibration date
Following an occurrence which could have impaired the accuracy established at the last calibration
After any repair is carried out on the equipment
Following initial purchase of new equipment (where an adequate calibration certificate did not accompany the equipment).
Functional testing shall be performed on static wrist straps weekly or before use.
Static Mats shall be tested monthly.

In the case where a manufacturer specification does not exist a specific set of calibration specifications will be developed. Qualified technical personnel within Company using existing calibrated equipment shall calibrate the instrument.

6

Process Owner

Where required, equipment will be calibrated to manufacturers specifications by a laboratory whose standards can be traced to National or International Standards. Equipment requiring NATA certification shall be forwarded to a certified provider for compliance testing.

This may also be the case for the calibration of specialist equipment.

7

 

Process Owner

Where equipment is found to be outside the required calibration limits, corrective action is necessary. Evaluation should be made to determine the effects on completed work and to what extent reprocessing, re-testing, recalibration or complete rejection may be necessary. In addition, investigation of cause is important to avoid recurrence.

This may include review of calibration methods and frequency, training and adequacy of test equipment.

Where equipment is found to be out of calibration but continues to operate in a satisfactory way to provide safe limit indication, the unit may be placed back into service and used for indication purposes only.  Test equipment shall be deemed as used for indication purposes if it has been approved for that purpose by the authorised nominated person.

Where equipment is deemed as suitable for indication only, calibration labels must be removed and the equipment register updated to reflect the equipment’s status.

8

Process Owner

Calibrated equipment available for service will have a Company Calibration Status sticker affixed, clearly displaying the calibration details. Where possible, the equipment will be safe guarded from adjustments which would invalidate the calibration setting.

If this label is not present, or due date exceeded, the equipment shall be deemed un-calibrated.

Update the Calibration Status Register and maintain copies of the Calibration Reports or records from the Certified Calibration provider.

Note:

 

Testing of electrical equipment is to be carried out in accordance with Testing of electrical equipment procedures.

Checklist for managing project quality management processes in pome breakdown structure:

If your company is ISO certified, or if it aspires to be, product development projects should be done in accordance with ISO requirements. ISO compliance supports the implementation of project management disciplines and controls. If you implement good project management practices, you will be naturally ISO compliant, and if you implement ISO requirements you will end up enforcing many sound project management practices.

The purpose of the Quality Controller/ Quality Assurance (QC/QA) in the Projects is to determine the applicability of International Standards for ‘Guidelines Quality in Project Management’. The questionnaire refers to project management processes to enable a framework for QC/ QA to discuss their application. The questionnaire pertains to projects of varying complexity, small or large, of short or long duration, in different environments and irrespective of the kind of project product. The content of the questionnaire has been derived form the International ISO 10006:1997(E), made accordingly with the POME Methodologies.

 

Definition of Categories

C = Compliant, N = Non-compliant

P = Present, A = Absent, X = Not applicable

Project Characteristics Checklist Questionnaire

Document Identification

Document Result

[C/N/P/A/X]

Implementation/ Observation/ Comments

1.1

Do Project Management Processes exist for planning, organizing, monitoring and controlling all aspects of the project?

 

 

 

 

 

1.2

Is there an organization that decides to register/ undertake projects and then assign the project to a project organization?

 

 

 

 

 

1.3

Are projects divided into sub-processes/ phases?

 

 

 

1.4

Is there an organization responsible for monitoring the realization of the sub-process/ phase objectives and related risks?

 

 

 

Quality in Project Management Processes Checklist Questionnaire

Document Identification

Document Result

[C/N/P/A/X]

Implementation/ Observation/ Comments

Which project management processes exist (documented or not) within the organization e.g. cost, resource & time related processes

 

 

 

 

 

Do Project Management guidelines and processes exist with the organization/ project organization to ensure quality?

 

 

 

 

 

Quality Strategic processes Checklist Questionnaire

Document Identification

Document Result

[C/N/P/A/X]

Implementation/ Observation/ Comments

Have customer and stakeholders needs been clearly understood to ensure that all project-related processes focus meeting their needs?

 

 

 

 

 

Has/ is the project carried out as a set of planned and Interdependent processes?

 

 

 

Is the clear division of responsibility versus authority between the originating organization, project organization, customers and stakeholders?

 

 

 

Do project progress evaluations exist? If so what do they evaluate?

 

 

 

J

Do quality attributes exist within the Project Management Process? E.g. approvals, documentation, preventative & corrective action, reviews, traceability, training, verification, etc

 

 

 

Have management provided and organizational structure that is a conducive means to support the project objectives?

 

 

 

Does management makes project decisions based on data and factual information?

 

 

 

Has the project organization established beneficial relationships with subcontractors and other organizations?

 

 

 

Has a project manager been appointed and defined with accountability, authority and responsibility for managing the project?

 

 

 

10.

Has a system been put in place to collect and analyse the information gained during/ after a project for use in a continual improvement process?

 

 

 

11.

Have provisions been made for self-assessments or internal audits?

 

 

 

Interdependency Quality Management Processes Checklist Questionnaire

Document Identification

Document Result

[C/N/P/A/X]

Implementation/ Observation/ Comments

Who is responsible for managing all of the interdependencies amongst the project processes?

 

 

 

Project Initiation and project plan development Quality Checklist Questionnaire

Document Identification

Document Result

[C/N/P/A/X]

Implementation/ Observation/ Comments

Does an approved project and quality plan exist? If so is it kept up to date and by whom?

 

 

 

H

Has the project plan been prepared to allow for traceability (measuring and assessing objectives/ deliverables? If not, is there an alternative means of traceability?

 

 

 

Is the objective of the project to fulfil the requirements of a contract? If so are contract reviews performed?

 

 

 

Are project organizations determined assigned projects based on similar projects that have been previously undertaken?

 

 

 

Does the Project Plan consist of a Quality Plan/ Quality approach?

 

 

 

Is the retention of project related records managed?

 

 

 

Are reviews and progress evaluations included in the Project Plan? If so do these reviews include preventative/ corrective action measures?

 

 

 

What project interfaces exist? Are the identified in the Project Plan and how are they managed? E.g. liaison with customer/ stakeholders – reporting lines – functions within the project organization.

 

 

 

Interaction Quality Management Checklist Questionnaire

Document Identification

Document Result

[C/N/P/A/X]

Implementation/ Observation/ Comments

Over and above the project organization, does the project consist of project interaction teams?  E.g. risk management teams, measuring project performance, project communication.

 

 

 

Quality  Change Management Checklist Questionnaire

Document Identification

Document Result

[C/N/P/A/X]

Implementation/ Observation/ Comments

Does the project consist of a Change Management approach/ process?

 

 

 

Does the Change Management Process include a control mechanism for documentation?

 

 

 

Project Closure Quality Checklist Questionnaire

Document Identification

Document Result

[C/N/P/A/X]

Implementation/ Observation/ Comments

At project closure, are all the project records retained for a specified time?

 

 

 

At project closure, is a complete project review conducted? – Irrespective of the reason for project closure.

 

 

 

Project Quality Scope related process Checklist Questionnaire

Document Identification

Document Result

[C/N/P/A/X]

Implementation/ Observation/ Comments

How are the customer requirements translated into activities to ensure project objectives are achieved?

 

 

 

Concept Development Quality Checklist Questionnaire

Document Identification

Document Result

[C/N/P/A/X]

Implementation/ Observation/ Comments

Have the customer’s requirements for both product and processes (expressed and implied) been translated into documented requirements?

 

 

 

Do these documented requirements include stakeholder requirements, by which the customer has agreed upon?

 

 

 

Project Quality  Scope Development and Control Checklist Questionnaire

Document Identification

Document Result

[C/N/P/A/X]

Implementation/ Observation/ Comments

Has a project scope been developed?

 

 

 

Is there supporting evidence of alternative approaches and solutions?

 

 

 

Project Activity Definition Checklist Questionnaire

Document Identification

Document Result

[C/N/P/A/X]

Implementation/ Observation/ Comments

In the definition of activities, has the project manager/ project leader involved the personnel who are responsible for carrying out the activities?

 

 

 

Have the activities been defined in such a way that its outputs are measurable?

 

 

 

Project Activity Control Checklist Questionnaire

Document Identification

Document Result

[C/N/P/A/X]

Implementation/ Observation/ Comments

Are the activities defined, carried out in accordance to the project plan?

 

 

 

Have reviews been planned on the activities?

 

 

 

Are variations from the defined activities being updated on the Project Plan?

 

 

 

 

 

Time-related Quality processes Checklist Questionnaire

Document Identification

Document Result

[C/N/P/A/X]

Implementation/ Observation/ Comments

 

Does a time-related process exist to determine the dependencies and duration of activities to ensure timely completion of the project?

 

 

 

 

Activity dependency Quality planning Checklist Questionnaire

Document Identification

Document Result

[C/N/P/A/X]

Implementation/ Observation/ Comments

 

Has the project defined and documented inter-relationships, logical interactions and interdependencies? E.g. project network diagrams

 

 

 

 

Estimation of duration Checklist Questionnaire

Document Identification

Document Result

[C/N/P/A/X]

Implementation/ Observation/ Comments

 

Who is the project responsible for establishing the duration of the activities?

 

 

 

 

Has the ‘estimation of duration’ been linked to project resource planning?

 

 

 

 

Has time allocation been planned for quality practices within the project?

 

 

 

 

Has the customer and stakeholder been involved?

 

 

 

 

Schedule development Quality  Checklist Questionnaire

Document Identification

Document Result

[C/N/P/A/X]

Implementation/ Observation/ Comments

 

What is the format of the project schedule?

 

 

 

 

Have key events, milestones, progress evaluations, critical and near-critical activities been identified in the schedule?

 

 

 

 

Prior to finalizing the schedule, was the customer/ stakeholder involved in a review for approval?

 

 

 

 

Schedule control Quality Checklist Questionnaire

Document Identification

Document Result

[C/N/P/A/X]

Implementation/ Observation/ Comments

 

Changes that affect the project objectives – does the customer/ stakeholder agree to these before implementation?

 

 

 

 

How often is the schedule revised?

 

 

 

 

Cost-related processes Quality Checklist Questionnaire

Document Identification

Document Result

[C/N/P/A/X]

Implementation/ Observation/ Comments

 

How are the project costs managed to ensure that the project is completed within the original budget constraints?

 

 

 

 

Cost estimation Quality Checklist Questionnaire

Document Identification

Document Result

[C/N/P/A/X]

Implementation/ Observation/ Comments

 

Have project costs been clearly identified and documented? If so, by whom?

 

 

 

 

Have the project costs been linked to the activity definition process?

 

 

 

 

Has the project cost estimation involved significant cost related risk? If so how are these managed?

 

 

 

 

Has the project budget been established based on the project cost estimation process and is it accordance with the approved accounting procedures within the organization?

 

 

 

 

Budgeting Checklist Questionnaire

Document Identification

Document Result

[C/N/P/A/X]

Implementation/ Observation/ Comments

 

Is the project budget consistent with the project requirements, assumptions, risks and contingencies? Is this documented?

 

 

 

 

Cost Control Checklist Questionnaire

Document Identification

Document Result

[C/N/P/A/X]

Implementation/ Observation/ Comments

 

What is the process for project purchasing/ expenditure requirements?

 

 

 

 

Has this process been documented and communicated to those responsible for authorizing expenditure or authorizing work that may have cost implications?

 

 

 

 

Are project expenditure records reviewed, managed and maintained?

 

 

 

 

Are the root causes for budget variances, both favorable and unfavorable identified? If so, is this part of a project budget review?

 

 

 

 

Resource-related Quality processes Checklist Questionnaire

Document Identification

Document Result

[C/N/P/A/X]

Implementation/ Observation/ Comments

 

Has resource planning and control been applied on the project?

 

 

 

 

Resource Quality planning Checklist Questionnaire

Document Identification

Document Result

[C/N/P/A/X]

Implementation/ Observation/ Comments

 

Does a resource plan exist for the project?

 

 

 

 

Resource Quality control Checklist Questionnaire

Document Identification

Document Result

[C/N/P/A/X]

Implementation/ Observation/ Comments

 

How does the project ensure that the remaining resources are sufficient to meet the project objectives?

 

 

 

 

Personnel-related processes and project organizational structure  Quality Checklist Questionnaire

Document Identification

Document Result

[C/N/P/A/X]

Implementation/ Observation/ Comments

 

Has a project organizational structure been established?

 

 

 

 

Is the project organizational structure encouraging for communication and co-operation between the project participants?

 

 

 

 

Is the project organizational structure appropriate for project scope, size and local conditions?

 

 

 

 

Does the project organizational structure identify customer/ stakeholders?

 

 

 

 

Are accountability, authority, responsibility and job descriptions defined and documented?

 

 

 

 

H

How often is the project organizational structure reviewed for validity and adequacy?

 

 

 

 

Staff allocation Quality Checklist Questionnaire

Document Identification

Document Result

[C/N/P/A/X]

Implementation/ Observation/ Comments

 

Was selection criteria prepared for staff allocation?

 

 

 

 

Has education, knowledge and experience been accounted for allocation of project staff?

 

 

 

 

Has the project manager been involved in the appointment of key team members?

 

 

 

 

Is project staff efficiency and effectiveness being monitored (subcontractor’s or not)?

 

 

 

 

Team Development Quality Checklist Questionnaire

Document Identification

Document Result

[C/N/P/A/X]

Implementation/ Observation/ Comments

 

Is the project team being recognized and rewarded?

 

 

 

 

Does the project environment encourage excellence, good working relationships, trust, respect and open communication?

 

 

 

 

Project Quality Communication-related processes and Planning  Checklist Questionnaire

Document Identification

Document Result

[C/N/P/A/X]

Implementation/ Observation/ Comments

 

Does the project plan consist of a communication plan?

 

 

 

 

What media is being used to transmit project communiqués?

 

 

 

 

How often are project communications been transmitted?

 

 

 

 

Does ‘Project Progress Reports’ form part of the project communications?

 

 

 

 

Information Management Quality Checklist Questionnaire

Document Identification

Document Result

[C/N/P/A/X]

Implementation/ Observation/ Comments

 

How does the project manage the following:

Preparing
Collecting
Classifying
Distributing
Filing
Updating and
Retrieving information

 

 

 

 

Do project meetings consist of meeting agendas?

 

 

 

 

Communication Control Quality Checklist Questionnaire

Document Identification

Document Result

[C/N/P/A/X]

Implementation/ Observation/ Comments

 

Is the project communication plan monitored and reviewed to ensure it continues to meet the needs of the project?

 

 

 

 

Risk-related processes, Risk identification, Risk  Assessment and Risk Control Quality Checklist Questionnaire

Document Identification

Document Result

[C/N/P/A/X]

Implementation/ Observation/ Comments

 

How often are risks identified through the project life cycle?

 

 

 

 

How are these risks managed?

 

 

 

 

1.5         3

Is probability of the occurrence and impact of the identified risk assessed?

 

 

 

 

1.6         4

What techniques are being used in the project to prioritise, manage and record the identified risks and their resolutions?

 

 

 

 

1.7         5

Are risks that may impact time schedules or project budget, identified and maintained separately?

 

 

 

 

1.8         6

Does the project plan consist of a contingency plan?

 

 

 

 

1.9         7

Do project risks form part of project progress reports?

 

 

 

 

Purchasing-related processes, Purchasing Planning and Control Checklist Questionnaire

Document Identification

Document Result

[C/N/P/A/X]

Implementation/ Observation/ Comments

 

Does the project plan consist of a procurement / purchasing process?

 

 

 

 

Does the process cover internal and external acquisitions?

 

 

 

 

Does the project organisational structure identify the interfaces with sub-contractors?

 

 

 

 

Has project purchasing/ procurement been reviewed?

 

 

 

 

Documentation of requirements checklist Questionnaire

Document Identification

Document Result

[C/N/P/A/X]

Implementation/ Observation/ Comments

 

Does purchasing documentation exist for the project?

 

 

 

 

Have the customer requirements been included into the purchasing/ procurement documents?

 

 

 

 

Do the purchasing documents go through a review process to ensure that all requirements are completely specified?

 

 

 

 

Evaluation of sub-contractors and  Sub-contracting Quality Checklist Questionnaire

Document Identification

Document Result

[C/N/P/A/X]

Implementation/ Observation/ Comments

 

Have project related sub-contractors been evaluated that may impact on the project? . E.g. technical experience, delivery times, quality system and financial stability.

 

 

 

 

1.10       2

How does the project manage project-relevant information being supplied to subcontractors?

 

 

 

 

1.11       3

How are subcontractor tenders evaluated?

 

 

 

 

Contract control Quality Checklist Questionnaire

Document Identification

Document Result

[C/N/P/A/X]

Implementation/ Observation/ Comments

 

Does the project consist of a process to ensure that all contract requirements, due dates and records are met?

 

 

 

 

How often are the contracts verified to ensure the performance of each subcontractor meets the contract requirements?

 

 

 

 

Are all contracts, prior to project closure, verified and updated?

 

 

 

 

POME Prescribe:

About Risk Management:

ü  There is no such thing as a zero-risk project: There is no such thing as a risk-free life.

ü  If you want to understand a risk fully, identify its causes as well as its effects.

ü  How do you respond to risks? POME emphasized on risk analysis on a dedicated chapter.

ü  When a project is desperately troubled, first take action to contain the damage then worry about recovery, just the way a first aid or rescue teams first “contain the damage” and consider other options after the victim’s condition stabilizes.

ü  Checklists for risks: Trouble sometimes stems from omissions. It is easy to “forget” key components of a work package. A checklist reduces the potential of leaving out important considerations.

 

Possibly related posts: (automatically generated)

• Related posts on Assurance
• Boomers Need to Address Long-Term Care Needs | meloanpay.com
• I Don't Want To Pay Given that Auto Assurance! What's It For …
• Ohio Dwelling Title-holder Assurance ? 3 The Reasonable Means To …

• Related posts on Control
• Cheap Pioneer CD-R55 Remote Control Shopping
• Intelligent Control Manual
• Natural Indoor Pest Control | eConsumerAlley.com

• Related posts on Quality
• Sleep problems can increase depression and reduce quality of life …

Related posts:

1. Website Quality Assurance – In Detail The term website quality assurance, when applied to websites, describes...
2. Quality Assurance & Quality Control – Guarantee Card To Superior Eminence Quality Assurance, abbreviated as QA implies a systematic and planned...
3. Quality Assurance Testing with ITIL Processes The IT Infrastructure Library ® (ITIL) is a collection of...
4. Quality Assurance Management Quality is never an accident; it is always the result...
5. Software Quality Assurance – Role and Responsibility of Management Team Once a software product undergoes different stages of development phase,...

Related posts brought to you by Yet Another Related Posts Plugin.

Tags: Assurance, Author Comments, Completeness, Control, Development Methodology, Operational Status, Organization System, Plan Checklist, Point Of Reference, Pome, Presentation Submissions, Project 1, Project References, Qa Group, Qap, Quality, Quality Assurance Plan, Quality Control, Reference Page, Responsible Organization, Reviewer Comments, Sdm, System Environment