GEEKS ON ROPES

PROJECT QUALITY MANAGEMENT PLAN

Version 1.0
August 2013

Geeks on Ropes Version: Error! Unknown document property name. Error! Unknown document property name.
Revision Date: August 2013 Page 2 of 11

Revisions
Revisions to this document are made on a per-page basis in order to clarify, refine, or adapt the Project
Quality Management Plan for any new or changed requirements. Each revised page is to have a revision
number and a date in the bottom footer. All revisions are to be recorded in the table below by number
and date.
Document Change Record (DCR)
Version Change Description Approved by
Date
Approved
1.0 Initial Release







Geeks on Ropes Version: Error! Unknown document property name. Error! Unknown document property name.
Revision Date: August 2013 Page 3 of 11

Table of Contents
Revisions ....................................................................................................................................................... 2
1 INTRODUCTION ..................................................................................................................................... 4
1.1 PURPOSE OF THE PROJECT QUALITY MANAGEMENT PLAN ......................................................... 4
2 PROJECT QUALITY MANAGEMENT OVERVIEW ..................................................................................... 4
2.1 ORGANIZATION, RESPONSIBILITIES, AND INTERFACES ................................................................. 4
2.5 Management Organization ....................................................................................................... 5
2.57 TOOLS, ENVIRONMENT, AND INTERFACES ................................................................................... 7
3 PROJECT QUALITY MANAGEMENT TASKS ............................................................................................. 7
3.1 EVALUATE SYSTEM REQUIREMENTS ............................................................................................. 7
3.7 EVALUATE FACILITY REQUIREMENTS ............................................................................................ 7
3.8 EVALUATE SYSTEM DESIGN PROCESS ........................................................................................... 7
3.18 EVALUATE SOFTWARE DESIGN PROCESS ...................................................................................... 8
3.23 EVALUATE SOFTWARE IMPLEMENTATION AND UNIT TESTING ................................................... 8
3.27 EVALUATE HARDWARE DESIGN PROCESS..................................................................................... 8
3.32 EVALUATE HARDWARE IMPLEMENTATION AND UNIT TESTING .................................................. 9
3.36 EVALUATE END-ITEM DELIVERY PROCESS .................................................................................... 9
4 DOCUMENTATION ................................................................................................................................ 9
5 SUPPLIER CONTROL............................................................................................................................. 10
APPENDIX A. LIST OF ACRONYMS ............................................................................................................... 11




Geeks on Ropes Version: Error! Unknown document property name. Error! Unknown document property name.
Revision Date: August 2013 Page 4 of 11

1 INTRODUCTION
1.1 PURPOSE OF THE PROJECT QUALITY MANAGEMENT PLAN
The purpose of this Project Quality Management Plan (PQMP) is to establish and define all the goals,
processes, and responsibilities required to effectively manage project quality from the project
planning phase to the project delivery phase.
1.2 The main goal of the PQMP program is to verify that all the software and documentation are
in accordance with all the technical requirements. The PQMP procedures, as defined within
this document, shall be used to verify that all deliverable software, hardware, and
documentation are in compliance with the technical and performance specifications.
1.3 The intended audience of the PQMP is the project manager, project team, project
stakeholders, and any senior level personnel whose support is required to carry the project
plan to completion.
2 PROJECT QUALITY MANAGEMENT OVERVIEW
2.1 ORGANIZATION, RESPONSIBILITIES, AND INTERFACES
2.2 This section outlines the management organizational structure, its roles and responsibilities,
and the software and hardware quality tasks that will be performed.
2.3 Project Quality Management (PQM) has the authority to identify quality problems and to
recommend and verify implementation of solutions. If there is evidence that the PQMP is
not being followed, PQM has the authority to stop work until corrective actions are taken.
2.4 PQM oversees the quality of all teams under the supervision of the Project Management
team as shown in the following diagram:

