Quality Assurance/ Quality Control (QA/ QC) from POME BY GAUTAM KOPPALA VT

Quality Assurance/ Quality Control (QA/ QC):				being conducted in accordance with the standards and
GUIDELINES FOR THE POME QUALITY				procedures (e.g., the proper people attend, minutes are
ASSURANCE PLAN CHECKLIST:				taken and distributed, and action items are assigned
This checklist is provided as part of the evaluation				and followed up)?
process for the Quality Assurance Plan. The
checklist assists designated reviewers in determining				Are appropriate test plans and procedures in place
whether specifications meet criteria established in				and being followed?
POME'S Project Development Methodology
(POMEPDM). The objective of the evaluation is to				Will the deliverables being produced meet the user's
determine whether the document complies with				requirements?
POMEPDM requirements.
Mentioned below is the DOCUMENT REVIEW				Are records being kept by the Quality Assurance role
CHECKLIST. Its purpose is to assure that documents				of quality problems, recommendations and actions?
achieve the highest standards relative to format,
consistency, completeness, quality, and presentation.				Are effective measurement techniques being used to
Submissions must include the following three				identify the levels of quality and productivity being
documents, and must be presented in the following				achieved and to provide a baseline for continuous
order: (First) Document Review Checklist, (Second)				improvement?
the Quality Assurance Plan Checklist, and (Third) the
Quality Assurance Plan.				Is project data being analyzed to determine trends and
				norms and to identify when quality threshold or target
