Introduction

Introduction to Chapter 3 of HybridP3M: Hybrid Project Management and Agile Mindset.

The HybridP3M process of defining the project / programme focuses on a stable management environment based on the definition of a Project Approach, a key document used for consensus. This process also corresponds to the contents of a Project Brief and Project Initiation Document, not the documents themselves. Moreover, the PID is not necessarily one document, it can be a collection of several documents. Project Definition has a static part (objectives, scope, etc) and a dynamic part (business case, risk log, and project plan). In order to create a stable management environment it is useful to classify the project or programme. Therefore, this Chapter introduces various types of projects. Instead of introducing a new typology of projects, HybridP3M simply makes a distinction between the following project types:

• ACE (Aerospace, Construction, Engineering),
• Application software development,
• Tangible Product Development,
• R&D
• Change (e.g., implementation of software)
• Venture Life Cycle Management (start up, growth, maturity)
• Line Function projects, single-functional and cross-functional (from mini-undertakings with distinguishable start, middle and end to more complex tasks with clear role distribution). Note that business as usual is increasingly fading as work is more and more organized around projects.
• Legal projects
• Consultancy assignment
• Business development efforts

See the Process Data Diagram or Process Deliverable Diagram below for an impression of this basic project management funciton: