4 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

5 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

6 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

7 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

8 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

The document in this file is adapted from the IEEE standards for Software Project Management Plans, 1058-1998, which conforms to the requirements of ISO standard 12207 Software Life Cycle Processes. Tailor

Appendix I Hardware Development Plan Template Version 2 March 7, 2005 This page is intentionally left blank. Version 2 March 7, 2005 Title Page Document Control Panel Table of Contents List of Acronyms

Appendix H Software Development Plan Template Version 2 March 7, 2005 This page is intentionally left blank. Version 2 March 7, 2005 Title Page Document Control Panel Table of Contents List of Acronyms

For the SeaPort-e contract, The Squires Group Inc. (TSGi) has developed a QA Plan that creates a strategic quality partnership at both the contract and Task Order level and is firmly based on the metrics

INL/EXT-09-17022 Rev. 2 Independent Verification and Validation of SAPHIRE 8 Software Project Plan March 2010 The INL is a U.S. Department of Energy National Laboratory operated by Battelle Energy Alliance

3 PART 2 SOFTWARE DEVELOPMENT PLAN 3.1 Overview of Software Development and Integration Activities The Development Team will utilize the SDLCM Methodology standards and procedures for all development with

SOFTWARE DEVELOPMENT PLAN This document outline is based on the IEEE Standard 1058.1-1987 for Software Project Management Plans. This is the controlling document for managing a software project, and it

Page 1 of 7 Software Supplier Process Requirements 1.0 QUALITY SYSTEM FRAMEWORK 1.1 QUALITY POLICY The Seller shall document and implement a quality program in the form of Quality manual or detailed Quality

Service Support Configuration Management ITIL Configuration Management - 1 Goals of Configuration Management The goals of Configuration Management are to: Account for all the IT assets and configurations

- ATTACHMENT - PROGRAM MANAGER DUTIES & RESPONSIBILITIES MARYLAND STATE POLICE W00B0400021 About this document this is a detailed description of typical Project Manager (PM) duties, responsibilities, and

What is a life cycle model? Framework under which a software product is going to be developed. Defines the phases that the product under development will go through. Identifies activities involved in each

ITS Projects Systems Engineering Process Compliance Checklist FHWA Final Rule (23 CFR 940) This checklist is to be completed by the MDOT or LPA Project Management Staff. Please refer to the accompanying

Lecture Slides for Managing and Leading Software Projects Chapter 1: Introduction developed by Richard E. (Dick) Fairley, Ph.D. to accompany the text Managing and Leading Software Projects published by

(STP) Template Items that are intended to stay in as part of your document are in bold; explanatory comments are in italic text. Plain text is used where you might insert wording about your project. This

QA Roles and Responsibilities There are various roles on projects, some people may play more than one role. You should always check with your organizations testing methodology on what your role(s) are.

System Development and Life-Cycle Management (SDLCM) Methodology Subject Type Standard Approval CISSCO Program Director A. PURPOSE This standard specifies the content and format requirements for a Software

Certified Software Quality Engineer (CSQE) Body of Knowledge The topics in this Body of Knowledge include additional detail in the form of subtext explanations and the cognitive level at which the questions

Change Management Plan Template Project Name: U.S. Department of Housing and Urban Development October, 2010 Change Management Plan Template (V1.0) Notes to the Author [This document is a template of a

INL/EXT-10-17828 Rev. 1 Independent Verification and Validation of SAPHIRE 8 Software Quality Assurance Plan March 2010 The INL is a U.S. Department of Energy National Laboratory operated by Battelle Energy

The INCOSE Certification Program Office has committed to release sample test questions to help guide applicants and training providers in understanding the format of the INCOSE knowledge exam. The following

1. ROLE DEFINITIONS ATTACHMENT 3 SPS PROJECT SENIOR PROGRAM MANAGER (SPM) DUTIES & RESPONSIBILITIES The purpose of this section is to distinguish among the roles interacting with the SPM obtained through

Template Version X.x October 11, 2012 This is an integral part of infrastructure and deployment planning. It supports the goal of optimum provisioning of resources and services by aligning them to business

Chapter 8 ISO 9001 for Small Projects INTRODUCTION TO ISO 9001 FOR SMALL PROJECTS Many organizations are intimidated by the amount of documentation associated with ISO 9001 conformance requirements. The

PHASE 6: DEVELOPMENT PHASE The Phase features a key step in the project: system construction. The previous phases lay the foundation for system development; the following phases ensure that the product

Appendix 2-A. Application and System Development Requirements Introduction AHRQ has set up a Distributed Systems Engineering Lab (DSEL) to support all internal development efforts and provide a facility

Page 1 of 8 TITLE: Control of Software WARNING This document is the property of United Technologies Corporation (UTC). You may not possess, use, copy or disclose this document or any information in it,

The Open Group Future Airborne Capability Environment (FACE ) Library Requirements Version 2.2 April 2015 Prepared by The Open Group FACE Consortium Business Working Group Library Subcommittee AMRDEC PR1201

1 BAL2-1 Professional Skills for the Business Analyst OVERVIEW This course trains participants to help business clients articulate their needs and wants, and to document them clearly, concisely, and completely.

Project Audit & Review Checklist The following provides a detailed checklist to assist the PPO with reviewing the health of a project: Relevance (at this time) Theory & Practice (How relevant is this attribute

API Q2 Specification for Quality Management System Requirements for Service Supply Organizations for the Petroleum and Natural Gas Industries A Service Providers Perspective How is API Q2 Different ISO

CMII-100H CMII Standard for Enterprise-Wide Configuration Management and Integrated Process Excellence by the Institute of Configuration Management and CMII Research Institute Revision H; Released March

How to Write a Software Process for YOUR COMPANY 1. Introduction MicroTools is proposing to assist YOUR COMPANY in improving the existing software process. The purpose of this project is to both improve

Annex 7 Software Project Audit Process 1. Introduction 1.1 Purpose Purpose of this document is to describe the Software Project Audit Process which capable of capturing different different activities take

Software Project Management Objectives Introduce students to a variety of approaches and techniques in SPM Use current SPM tools Develop new SPM ideas Document reading, experiences and ideas Improve writing

Total Quality 1) Quality 1.1 Quality assurance (QA) refers to the engineering activities implemented in a quality system so that requirements for a product or service will be fulfilled. It is the systematic

Integrated Methodology Deliverable Descriptions Copyright 2011, QAIassist C2011 This publication may not be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic,

Appendix E Program Management Plan Template Version 2 March 7, 2005 This page is intentionally left blank. Version 2 March 7, 2005 Title Page Document Control Panel Table of Contents List of Acronyms Definitions

Object-Oriented Software Development What is Object-Oriented Development Object-Oriented vs. Traditional Development An Object-Oriented Development Framework Phases, Activities, and Work Products Phases,