The Quality Assurance Plan (QAP) presents a				levels are not being achieved?
framework for activities, which when followed, will
ensure delivery of quality products and services. The				Have quality improvement sessions been conducted
SDM provides the project standards and procedures				between the Quality Assurance Manager and the
to be used as the basis for the QA group's reviews				project team to develop solutions to delivery problems
and audits.				and to explore opportunities for improvement?
Document Review Checklist:
Purpose: Describe the purpose of the Quality				Are corrective actions being monitored for
Assurance Plan.				effectiveness in eliminating the cause of problems?
Scope: Describe the scope of the Quality Assurance
Plan as it relates to the project.				In any cases where corrective action is not taken or is
System Overview: Provide a brief system overview				ineffective, has the problem been escalated to the
description as a point of reference for the remainder				Quality Management function outside the project
of the document, including responsible organization,				team?
system name or title, system code, system category,				scope & timing of planned audits
operational status, and system environment and				Refer to the completed Engineering Methodology
special conditions.				Qualification Tool for the project to identify if
Project References: Provide a list of the references				Engineering Quality Audits are mandatory or optional
that were used in preparation of this document.				for the project. The qualification tool determines this
Acronyms and Abbreviations: Provide a list of the				based upon the assessment of technical risk &
acronyms and abbreviations used in this document and				complexity and project duration. Where audits are
the meaning of each.				required, use the following guidelines to determine the
Points of Contact:				broad scope of planned audits for the project. Once
1.6.1 Information: Provide a list of the				agreed, identify the proposed Audit regime / dates in
points of organizational contact (PoCs) that may be				the Project or Engineering Schedule.
needed by the document user for informational and				- Notwithstanding the following guidelines, planned
troubleshooting purposes.				Quality Audits:
1.6.2 Coordination: Provide a list of				- Should not be performed more frequently than once
organizations that require coordination between the				per month
project and its specific support function (e.g., installation				- Are generally triggered by achievement of selected
coordination, security, etc.). Include a schedule for				milestones
coordination activities.				- Scope and frequency should be based upon an
Quality Assurance Plan Checklist:				assessment of engineering risk, agreed between the
2.0 SCHEDULE OF TASKS AND				Project Manager and Project Engineer
RESPONSIBILITIES				- For projects that are large AND either technically
				complex OR technically high risk (as determined by the
Based on the tasks described in your Project Plan,				Methodology Qualification Tool:
provide a schedule of the QA activities for the duration				- At each major milestone gate i.e.
of the project. Tasks may include, but are not limited				- Milestone Gate 1 - After Release of Scope to Design
to, those listed below:				phase i.e. planning completed, design commenced
				- Milestone Gate 2 - After initiating the build
- Identify Standards and Guidelines				process i.e. after commencing significant build,
- Evaluate Software Tools				configuration or programming activities
- Evaluate Facilities				- Milestone Gate 3 - After initiating the Installation
- Evaluate Software Products Review Process				Process i.e. after commencing one or more significant
- Evaluate Project Planning, Tracking, and Oversight				installation activities
Processes				- For any of the lesser milestones deemed at risk e.g.:
- Evaluate Requirements Analysis Process				- Upon completion of Concept Design & Review
- Evaluate Design Process				- Upon completion of Functional Design & Review
- Evaluate Code and Unit Testing Process				- Upon completion of Detailed Design & Approval
- Evaluate Integration Testing Process				- Start or completion of Head End Set up
- Evaluate Acceptance Testing Process				- Start or completion of Static Graphics
- Evaluate Release Process				- Start or completion of Programming
- Evaluate the Corrective Action Process				- Start or completion of off-site Assembly &
- Evaluate Media Certification Process				Manufacture
- Certify Non-deliverable Software				- Start or completion of Database (point) Building
- Evaluate Storage and Handling Process				- Start or completion of Head End Configuration
- Evaluate Deviations and Waivers Process				- Start or completion of Graphics Programming
- Evaluate Configuration Management Process				(dynamic point allocation)
- Evaluate Software Development Library Control				- Before commencement of Staging & FAT
Process				- During the Installation phase i.e. at key milestones
- Evaluate Non-developmental Software				through installation process
- Perform Configuration Audits				- Before commencement of commissioning
- Evaluate Risk Management Process				- Upon completion of Customer Acceptance testing
				- Upon project completion
Quality Assurance Plan:				- For projects that are small AND technically
				"standard" AND low risk (as determined by the
Documents by Phase: List and briefly describe the				Methodology Qualification Tool)
documentation expected to be produced during this				- Planned Quality Audits are optional
project. Depending on the size of your project, this				- It is recommended that Project Managers select a
may include, but is not limited to, the documents in the				random sample of projects and/or project engineers
following subsections:				technicians to be audited to give confidence that these
3.1.1 Initiate Phase:				types of projects are following appropriate engineering
- Needs Statement				practice, and to help grow the engineering competency
- Project Plan (including WBS)				of team members who may not have benefited from
- Configuration Management Plan				recent involvement in large, high risk project audits.
- QualityAssurance Plan				Unplanned Quality Audits
- Feasibility Study				- Unplanned Quality Audits may occur at any stage in
- Cost/Benefit Analysis				response to an undesirable event or major change e.g.
- Risk Analysis				- Major process failure
3.1.2 Define Phase:				- Customer complaint
- System Support and Acquisition Plan (initial)				- Change of key personnel
- Functional Requirements Document				- Major design change
- Data Requirements Document				2
- System Security and Privacy Plan				Project Manager / Project Engineer
- Internal Audit Plan				Identify suitable auditor
- Project Plan (updated)				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
3.1.3 Design Phase:				Operations Manager. When selecting auditors, the
- System/Subsystem Specifications				following should be considered:
- Database Specifications				- Independence - NOT directly involved in delivery of
- Program Specifications				the project (e.g. not the Project Manager or Engineer
- System Support and Acquisition Plan (final)				for the project) and is not likely to be influenced
- Validation, Verification, and Testing Plan (initial)				- Competence - recognised for their knowledge and
- Training Plan (initial)				skill in the type of activities being audited
- Project Plan (updated)				- Observant & perceptive - able to identify things
				of greatest concern, to understand and adapt to the
3.1.4 Build Phase:				particular project circumstances
- Installation and Conversion Plan (initial)				- Persistent & thorough - but not pedantic or
- Test Plan				single-minded, able to evaluate efficacy of alternative
- User's Manual				approaches
- Operations Manual				- Will often be a Project Manager, Team Leader or
- Maintenance Manual				nominated Auditor from a similar business, but NOT
- Validation, Verification, and Testing Plan (final)				from the project
- Training Plan (final)				For long duration, high risk projects, it may be beneficial
- Project Plan (updated)				to use a number of different auditors throughout the
3.1.5 Evaluate Phase:				project life cycle.
- Test Results and Evaluation Reports				Once the auditor has been agreed, ensure that they
- Installation and Conversion Plan (final)				are informed of and available for the planned audit
- Project Plan (updated)				schedule / dates.
3.1.6 Operate Phase:				3
- Pilot Test Results				Project Engineer
- Training Material				Prepare for Audit
- Project Plan (updated)				- Gather the audit documentation and reference
3.2				material including:
Discipline for Documentation Standard Practices:				- Completed Engineering Qualification Tool and the
Describe the criteria that will be applied during review				Balanced Scorecard template for the project - to use
and evaluation of all lifecycle documents.				to record the audit outcomes
4.0 REVIEWS AND AUDITS				- Completed Balanced Scorecard from previous audit
4.1				s (where relevant) - to identify prior corrective actions
Review Process: Define the steps of the review				or suggestions for improvement that should be
process and the procedures that will be used to				reviewed
conduct reviews.				- Copies of relevant procedures or procedure flow
4.2.1 Lifecycle Reviews: Identify the				charts - to use as a prompt for things to look for,
types of SDM associated lifecycle or non-lifecycle				questions to ask, and to capture observations during
reviews that will be conducted within each project				the audit
lifecycle phase. Include a schedule of reviews and				- Copy of the up-to-date project or engineering
include how the results of each review will be used on				schedule - to show the current progress of the project
the project.				and thus indicate the main focus of the audit
				- Ensure the Auditor receives the above information
Typically, the lifecycle reviews include:				well in advance of the audit
- Requirements Review				- Confirm the date and place where the audit is to
- Design Review				take place and the persons to be in attendance
- Specification Review				- Ensure that those to be in attendance understand the
- Preliminary Design Review				scope of the audit and make arrangements to be able
- Critical Design Review				to provide the necessary evidence of conformance
- Test Readiness Review				with relevant procedures & standards at the time
- Formal Qualification Review				of the audit
- Production Readiness Review				4
- Acceptance Test Review				Auditor / Project Engineer
- Post-Implementation Review				Conduct engineering audit
				The Engineering Balanced Scorecard shall be used as
5.0 TESTING				the basis of recording the outcomes of the engineering
Identify the roles and responsibilities of the QA function				audit, including:
in relation to testing throughout the various stages of				- Who conducted the audit
the project.				- Which procedures were audited - the scope
6.0 PROBLEM REPORTING AND CORRECTIVE				- Overall performance assessment against the
ACTION				requirements of relevant procedures
Discuss QA responsibilities and activities concerned				- What objective evidence was sighted
with the reporting and tracking of project-related				- Major observations, Corrective Actions or
problems and resolutions.				Suggestions for Improvement
6.1				For 2nd and subsequent audits, the Balanced
Problem/Issue Documentation: Explain how problems				Scorecard worksheet should be copied to a new tab
and issues will be documented.				in the workbook so that there is a separate scorecard
				worksheet for each audit performed.
6.2				The Scorecard is not an exhaustive list of questions
Report Metrics: Describe how metrics from the above				& issues but should be used as an aide memoir or
reports will be collected and analyzed to determine				prompt to the auditor. Likewise, copies of procedures
and coordinate corrective actions.				and procedure flow charts should also be used as aids
				to memory; to help ensure that essential issues are not
7.0 TOOLS				overlooked. Where necessary the auditor may need
Describe the tools that will be used for QA and the				to deviate from the content of the Scorecard to
methodology employed to implement usage of the				investigate an issue or concern with a view to
mentioned tools.				establish if any corrective action is required.
8.0 PROJECT CONTROLS				The auditor should:
8.1				- Review all outstanding Corrective Actions and
Product Control: Identify how QA will monitor the				Suggestions for Improvement form previous audits
methods and tools used to maintain and store				- Seek and record objective evidence of
controlled versions of system products.				conformance with the requirements of the relevant
8.2				procedures
Supplier Control: Describe the provisions for assuring				- Assess and score overall performance against each
that products provided by suppliers meet established				procedure relevant to the current audit. Note that
requirements.				procedures targeted for the audit would be expected
				to include:
9.0 TRAINING				- All procedures identified as 'applicable to the project'
				AND included in the most recently completed milestone
Identify the training activities that will be provided to				s
meet the needs of QA on this project.				- Procedures identified as 'applicable to the project'
CHECKLIST FOR MANAGING OVER ALL				AND included in the next or subsequent incomplete
PROJECT QUALITY				milestones WHERE the input or initiating event for the
Has the Quality Assurance role been identified and				procedure has occurred. In such cases, the
assigned an appropriate level of authority?				procedure should be marked as 'applicable to current
				project status' and assessed accordingly.
Are project standards and procedures being defined				Identify Corrective Actions or Suggestions for
for each area of the project to ensure consistent				Improvement. These should be recorded and used in
delivery in accordance with the quality requirements?				a constructive manner to assist the project to
				effectively manage risk and deliver customer
Do the standards and procedures make reference to				satisfaction.
material in the knowledge base and simply note any				Identify Best Practice examples and significant
project-specific additions, exceptions, or				opportunities to improve the engineering procedures,
enhancements?				tools and/or processes

Are the standards and procedures in place prior to the				Presentation of audit results & recommendations
commencement of the work to which they apply?				- The completed Audit Scorecard should be
				forwarded to the Engineer's manager and the Project
Are all team members adequately trained in the tools				Manager.
and standards and procedures for the project				- Where the overall audit result falls below the
environment (or will additional start-up training be				accepted benchmark value, a Corrective Action OFI
required)?				should be raised against the Engineer and the
				scorecard attached to the OFI. The Scorecard
Is each member of the team personally committed to				prompts for this action when the result falls below the
abide by the standards and procedures?				accepted benchmark.
				- Suggestions for improvement of the Engineering
Is the team involved in the ongoing development and				Methodology should be forwarded to the relevant
adoption of the standards (to promote a sense of				Procedure Owner. Suggestions for improvement will
ownership by the team)?				often arise from cases where the audit has identified
				performance as 'above standard' or 'best practice'.
Are formal structured walk-throughs and reviews

ITIL

Quality Assurance/ Quality Control (QA/ QC) from POME BY GAUTAM KOPPALA VT