Geeks on Ropes Version: Error! Unknown document property name. Error! Unknown document property name.
Revision Date: August 2013 Page 5 of 11

2.5 Management Organization
2.6 Relevant entities and roles that are of interest and applicable to the PQMP are described in
the following subsections:
2.7 Project Manger
2.8 The Project Manager (PM) is responsible for management of project objectives and the
project plan.
2.9 The PM will implement the quality program in accordance with the quality assurance
specifications as outlined in the Quality Assurance Requirements.
2.10 The PM will work with the customer early on in the Project Scope phase and will produce
the Customer Requirements Definition which defines the customers needs.
2.11 The PM will manage and analyze the costs and benefits of all quality improvements.
2.12 The PM will ensure that the customer endorses all quality objectives as outlined in the
PQMP.
2.13 The PM will identify, develop and maintain all planning documents, such as the Project
Management Plan, references, and Test Plans.
2.14 Team Leader
2.15 The Team Leader (TL) is responsible for the quality control evaluations of the teams work.
2.16 The TL will assist in verifying that all work is in accordance with the quality assurance
specifications as outlined in the Quality Assurance Requirements.
2.17 The TL will report to the project manager, as often or frequent as the project manager
deems necessary, the quality status of the project as it pertains to the team leaders
department.
2.18 The TL will report any problems directly to the project manager.
2.19 Systems Engineering
2.20 The Systems Engineering Department (SED) shall review and comment on the PQMP.
2.21 SED shall implement the quality program as outlined in this PQMP.
2.22 SED shall resolve and follow-up on any quality issues as relating to the system in both
hardware and software.
2.23 SED will identify, implement, and evaluate the quality factors to be implemented in the
system in accordance with other program and/or project planning documents.
2.24 Systems Test
2.25 The Systems Test Department (STD) shall review and comment on the PQMP.
2.26 STD shall implement the quality program as outlined in this PQMP.
2.27 STD shall resolve and follow-up on any quality issues as relating to the system test in both
hardware and software.
2.28 STD will verify that all quality factors are implemented in the system for both hardware and
software.
2.29 STD will implement the system test practices, processes, and procedures as defined and in
accordance with other program and/or project planning documents.
Geeks on Ropes Version: Error! Unknown document property name. Error! Unknown document property name.
Revision Date: August 2013 Page 6 of 11

2.30 Software Engineering
2.31 The Software Engineering Department (SEGD) shall review and comment on the PQMP.
2.32 SEGD shall implement the quality program as outlined in this PQMP.
2.33 SEGD shall resolve and follow-up on any quality issues as relating to the software design and
development
2.34 SEGD will verify that all quality factors are implemented in the software.
2.35 SEGD will implement the software design and development practices, processes, and
procedures as defined and in accordance with other program and/or project planning
documents.
2.36 Software Test
2.37 The Software Test Department (STED) shall review and comment on the PQMP.
2.38 STED shall implement the quality program as outlined in this PQMP.
2.39 STED shall resolve and follow-up on any quality issues as relating to software test.
2.40 STED will verify that all software quality factors are implemented in the system.
2.41 STED will implement the software test practices, processes, and procedures as defined and
in accordance with other program and/or project planning documents.
2.42 Hardware Engineering
2.43 The Hardware Engineering Department (HEGD) shall review and comment on the PQMP.
2.44 HEGD shall implement the quality program as outlined in this PQMP.
2.45 HEGD shall resolve and follow-up on any quality issues as relating to the hardware design
and development
2.46 HEGD will verify that all quality factors are implemented in the hardware.
2.47 HEGD will implement the hardware design and development practices, processes, and
procedures as defined and in accordance with other program and/or project planning
documents.
2.48 Hardware Test
2.49 The Hardware Test Department (HTED) shall review and comment on the PQMP.
2.50 HTED shall implement the quality program as outlined in this PQMP.
2.51 HTED shall resolve and follow-up on any quality issues as relating to hardware test.
2.52 HTED will verify that all hardware quality factors are implemented in the system.
2.53 HTED will implement the hardware test practices, processes, and procedures as defined and
in accordance with other program and/or project planning documents.
2.54 Logistics
2.55 The Logistics Department (LD) shall review and comment on the PQMP.
2.56 LD shall implement the quality program as outlined in this PQMP.
Geeks on Ropes Version: Error! Unknown document property name. Error! Unknown document property name.
Revision Date: August 2013 Page 7 of 11

