This preview shows page 1. Sign up to view the full content.
Unformatted text preview: ects. There are many others that may be useful on certain projects or in some application areas. The project team should also be aware of one of the fundamental tenets of modern quality management--quality is planned in, not inspected in. Project Project Management Management Body of Body of KnowledgeE L KnowledgeE PL MP AM SA S
Tools & Techniques
.1 .2 .3 .4 .5 Benefit/cost analysis Benchmarking Flowcharting Design of experiments Cost of quality Inputs
.1 .2 .3 .4 .5 Quality policy Scope statement Product description Standards and regulations Other process outputs Outputs
.1 .2 .3 .4 Quality management plan Operational definitions Checklists Inputs to other processes A Guide to the Project Management Body of Knowledge (PMBOK Guide) 2000 Edition 2000 Project Management Institute, Four Campus Boulevard, Newtown Square, PA 19073-3299 USA NAVIGATION LINKS ACROYMNS LIST ACRONYMS LIST 97 ACROYMNS LIST Chapter 8--Project Quality Management ment ment geE L geE PL P 8.1.1 Inputs to Quality Planning .1 Quality policy. Quality policy is "the overall intentions and direction of an organization with regard to quality, as formally expressed by top management" (4). The quality policy of the performing organization can often be adopted "as is" for use by the project. However, if the performing organization lacks a formal quality policy, or if the project involves multiple performing organizations (as with a joint venture), then the project management team will need to develop a quality policy for the project. Regardless of the origin of the quality policy, the project management team is responsible for ensuring that the project stakeholders are fully aware of it (e.g., through appropriate information distribution, as described in Section 10.2). .2 Scope statement. The scope statement (described in Section 126.96.36.199) is a key input to quality planning since it documents major project deliverables, as well as the project objectives that serve to define important stakeholder requirements. .3 Product description. Although elements of the product description (described in Section 188.8.131.52) may be embodied in the scope statement, the product description will often contain details of technical issues and other concerns that may affect quality planning. .4 Standards and regulations. The project management team must consider any application area-specific standards or regulations that may affect the project. Section 2.5.1 discusses standards and regulations. .5 Other process outputs. In addition to the scope statement and product description, processes in other knowledge areas may produce outputs that should be considered as part of quality planning. For example, procurement planning (described in Section 12.1) may identify contractor quality requirements that should be reflected in the overall quality management plan. 8.1.1 | 184.108.40.206 8.1.2 Tools and Techniques for Quality Planning .1 Benefit/cost analysis. The quality planning process must consider...
View Full Document
- Fall '13
- The American