Process Interconnection Diagrams

By Talha Elgazzar

Format: Presentation

A Guide to the Project Management Body of Knowledge (PMBOK® Guide) explains process inputs and outputs in a graphical representation, but shows this individually for each process without connecting the processes in a knowledge area in one diagram. This collection of maps not only achieves this, but also has connected all project processes (except the integration processes) in the same diagram with a minimum number of lines crossing. This collection of PDFs includes a diagram of each knowledge area that shows all of the internal connections, and then all are put together in one map.

Some documents (process outputs) are not connected to their corresponding inputs because connecting them will generate a high number of line crossings. These are: risk register, stakeholder register, scope baseline and resource calendar. Also, some inputs are not connected due to the same reason; all are indicated by red lines in the diagram.

The Project Integration Management Diagram is independent and requires no need to look at the other diagram to understand it. In contrast, the Processes Interconnection Diagram depends on the integration diagram because, as mentioned, around 50% of the inputs and outputs are moved from the knowledge area processes as typical inputs/outputs to the integration processes.

This Project Integration Management Diagram shows how integration management works, and how it interacts with typical knowledge area processes. The idea of a typical knowledge area is introduced here (shown in the right side of the diagram) to focus on the fact that integration management is almost interacting with other areas in a similar way. This idea dramatically minimizes the number of connection lines between the integration processes and the different knowledge area processes. Some untypical connections with specific processes are shown on the left side of the diagram.

The connections between integration processes and other project processes generates some kind of documents flow, or cycles. These are identified by different colors and have been given names that reflect their functions in the project (these names can be adjusted to PMI terms if required). The cycles detected in the design are: Project Planning, Flow of Project Deliverable, Change Management Cycle and Work Performance Reporting.

The Project Integration Management Diagram covers 54% of the 47 processes inputs and 33% of outputs listed in PMBOK® Guide.

People who downloaded this item also downloaded . . .

Premium Content
PMI Membership
$129 /year
(plus $10 application fee)
Sign up to download this deliverable and get unlimited access to our library of webinars, time-saving templates and more.
PMI Membership perks include job opportunities, local chapters, respected publications, and standards.   Learn more
Already a PMI Member? Log in now.



Reviews (7)

Login/join to subscribe

"One man alone can be pretty dumb sometimes, but for real bona fide stupidity there ain't nothing can beat teamwork."

- Mark Twain