2.57 TOOLS, ENVIRONMENT, AND INTERFACES
2.58 The teams working on maintaining quality assurance on this project shall have access to the
facilities and the equipment necessary to perform quality assurance functions such as
process and product evaluations.
3 PROJECT QUALITY MANAGEMENT TASKS
The scheduling of tasks is determined by the development schedule. Therefore, a task is done in
relationship to what other development activities are taking place at any given moment. Various tasks
can be worked on concurrently until a task is completed. A task is considered completed when the
required sign-off reports are satisfactorily completed and any open action items have been closed. With
the coordination and cooperation of the team members the following tasks shall be performed:
3.1 EVALUATE SYSTEM REQUIREMENTS
During this task, the system requirements phase builds a mutual understanding of the customers
requirements and the development team. An agreement between the two is concreted and
maintained. The activities and goals during this phase are:
3.2 Make sure that the correct team members are involved in the system requirement process
to identify all participants needs.
3.3 Make sure that the requirements are reviewed for implementation feasibility.
3.4 Make sure that the requirements are clearly stated and consistent.
3.5 Make sure that all commitments are documented, reviewed, and signed.
3.6 Make sure that all processes for the documenting and allocating of the requirements are
followed and documented.
3.7 EVALUATE FACILITY REQUIREMENTS
During this task, PQM shall evaluate existing and planned facilities for adequacy. PQM shall assess
whether the facilities provide the needed equipment and space necessary for total system
development and support.
3.8 EVALUATE SYSTEM DESIGN PROCESS
During this task, a system behavioral design shall be determined and any other decisions shall be
made that well affect the selection and design of the system components. System architectural
design shall organize the system into subsystems. The subsystems shall be organized into individual
hardware items.
3.9 Make sure that the system design documents are kept current and consistent.
3.10 Make sure that the traceability matrix is kept current and consistent.
3.11 Make sure that the Peer Reviews of the design are in compliance to the requirements.
3.12 During the Peer Reviews, make sure that any identified defects in the design are reported.
3.13 During the Peer Reviews, make sure that any improvements or design alternatives are
reported.
3.14 Make sure that any previously identified defects have been resolved and properly recorded
utilizing the change control procedure.
Geeks on Ropes Version: Error! Unknown document property name. Error! Unknown document property name.
Revision Date: August 2013 Page 8 of 11

3.15 Identify any deviation from standards compliance and propose corrective actions.
3.16 Continuously review status of design milestones.
3.17 Verify that the requirements and the accompanying design and tools are in accordance with
the set standards. Determine whether waivers are needed prior to continuing with
development.
3.18 EVALUATE SOFTWARE DESIGN PROCESS
The preliminary design activity will determine the requirements for this phase. Based on the
requirements previously identified in a prior phase, the software is broken down into objects and
the function of each object and their relationships to one another are defined.

