Quality Assurance Plan PPM Version 2.0



Similar documents
Quality Management Plan Template

<name of project> Software Project Management Plan

SOFTWARE QUALITY & SYSTEMS ENGINEERING PROGRAM. Quality Assurance Checklist

Overview of STS Consulting s IV&V Methodology

PROJECT MANAGEMENT PLAN TEMPLATE < PROJECT NAME >

<Project Name> Software Quality Assurance (SQA) Plan. <Document Control Number>

QUALITY MANAGEMENT PLAN

Appendix H Software Development Plan Template

Software Project Management Plan (SPMP)

Independent Verification and Validation of SAPHIRE 8 Software Project Plan

Software Quality Subcontractor Survey Questionnaire INSTRUCTIONS FOR PURCHASE ORDER ATTACHMENT Q-201

STS Federal Government Consulting Practice IV&V Offering

Certified Software Quality Engineer (CSQE) Body of Knowledge

ITS Projects Systems Engineering Process Compliance Checklist

<PROJECT NAME> PROJECT MANAGEMENT PLAN

An Introduction to. Metrics. used during. Software Development

Service Support Kasse Initiatives, LLC. ITIL Configuration Management - 1. version 2.0

Your Software Quality is Our Business. INDEPENDENT VERIFICATION AND VALIDATION (IV&V) WHITE PAPER Prepared by Adnet, Inc.

Project Management Guidelines

- ATTACHMENT - PROGRAM MANAGER DUTIES & RESPONSIBILITIES MARYLAND STATE POLICE W00B

8. Master Test Plan (MTP)

Template K Implementation Requirements Instructions for RFP Response RFP #

3.1 Overview of Software Development and Integration Activities

<Project Name> Deployment Plan

Design Specification for IEEE Std 1471 Recommended Practice for Architectural Description IEEE Architecture Working Group 0 Motivation

CMII-100H. CMII Standard for Enterprise-Wide Configuration Management and Integrated Process Excellence. by the Institute of Configuration Management

Capacity Plan. Template. Version X.x October 11, 2012

Change Management Plan Template

SOFTWARE ASSURANCE STANDARD

Process Improvement Plan

NODIS Library Program Formulation(7000s) Search

Positive Train Control (PTC) Program Management Plan

Department of Administration Portfolio Management System 1.3 June 30, 2010

CONFIGURATION MANAGEMENT PLAN GUIDELINES

Appendix <<1>> System Status Report for System template

<Project Name> Quality Assurance Plan

Page 1 of 7 Effective Date: 12/18/03 Software Supplier Process Requirements

What is a life cycle model?

SOFTWARE DEVELOPMENT PLAN

PROJECT PLAN TEMPLATE

How To Understand And Understand The Cmm

Project Type Guide. Project Planning and Management (PPM) V2.0. Custom Development Version 1.1 January PPM Project Type Custom Development

<Company Name> <Project Name> Software Development Plan. Version <1.0>

Independent Verification and Validation of SAPHIRE 8 Software Quality Assurance Plan

Software Quality Assurance: II Software Life Cycle

Management. ITIL Release. Dave Howard. A Hands-on Guide. CRC Press. Taylor & Francis Group. Taylor St Francis Croup, an Informa business

Appendix 2-A. Application and System Development Requirements

TITLE: Control of Software

Lecture Slides for Managing and Leading Software Projects. Chapter 1: Introduction

An Overview of IEEE Software Engineering Standards and Knowledge Products

ATTACHMENT 3 SPS PROJECT SENIOR PROGRAM MANAGER (SPM) DUTIES & RESPONSIBILITIES

Sparx Systems Enterprise Architect Cloud-based repository hosting

SEI Level 2, 3, 4, & 5 1 Work Breakdown Structure (WBS)

When printed the document is for reference only and is considered uncontrolled - refer to the Document Control System for the most current version

Rapidly Defining a Lean CMMI Maturity Level 3 Process

BAL2-1 Professional Skills for the Business Analyst

How To Write An Slcm Project Plan

Reaching CMM Levels 2 and 3 with the Rational Unified Process

Library Requirements

API Q2 Specification for Quality Management System Requirements for Service Supply Organizations for the Petroleum and Natural Gas Industries

Standards & Practices for the software and system engineers /

ENOVIA Aerospace and Defense Accelerator for Program Management

Software Classification Methodology and Standardisation

ISO 9001 for Small Projects

Program Management Office Provided Adequate Oversight of Two Contracts Supporting the Defense Enterprise Accounting and Management System

Appendix A-2 Generic Job Titles for respective categories

Software Quality Assurance Plan

Release Notes Applied SAFe 4.0

Global Onboarding: An Integrated Learning Journey

Testing Process Models

Software Test Plan (STP) Template

GAMP 4 to GAMP 5 Summary

E2E Project Management Process Governance (Electric Capital)

INTEGRATED SOFTWARE QUALITY MANAGEMENT (ISQM)

System Development and Life-Cycle Management (SDLCM) Methodology

Project Lifecycle Management (PLM)

KPMG in India s Software testing services Test consulting case studies

Colorado Department of Health Care Policy and Financing

Dynamic Forms for SharePoint

Project Management Life Cycle (PMLC)

Software Project Management

1. Introduction. Annex 7 Software Project Audit Process

PHASE 6: DEVELOPMENT PHASE

Maps between the 2016 CSQE BOK and the previous BOK

Space Environment Technologies (SET) QUALITY ASSURANCE PROGRAM. Command Media. Approved by: Approved by: Approved by:

Software Project Audit Process

Software Project Management Plan. Team Synergy Version: 1.0 Date: 1/27/03

Errata 1 st Printing. Errata 2 nd Printing

PMP Examination Tasks Puzzle game

CONTENTS. Preface. Acknowledgements. 1. Introduction and Overview 1 Introduction 1 Whatis the CMMI"? 2 What the CMMI* is Not 3 What are Standards?

AS9100 B to C Revision

Sample Quality Management Plan

Peer Review Process Description

Test Plan (a Real Sample) SoftwareTestingHelp.com Live Project Training - OrangeHRM

Manag. Roles. Novemb. ber 20122

Making Sense of Process Improvement Programs and Appraisals

QUALITY MANAGEMENT SYSTEM REQUIREMENTS General Requirements. Documentation Requirements. General. Quality Manual. Control of Documents

Transcription:

Quality Assurance Plan PPM Version 2.0 <Project or Solution Name> U.S. Department of Housing and Urban Development <Month, Year> PPM Version 2.0 January 2014

Quality Assurance Plan Document Control Information Document ID <Document Management System #> Document Creator Document Owner Issue Date Last Saved Date File Name Document History <Document Creator s Name> <Owner Name> <Date> <Date> <Name> <Provide information on how the development and distribution of the Quality Assurance Plan is controlled and tracked. Use the table below to provide the release number, date, author, and a brief description of the reason for creating the revised version.> Release No. Date Implemented By Revision Description PPM Version 2.0 January 2014 Page i

Contents Quality Assurance Plan Document Control... i Document History... i Contents... ii 1. Quality Management... 1 1.1 Organizations, Responsibilities, and Interfaces... 1 1.2 Tools, Environments, and Interfaces... 1 1.3 Systems Impacted... 1 1.4 Deployment Schedule... 1 2. Reviews, Audits and Walkthroughs... 2 2.1 Reviews and Walkthroughs... 2 2.2 Deliverables... 2 2.3 Process Assessments... 2 2.4 Products Assessments... 2 3. Standards, Metrics, Practices, Conventions and Waivers... 3 3.1 Conventions... 3 3.2 Metrics... 3 Appendix A: References... 4 Appendix B: Key Terms... 5 PPM Version 2.0 January 2014 Page ii

