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
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Index

Oracle Primavera and scheduling best practices


To understand the most basic element of the schedule, we should first agree on the best practices. Under the conditions of these best practices, Oracle Primavera performs at its best:

  • The schedule should follow the rules of a Critical Path Method (CPM) schedule. In such a schedule there is a list of all activities required to complete the project. Each activity has a duration to complete, and each activity has at least one predecessor and one successor relationship. The Start Project Milestone and Finish Project Milestone are the only exceptions to this rule. This creates a relationship-driven schedule in which one set of activities will be the longest path and the earliest the product can be delivered. The activities within that primary path are critical, meaning they must occur on the calculated dates in order to deliver the entire project on time.

  • Lead times and Lag times are rarely used, though there are uses which are clear exceptions.

  • Constraints...