This project requires that all software be designed with great detail and that the utilization of
objects be enforced to satisfy the software allocated requirements. The level of detail that should
be placed into the design should be such that the coding of the computer program can be designed
or modified by someone other than the original programmer.
3.19 Make sure that the software design process and reviews are done in accordance with the
standards and procedures set forth by the project and as outlined in the Software
Development Plan (SDP).
3.20 Make sure than any action items resulting from reviews are resolved according to these
standards and procedures.
3.21 Verify that a method is set in place for the tracking and documenting of the development of
a software object.
3.22 Verify that the method of tracking and documenting the development of software objects is
kept current.
3.23 EVALUATE SOFTWARE IMPLEMENTATION AND UNIT TESTING
During this task, the process of unit testing of software is performed.
3.24 Make sure that the coding process, code reviews, and software unit testing are in
accordance with the standards and procedures as established by this project and as outlined
in the SDP.
3.25 Make sure that any action items generated during the review of the code are resolved in
accordance with the standards and procedures as established by this project and as outlined
in the SDP.
3.26 Verify that the method of tracking and documenting the development of software objects is
kept current.
3.27 EVALUATE HARDWARE DESIGN PROCESS
The preliminary design activity will determine the requirements for this phase. Based on the
requirements previously identified in a prior phase, the hardware is broken down into modules
(subsections) and the function of each module and their relationships to one another are defined.

3.28 Make sure that the hardware design process and reviews are done in accordance with the
standards and procedures set forth by the project and as outlined in the Hardware
Development Plan (HDP).
Geeks on Ropes Version: Error! Unknown document property name. Error! Unknown document property name.
Revision Date: August 2013 Page 9 of 11

3.29 Make sure than any action items resulting from reviews are resolved according to these
standards and procedures.
3.30 Verify that a method is set in place for the tracking and documenting of the development
and design of hardware modules.
3.31 Verify that the method of tracking and documenting the development of hardware designs
is kept current.
3.32 EVALUATE HARDWARE IMPLEMENTATION AND UNIT TESTING
During this task, the process of module testing of hardware is performed.
3.33 Make sure that the technical requirements, reviews, and hardware module and/or
component testing are in accordance with the standards and procedures as established by
this project and as outlined in the HDP.
3.34 Make sure that any action items generated during the review of the designs are resolved in
accordance with the standards and procedures as established by this project and as outlined
in the HDP.
3.35 Verify that the method for tracking and documenting the development and changes of
hardware designs is kept current.
3.36 EVALUATE END-ITEM DELIVERY PROCESS
During this task, the functional and physical audits of the final system shall be reviewed to verify
that all the requirements have been satisfied. PQM has the authority to refuse release or delivery of
the end-item, or certain items, if PQM determines that these items fail to meet contractual
requirements. Examples of items which can be refused for release consist of documentation, code,
or the final product.

The results of this process will be documented and provided to Project Management. Any
recommendations for corrective action at this point will require Project Management approval.
4 DOCUMENTATION
4.1 The documentation that describes and supports Geeks on Ropes Project Quality
Management Plan for the hardware and software development process shall be created and
updated on a periodic basis during the development life cycle of the project.
4.2 All documents will undergo a peer review according to the Peer Review Process.
4.3 Upon completion of the peer review, PQM will record and report the following to Project
Management:
4.3.1 The item reviewed.
4.3.2 The phase where the peer review was conducted.
4.3.3 The number of errors encountered.
4.3.4 The number of open action item reports.
4.3.5 The number of resolved action item reports.
Geeks on Ropes Version: Error! Unknown document property name. Error! Unknown document property name.
Revision Date: August 2013 Page 10 of 11

5 SUPPLIER CONTROL
5.1 PQM and project members will delineate and provide a complete list of requirements to the
supplier prior to any purchase.
5.2 The supplier will describe to PQM, or assigned proxy, the technical support that they offer,
the process that they require for the handling of user questions and problems, and the
handling and terms for hardware and software upgrades.

Geeks on Ropes Version: Error! Unknown document property name. Error! Unknown document property name.
Revision Date: August 2013 Page 11 of 11

APPENDIX A. LIST OF ACRONYMS

HEGD Hardware Engineering Department
HDP Hardware Development Plan
HTED Hardware Test Department
LD Logistics Department
PM Project Manager
PQM Project Quality Management
PQMP Project Quality Management Plan
SED Systems Engineering Department
SEGD Software Engineering Department
SDP Software Development Plan
STD System Test Department
STED Software Test Department
TL Team Leader