Quality Assurance Plan 1. Quality Management 1.1 Organizations, Responsibilities, and Interfaces <Describe the primary roles and responsibilities of the project staff as it relates to the practice of quality assurance for the project. Indicate responsibilities for activities such as mentoring or coaching, auditing work products, auditing processes, participating in project reviews, etc.> Name Role Quality Responsibility <Insert Name> IT Project Manager Quality mentoring & coaching <Insert Name> Business Project Manager Quality audits <Insert Name> <Role> <Responsibility> 1.2 Tools, Environments, and Interfaces <List and define the data elements and the quality tools that will be used to measure project quality and level of conformance to defined quality standards/metrics.> Tool <Benchmarking> <Tool Name> <Industry recognized benchmarks> <Tool Description> 1.3 Systems Impacted Description <List all the systems that may be impacted with a brief description of the type of impact associated.> 1.4 Deployment Schedule <Provide a description of [Project name s] deployment schedule and lists major milestones.> PPM Version 2.0 January 2014 Page 1

Quality Assurance Plan 2. Reviews, Audits and Walkthroughs 2.1 Reviews and Walkthroughs <Detail the reviews and walkthroughs for each phase of the Project Planning and Management (PPM) Life Cycle. Begin with known reviews and walkthroughs and update this document to include more detail throughout subsequent PPM Life Cycle phases.> 2.2 Deliverables Use the following table to show the artifacts and deliverables required for <Project Name>. <The quality assurance team will review required artifacts for conformity to the standards of the PPM Life Cycle. Existing [Project name] artifacts may be updated as appropriate. To meet documentation requirements, the project team is highly encouraged to copy, revise and reuse existing project documentation to the maximum extent possible. > Phase Deliverable Lead Role Comments 2.3 Process Assessments <The following are typical process assessments that may be conducted by quality assurance personnel. Project planning Project monitoring and control Measurement and analysis System/subsystem reviews Peer reviews Requirements management Software configuration management and configuration audits Test management (verification & validation) Software problem reporting and corrective action Risk management Supplier agreement management> 2.4 Products Assessments <The following are typical product assessments that may be conducted by quality assurance personnel. Peer review packages Document reviews Software development folders Software configuration management Test results (e.g., requirements traceability matrix, test reports)> PPM Version 2.0 January 2014 Page 2

3. Standards, Metrics, Practices, Conventions and Waivers 3.1 Conventions Quality Assurance Plan <Quality assurance generated artifacts will conform to HUD standards and practices, and the naming conventions of the PPM Life Cycle.> 3.2 Metrics <The following standard metrics are the minimum threshold that may be collected, reported, and maintained in the area of quality assurance: QA effort and funds expended (Planned vs. Actual) Number of quality assurance assessments (Planned vs. Actual) Number of quality assurance assessment findings or Number of quality assurance assessment observations Number of risks identified as a result of a quality assurance assessment Additional project metrics may also be collected, reported, and maintained, they include: Number of peer reviews (Planned vs. Actual) Number of open vs. closed action Items from peer reviews Number of open vs. closed software problem reports, with aging and trending over time Number of open vs. closed independent verification and validation (IV&V) findings Number of open vs. closed software requests for action or items from project-level reviews> PPM Version 2.0 January 2014 Page 3

Quality Assurance Plan Appendix A: References <Insert the name, version number, description, and physical location of any documents referenced in this document. Add rows to the table as necessary.> Table 1 below summarizes the documents referenced in this document. Document Name Description Location <Document Name and Version Number> <Document description> <URL to where document is located> Table 1 - References PPM Version 2.0 January 2014 Page 4

Appendix B: Key Terms Quality Assurance Plan Table 2 below provides definitions and explanations for terms and acronyms relevant to the content presented within this document. <Insert Term> Term Definition <Provide definition of term and acronyms used in this document.> Table 2 - Key Terms PPM Version 2.0 January 2014 Page 5