Practice Standard for Work Breakdown Structures - Softcover

Project Management Institute

 
9781628256192: Practice Standard for Work Breakdown Structures

Inhaltsangabe

The Work Breakdown Structure (WBS) serves as a guide for defining work as it relates to a specific project&;s objectives. This book supplies project managers and team members with direction for the preliminary development and the implementation of the WBS. Consistent with A Guide to the Project Management Body of Knowledge (PMBOK® Guide)-Sixth Edition, the WBS Practice Standard presents a standard application of the WBS as a project management tool. Throughout the book, the reader will learn what characteristics constitute a high-quality WBS and discover the substantial benefits of using the WBS in every-day, real-life situations.

Die Inhaltsangabe kann sich auf eine andere Ausgabe dieses Titels beziehen.

Über die Autorin bzw. den Autor

The Project Management Institute provides services including the development of standards, research, education, publication, networking opportunities in local chapters, hosting conferences and training seminars, and providing accreditation in project management.

Auszug. © Genehmigter Nachdruck. Alle Rechte vorbehalten.

Practice Standard for Work Breakdown Structures

By Project Management Institute Inc.

Project Management Institute, Inc.

Copyright © 2019 Project Management Institute, Inc.
All rights reserved.
ISBN: 978-1-62825-619-2

Contents

1. INTRODUCTION TO THE PRACTICE STANDARD FOR WORK BREAKDOWN STRUCTURES,
2. CONCEPTS AND PRINCIPLES,
3. RELATIONSHIPS, INTEGRATION, AND CONTEXT,
4 WBS QUALITY,
5 WBS APPLICATION AND USAGE,
REFERENCES,
BIBLIOGRAPHY,
APPENDIX X1,
APPENDIX X2,
APPENDIX X3,
GLOSSARY,


CHAPTER 1

INTRODUCTION TO THE PRACTICE STANDARD FOR WORK BREAKDOWN STRUCTURES


1.1 PURPOSE OF THIS PRACTICE STANDARD

A standard is a document established by consensus and approved by a recognized body that provides rules, guidelines, or characteristics for activities or their results. Standards aim to achieve the optimum degree of order in a given context through common and repeated use. Developing a standard follows a process based on the concepts of consensus, openness, due process, and applicability. PMI standards provide guidelines for achieving specific portfolio, program, and project management results, which apply to most projects, in most organizations, most of the time.

The purpose of a standard is to convey the what, not the how.

A practice standard differs from a standard by providing more explanations, specifications, and in-depth experience-based knowledge about a topic and its implementation. More importantly a practice standard is descriptive, not prescriptive. A practice standard conveys both the what and recommended how. It is important to note that the how aims to be a guideline for most projects, in most organizations, most of the time.

Objectives of the Practice Standard for Work Breakdown Structures – Third Edition are to:

[??] Provide a common ground for understanding the concepts and principles of the work breakdown structure (WBS);

[??] Present guidelines and recommended practices for the creation and use of the WBS; and

[??] Render standard application of the WBS as an essential mechanism to ensure integrated program and/or project schedule, cost, risk, resource, technical, and contractual control.


This practice standard promotes consistent application of the WBS, thus maximizing the effectiveness and efficiency of program or project planning and control efforts.

This practice standard also sets out to demonstrate what a quality WBS looks like, providing numerous examples throughout. In addition to the WBS examples, quality work breakdown structures are annotated in later sections, outlining the application of key principles. Appendix X3 of this practice standard comprises various industry-specific WBS examples. The examples demonstrate how to create and use work breakdown structures in different types of programs and projects. Some of these examples also illustrate the application of quality concepts on industry-related work breakdown structures.

The Practice Standard for Work Breakdown Structures – Third Edition elaborates on WBS-related guidance presented in A Guide to the Project Management Body of Knowledge (PMBOK® Guide) [1], The Standard for Program Management[2], and the Agile Practice Guide[3], based on literature, research, and practical application of work breakdown structures in industry today. Other PMI standards and practice standards also reference content found in this practice standard.

When referring to the processes of WBS creation and update, unless otherwise noted, the WBS applies to program and project interchangeably. Other sections of this practice standard discuss specific aspects pertaining to the content and application of the program WBS.

The Practice Standard for Work Breakdown Structures – Third Edition provides the framework to build, decompose, organize, utilize, and regularly update the WBS. This practice standard contains five main sections:

[??] Section 1 Introduction — This section provides the background and overview of a WBS, its objectives, uses, and business value.

[??] Section 2 Concepts and Principles — This section presents the core concepts and principles of using the WBS; discusses its implementation in different project life cycles; and describes methods and instructions on how the WBS applies, all of which are accompanied by numerous examples.

[??] Section 3 Relationships, Integration, and Context — This section provides the project-wide context of the WBS by describing its integration with other standards and other project management processes. Cross-process examples for the four main project life cycles demonstrate the project-wide context.

[??] Section 4 WBS Quality — This section presents specific quality guidelines and checklists that serve as a framework for ensuring the completeness and correctness of the WBS. It also explains the usage of a quality WBS in programs and projects.

[??] Section 5 WBS Application and Usage — This section provides the necessary guidelines required for the actual application of the WBS, from WBS creation throughout the entire project life cycle. This section also covers the application of work breakdown structures for programs.

[??] The Appendixes of the Practice Standard for Work Breakdown Structures – Third Edition comprise numerous examples of work breakdown structures for a multitude of project types, industries, market segments, and project life cycles, to provide the reader with as comprehensive an understanding as possible of the applicability of the WBS.


1.2 OVERVIEW

A project is a temporary endeavor undertaken to create a unique product, service, or result. This very often involves a significant amount of uncertainty. A project, in its entirety, is an endeavor that has not been carried out before, hence it carries with it a certain degree of risk.

Successful project management, regardless of the project's life cycle approach, depends on a thorough and complete planning process, which in its essence is multidisciplined and involves technical and subject-matter aspects. The differing viewpoints on scope, schedule, cost, and risk are crucial during the planning stage. Planning begins by defining the project goals and objectives with sufficiently detailed information and specifying the precise deliverables the project typically creates. The project's scope of work derives from these definitions and specifications, whereas the WBS establishes the framework for planning, controlling, executing, and managing the project's work to its completion and successfully handing over its deliverables.


1.2.1 WHAT IS A WBS?

A WBS is a hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables. Whereas the project scope statement describes the project scope and its major deliverables, assumptions, and constraints, the WBS elaborates on this description by defining, and hierarchically organizing, the total scope of the project. The WBS represents the entirety of the work specified in the current approved project scope.


1.2.2 WHY IS A WBS REQUIRED?

The WBS is a practical tool assisting the project planning team in overcoming large uncertainties. The WBS aids in converting an uncertain challenge into a series of...

„Über diesen Titel“ kann sich auf eine andere Ausgabe dieses Titels beziehen.