Book Image

Oracle Primavera P6 Version 8: Project and Portfolio Management

Book Image

Oracle Primavera P6 Version 8: Project and Portfolio Management

Overview of this book

In 2008 Oracle acquired Primavera Software, Inc., a leading provider of Project Portfolio Management (PPM) solutions for project-intensive industries.Primavera P6 Enterprise Project Portfolio Management is an integrated project portfolio management (PPM) solution comprising role-specific functionality to satisfy each team member's needs, responsibilities, and skills. It provides a single solution for managing projects of any size, adapts to various levels of complexities within a project, and intelligently scales to meet the needs of various roles, functions, or skill levels in your organization and on your project team.Oracle Primavera P6 Version 8: Project and Portfolio Management aims to show you all the features and functionality of the software thoroughly and clearly.With Oracle Primavera P6 Version 8: Project and Portfolio Management, readers will master the core concepts of Primavera P6 and the new features associated with version 8.This book is divided into two sections, in the first section we learn the fundamental concepts behind managing projects which include organizing projects, adding activities and relationships, assigning roles and resources, scheduling a project, and much more. In the second section we cover portfolio management and how to make the best use of the web client that includes working with portfolios, portfolio analysis, portfolio capacity planning, ROI, tracking performance, and lots more.
Table of Contents (25 chapters)
Oracle Primavera P6 Version 8: Project and Portfolio Management
About the Authors
About the Reviewers

Work Breakdown Structure (WBS)

Within a project, activities can be grouped, filtered, planned, and organized by Work Breakdown Structure (WBS). The WBS classifies all of the deliverables of a project and is often formed into a hierarchy with an increasing level of detail. How WBS is defined varies by company and by project, but having a well-planned WBS is a key first step to implementing good project controls.

Consider any one of several standardized WBS structures:

  • UNIFORMAT II Elemental Classification for Building Elements (Publication NISTIR-6389)

  • UNIFORMAT II Classification for Bridge elements (NIST 1122)

  • DOT Specs for use in almost every public entity road project. FHWA publication FP-03, also see specific state DOT website for more specific documentation.

  • FAA Specs for use in every US airport/airfield construction project. FAA Publication AC 150/5370-10.

An example of WBS for a software development project could be:

  1. Needs assessment

  2. Design

  3. Coding

  4. Integration testing

  5. Implementation and rollout...