4squareviews

1. Introduction

In this next series of posts on memorizing the processes, we move on to the final step 6, which is memorizing the INPUTS & OUTPUTS associated with each of the 47 processes.   In order to breakdown the memorization into more bite-size chunks, I am breaking down the processes in the 10 knowledge areas into 2 or 3 posts each.

2.  Review of Processes, Tools & Techniques in Integration Knowledge Area

For a review of the following two processes and their tools & techniques, please see previous posts (look in the search function under “Chapter 4”).     As usual, the generic inputs EEFs stand for “Enterprise Environmental Factors” and OPAs stand for “Operational Process Assets.”

Process Name	Tools & Techniques	Inputs	Outputs
4.5 Perform Integrated Change Control	1.  Expert judgment 2.  Meetings 3.  Change Control Tools	1.  Project management plan 2.  Work performance reports 3.  Change requests 4.  EEFs 5.  OPAs	1. Approved change requests 2. Change log 3. Project management plan updates 4. Project documents updates
4.6 Close Project or Phase	1.  Expert judgment 2.  Analytical techniques 3.  Meetings	1.  Project management plan 2. Accepted deliverables 3.  OPAs	1. Final product, service, or result transition 2. OPAs updates

3.  Outputs of Integration Knowledge Area processes 4.5 and 4.6

We will discuss the outputs of the processes first before the inputs.

a.  Approved change requests (4.5 Perform Integrated Change Control)

Since the purpose of the process is to take change requests, analyze them and then either approve or reject them, it should make sense that this is the most basic (and most important) of the outputs of the process.

b.  Change log (4.5 Perform Integrated Change Control)

What happens if the change is rejected instead of approved?    It gets captured in the change log, which lists the details of all proposed changes, and whether they are approved or rejected.  If they are rejected, the reason for the rejection is given.

c.  Project management plan updates (4.5 Perform Integrated Change Control)

The changes to the project may require the adjustment of other constraints.   Both the changes and the other adjustments made to accommodate them must be reflected in the performance baselines and the affected subsidiary plans that deal with those constraints.

d.  Project document updates (4.5 Perform Integrated Change Control)

All documents that are part of the formal change control process will be updated as the result of a change request.

e.  Final product, service, or result transition (4.6 Close Project or Phase)

The final product, service, or result is transferred from the organization that has done the project to either the customer or sponsor who requested it.

f.  OPAs

The OPAs that are updated as a result of the process 4.6 Close Project or Phase include:

• Project files (project management plan, risk registers, change management documentation)
• Project closure documents (customer acceptance documentation, financial closure documentation, etc.)
• Historical information (lessons learned, etc.) to be used on future projects

4.  Inputs of Integration Knowledge processes 4.5 and 4.6

a.  Project management plan (4.5 Perform Integrated Change Control)

In particular, the parts of the project management plan that are used as inputs for the process 4.5 Perform Integrated Change Control are:

• scope baseline (scope statement, WBS, and WBS dictionary)
• scope management plan (includes procedures for scope changes)
• change management plan (provides direction for managing the change control process and documents the format change control board or CCB)

The parts of the project management plan that are used as inputs for the process 4.6 Close Project or Phase are:

• The agreement between the project manager and project sponsor on what constitutes successful project completion

b.  Work performance reports (4.5 Perform Integrated Change Control)

Earned value measurement reports and reports about resource availability.

c.  Change requests (4.5 Perform Integrated Change Control)

These are what are to be analyzed and either approved or rejected as part of this process.

d.  EEFs (4.5 Perform Integrated Change Control)

• Project management information system (Microsoft Project, Primavera, etc.)

e.  OPAs

The OPAs that are inputs of the process 4.5 Perform Integrated Change Control include:

• Change control procedures
• Procedures for approving and issuing change authorizations
• Process measurement database (measurement data on processes and products)
• Project documents (performance baselines, project calendars, project schedule network diagrams, risk registers, planned risk response actions, and defined risk impacts)

The OPAs that are inputs of the process 4.6 Close Project or Phase include:

• Project or phase closure guidelines or requirements
• Historical information and lessons learned knowledge base

f.  Accepted deliverables (4. Close Project or Phase)

The documentation for accepted deliverables may include such items as

• approved product specifications
• delivery receipts
• work performance documents

That covers the inputs and outputs for the last two processes of the Integration Management Knowledge Area.  The next post will start the same coverage of the inputs and outputs of the next chapter of the 5th Edition of the PMBOK Guide, Scope Management.

Filed under: Uncategorized |