Integration Management Take out Your ITTO Docs

Formal Project Charter Charter Definition What is a Project Charter ? A Project charter is a 5 to 6 page document which collects all the information that has been developed in the previous steps and puts it in a central location. The Project charter serves as the constitution which governs the working of the project and disputes if any that may arise during the execution of the project. Review the Charter document on the site. Formal Project Charter

Team Integration is Central to All You Need to Do To Integrate a Project “My strengths, for example, are: futuristic, adaptable, strategic, and maximizing my energy--and also thinking in a way where I can connect everybody else (connection). My weaknesses sometimes lie in execution, so I complement that weakness with people that know how to execute.” Deepak Chopra, MD who teaches business at Northwestern University’s Kellogg School of Business

Integration Processes Develop the Charter Develop PM Plan (POP for us in class, using OPPM Methodology) Direct/Manage Project Execution Monitor/Control Project Work Perform Integrated Change Control Close Project OR Phase (All these activities or “processes” above relate to 5 “ing” Processes)

How They Look in a Picture

Ok, Here Come the Integration ITTOs Let’s see how they work The Develop Charter process -> Proj. Charter P. Charter becomes an input item to develop prelim project scope process which generates preliminary project scope statement which becomes  input item to the develop project management plan process, that -> project mgt. plan that becomes an input to various processes, including direct & manage project execution.

The direct and manage proj. execution process generates the work performance info, which becomes an input to the monitor and control proj. work process, which in turn generates -> Change reqs/recommendations for corrective action, preventive actions, and defect repairs. These recommendations become input items ->to the integrated change and control process.

The deliverables (results) from the integrated change control process become an input item to the close project process AND PROVIDES FEEDBACK to the direct and manage project execution process.

Understand Proj. INTEGRATION mgt = defining, identifying, unifying, and coordinating activities and processes within the PM Process Groups (ings). The PROJECT MANAGEMENT PLAN is the MAIN document to develop and be managed in this area. Your POP / OPPM makes working your plan easier.

Understand Recommendations and change reqs are made during the “monitor/control” process and are… Evaluated (rejected or approved) during the integrated change control process, and implemented during the direct and manage project “execution” process…

Understand Project management methodologies and project management information system are common tools and techniques for ALL the integration management processes. (in other words, the 5 processes of the integration area require them and are supported by those tools).

Examples Methodologies Critical Path Method (CPM) Critical Chain Project Management (CCPM) Event Chain Methodology (ECM) Six Sigma Scrum XP (Extreme Programming) Crystal FDD (Feature Driven Development) DSDM (Dynamic Systems Development) Adaptive Software Development RUP (Rational Unified Process) PRINCE2 Agile Waterfall

Examples PM Info Systems PM Software Comparison

Keeping an Eye on the Big Picture Integration, in addition to the point of ignition, is crucial to project success. It’s the process of holding everything together in a logical framework of interconnected tasks and responsibilities.

Understand! The integrated change control process can occur any time during the project lifecycle. Why is this logical? Because S**** Happens. All the time. Also please remember that the project charter is an input -> develop project management plan process.

Understand! Project Mgt. Plan is an input -> to all the processes of the Integration Mgt. Knowledge Area except the stuff that comes before its development: i.e., develop proj. charter, develop preliminary proj.scope statement, and develop proj. management plan. Only APPROVED changes are EVER made in formal project settings for CAPM

Understand! Formal closing process should apply for both complete and terminated projects. Administrative closure procedure is an output of the close project process, and not an input. When in doubt, on exams, read carefully and think logically.

More to Know Recognize – not necessarily memorize-- processes that fall under project integration management. Look at your ITTO resource or PMBOK. Who can authorize closure of the completed project, or any phase of it? The project sponsor

More to Know The documentation archive or file includes the lessons learned database (in whatever format that is)—typically made as part of the close project and contract closure processes.

Think Logically Which of the following is an output of the develop project charter process? Project charter Preliminary project scope statement Project management plan Final (approved) product, service, or result Answer is A.

Keep Thinking. This one is tougher. All of the following are tools and techniques used in the integrated change control process except: Expert judgment Project management information system Project management methodology Approved change requests Answer: D – approval is an output of it.

Keep Going… The integrated change control process is performed: During project execution only During project planning and execution From the project inception through completion During the project execution and controlling. Answer: C - throughout the project lifecycle, through all the processes and phases.

Last One Which of the following processes will be executed first? Develop the project mgt. plan Develop the preliminary project scope statement Direct and manage project execution Develop project charter Answer – D. Without the charter, no project exists.