Project Management Framework
Execution - Quality Assurance Management

How to use the Quality Assurance Plan

Quality Assurance (QA) Management ensures that a project is on track with scheduled deliverables and within budget. QA is conducted using independent quality reviews. This function reports directly to the Project Sponsor and is separate from the Project Manager. Project processes are monitored for effectiveness and project risk is continuously addressed. This independent and regular evaluation of project performance provides the confidence that the project is progressing in a satisfactory manner. Reviews are documented using Quality Assurance reports to indicate status and make recommendations. Project participants should reference the Quality Assurance and Risk Management Plans, Project Schedule and Task Plans and Post Implementation Reviews. QA reporting feeds into Issue Management and Status Reporting and coordinates with Change Management, Staffing and Communications Management.

For Best Results

  • Make sure that the Project Sponsor articulates the value and use of the QA Plan and quality processes to the project team members and stakeholders.
  • Verify the decision-making structures and processes for advising corrective actions and implementing QA recommendations in a timely manner.
  • Maintain the independence necessary for objective QA. The QA function should report independently to the Project Sponsor.
  • Use external sources and/or independent staff not reporting to the project manager early in the project.
  • Arrange for QA representation at key meetings and project activities.
  • Prepare QA reports according to the schedule in the QA Plan.
  • Address points of risk identified in QA reports. Utilize the Risk Management Plan to assess risk trends and evaluate recommendations and risk mitigation strategies.
  • Position the QA function to confirm what is being done right by use of due diligence within acceptable risk levels.
  • Validate that the Risk Management process parallels QA reporting intervals.
  • Respond quickly to implement QA recommendations or revise processes.
  • Utilize other quality resources such as a Quality Agreement to address QA issues.
  • Scale QA functions to the size of the project.
  • Provide a balanced perspective for technology choices to reaffirm business decisions.
  • Maintain thorough and accurate documentation of all inputs and outputs of the processes, reporting, tracking, recommendations and corrective action activities.

Also Consider

  • Monitoring the QA provider for adherence to schedule, reporting elements, assessment methods and meeting coverage.
  • Reaffirming QA roles and responsibilities to reduce resistance.
  • Instituting more formalized quality methods for high-risk project elements.
  • Providing two-way feedback mechanisms for process assessment. Early identification of mistakes avoids costly corrections later in the project.
  • Pacing the introduction of new processes that require more frequent monitoring than well-established practices.
  • Utilizing logs, checklists and automated tools to track implementation of recommendations, risk management measures and schedules.
  • Using a mix of quality monitoring methods such as reviewing Deliverable Expectation Documents (DED).
Related Links:
Quality Assurance Plan
Quality Assurance Plan Template
Quality Assurance Report Template
Quality Assurance Report Example

Checklists

QUALITY ASSURANCE MANAGEMENT
Has the Quality Assurance (QA) Plan been reviewed by the Project Sponsor, project team and all internal and external stakeholders?
Have the stakeholders agreed that the QA Plan includes the appropriate quality provisions and independence to achieve stakeholder confidence?
Is the QA Plan being followed?
Have QA reviews been scheduled?
Does QA have access to all pertinent materials and levels of oversight?
Is integration with the Risk Management Plan and trending continually assessed?
Are QA reports being provided for Status Reporting?
Is documentation and are recommendations reviewed at the appropriate levels?
Are external/internal providers or Contractors complying with quality controls?
Is the project team using quality processes?
Have QA tasks in the project schedule been verified to ensure tasks are still valid and nothing should be modified?
Are Lessons Learned maintained to use for the Post Implementation Review?.

 

 

 

| Home | Privacy | Site Map | Copyright © 2008 by DIS