1 Description of Program Management Processes (Initiating, Planning)
2 Topics Covered Program Management Process Groups salient features Description of all processes in Initiating Process Group: Initiate Program Authorize Program Initiate Team Description of all processes in Planning Process Group: Develop Program Management Plan Interface Planning Transition Planning Resource Planning Scope Definition Create Program Work Breakdown Structure Schedule Development Cost Estimating and Budgeting Quality Planning Human Resource Planning Communications Planning Risk Management Planning and Analysis Plan Purchases and Acquisitions Plan Program Contracting
3 Summary of Program Management Process Groups There are five Program Management Process Groups (briefly discussed below, and covered in detail in next chapter) Initiating Process Group: This defines and authorizes the program or a project within the program Planning Process Group: This describes the best alternative courses of action to deliver the benefits of the program Executing Process Group: This integrates projects, people, and other resources to carry out the plan for the program and deliver the program's benefits. Monitoring and Controlling Process Group: This requires that the program and its component projects be monitored against the benefit delivery expectations and appropriate corrective actions taken if necessary. Closing Process Group: This formalizes acceptance of a product, service, or benefit and brings the program to an orderly end.
4 Initiating Process Group Initiation of a program can be because of as the result of : a strategic plan a strategic initiative to fulfil an initiative within a portfolio The result of a decision to bid for a contract from an external customer. Three important activities are performed during the Initiate Process Group: 1. Initiate Program 2. Authorize projects 3. Initiate Team
5 Initiating Process Group (Initiate Program) 1. Initiate Program 2. Authorize projects 3. Initiate Team Main objectives of Initiate program are to: Help define the scope and benefit expectations of the program. Ensure that authorization and initiation of the program are linked to the organization's ongoing work and strategic priorities. Please note(optional): This process is similar to the processes, Develop Project Charter, Develop Preliminary Project Scope Statement for projects: for clarifications and better understanding, you may refer to Page 81 Page 88, PMBOK Third Edition
6 Initiating Process Group (Initiate Program) continued Major inputs and outputs for Initiate Program include INPUTS 1. Business Case 2. Investment Analysis 3. Funding for the initial phases of program 4. Organizational strategic and tactical plans OUTPUTS 1. Documentation for contract or statement of work 2. Program Charter 3. Program Manager identification 4. Program scope statement (preliminary) 5. Program Benefits statement 6. Program Selection Criteria 7. Benefits Realization plan 8. Program Sponsor Identification
7 Initiating Process Group (Initiate Program - Inputs) 1. Business Case (Input): The organization s strategic plan and business needs help define the business case for the program (i.e. why the program should be undertaken) 2. Investment Analysis (Input): This includes analysis of what kind of investment would be required for the program including financial ratios for the program e.g. Return on Investment, Payback Period, Internal Rate of Return(IRR) and Net Present Value(NPV) 3. Funding for the initial phases of the program(input): Some funding is required initially to do the high level estimates of cost, time etc. for the project and to support the funding requirements for the program management team when the program is initiated 4. Organizational strategic and Tactical Plans(Input): It is important to know about the Organizational strategic plan so that the selected programs provide benefits to aid the Organization s long term goals.
8 Initiating Process Group (Initiate Program - Outputs) 1. Documentation for contract or statement of work (Output): If some work for the program is going to be done as part of a contract, the documentation for the contract or statement of work will be an output from this process and will define the work which will be contracted to an external vendor 2. Program Charter (Output): The program charter links the program to the ongoing work of the organization. It often contains the vision statement that defines the desired organizational end state to follow for successful completion of the program, and is used as the vehicle to authorize the program 3. Program Manager identification: The Program Manager should be identified as early as possible (preferably during the Initiate Program phase) 4. Program scope statement (preliminary): This includes objectives and high-level deliverables of the program.
9 Initiating Process Group (Initiate Program - Outputs) 5. Program Benefits statement: This is a comprehensive statement which clearly states the benefits that will be derived from the program and helps the program management team justify costs and resource allocations. 6. Program Selection Criteria: There might be multiple programs which the company can select from. The Program Selection Criteria lists down the criteria which were used to select a particular program 7. Benefits Realization plan: Once the Program Benefits statement is finalized, the Benefits Realization plan states how the benefits from the program would be realized over a period of time. 8. Program Sponsor Identification: Every program should identify a program sponsor (or program champion) who would be responsible for providing funding for the program and helping the program get appropriate resources for successful implementation.
10 Initiating Process Group (Authorize Projects) 1. Initiate Program 2. Authorize projects 3. Initiate Team Main objectives of Authorize program are to: Perform the program management activities to initiate a component within the program. Develop a business case that will secure funding for and allocating budget to the project Ensure that a program manager is assigned Communicate project-related information to the stakeholders Redeploy of human and other resources from one project or activity to another Update all program-level documentation and records dealing with the project to reflect the new status of the projects
11 Initiating Process Group (Authorize Projects) continued Major inputs and outputs for Initiate Program include: INPUTS 1. Program Scope Statement 2. Project Selection Criteria 3. Strategic Plan OUTPUTS 1. Program Reporting Requirements 2. Project Charter 3. Project Manager Assignment 4. Project Sponsor Identification 5. Project Funding Approval Please note: The Program Manager may be the sponsor of individual projects The Program Manager will be involved with determining the project charter of projects in the program : so, all the projects should be aligned with the program objectives
12 Initiating Process Group (Initiate Team) 1. Initiate Program 2. Authorize projects 3. Initiate Team Main objectives of Initiate Team are to: Ensure that human resources are assigned to and working on the program. (assignment could be either from inside the organization or by acquiring resources through external recruitments) Develop a team to accomplish the tasks necessary to commence the Planning Processes some of these resources may be redeployed and other resources may be included as part of the program for Execution and subsequent phases.
13 Initiating Process Group (Initiate Team) continued Major inputs and outputs for Initiate Program include: INPUTS 1. Recruitment Practices 2. Staffing pool description OUTPUTS 1. Core Program Team Assignments 2. Program Manager Assignment 3. Program Team Directoryzz Please note: The Staffing Pool description provides a description of the resources in the resource pool who may be available for selection in the program The Program Manager should definitely be assigned at this stage to lead the Program Management Team during the Planning Processes
14 Planning Process Group The Planning Process Group contains the processes needed to determine how the program will be implemented and position it for successful execution. These processes involve formalizing the scope of the work to be accomplished by the program and identifying the deliverables that will satisfy the program's goals. The most important output of the Planning Process Group is the Program Management Plan, which defines how the program will be carried out. This also includes all the other subsidiary plans created as part of the planning process group.
15 Planning Process Group (continued) The Planning Process Group contains 14 processes as mentioned below: MONITORING AND CONTROLLING PROCESS I N I T I A T I N G P R O C E S S 1. Develop Program Management Plan 8. Cost Estimating and Budgeting 9. Quality Planning 2. Interface Planning 7. Schedule Development 10. Human Resource Planning 14. Plan Program Contracting 3. Transition Planning 6. Create Program WBS 11. Communications Planning 13. Plan Program Purchases, Acquisitions 4. Resource Planning 5. Scope Definition 12. Risk Management Planning, Analysis E X E C U T I N G P R O C E S S CLOSING PROCESS
16 Planning Process Group (1. Develop Program Management Plan) Main objectives of Develop Project Management Plan are to: Consolidate the outputs of the other Planning Processes, including strategic planning, to create a consistent, coherent set of documents that can be used to guide program execution, monitoring and control and closing Develop the following subsidiary plans (which are included as part of Program Management Plan): Benefits management plan Communications management plan Cost management plan Contracts management plan Interface management plan Scope management plan Procurement management plan Quality management plan Resource management plan Risk response plan Schedule management plan Staffing management plan.
17 Planning Process Group (1. Develop Program Management Plan) continued Major inputs and outputs for Develop Program Management Plan include: INPUTS 1. Subsidiary Plans 2. Project Planning process outputs OUTPUTS 1. Program Management Plan 2. Program Benefits Statement (updates) Please note: Develop Program Management Plan is an iterative process and the Program Management Plan is a living document (i.e. it can be regularly updated and changed during the program planning and implementation processes) Please note(optional): This process is similar to the process, Develop Project Management Plan for projects: for clarifications and better understanding, you may refer to Page 88 Page 91, PMBOK Third Edition
18 Main objectives of Interface Planning are to: Planning Process Group (2. Interface Planning) Identify the interrelationships that exist within a program with other programs in the portfolio or with factors outside the program. It involves describing the characteristics of these interfaces and creating the plan to ensure that these interfaces are established and maintained. Identify interdependencies and communications channels between different interfaces of the program with other programs/portfolios
19 Planning Process Group (2. Interface Planning) continued Major inputs and outputs for Interface Planning include: INPUTS 1. Communications Management Plan 2. Staffing Management Plan 3. Program Schedule 4. Risk Register 5. Stakeholder Analysis Chart 6. Program Work Breakdown Structure OUTPUTS 1. Interface Management Plan 2. Program Interfaces 3. Program Schedule (updates) 4. Requirements for individual project communications planning Please note: Interface Planning is usually done in conjunction with Human Resource Planning and Communications Planning Processes. Interface Planning not only helps in identifying interdependencies; it also helps in determining the formal communication channels and decision making relationships (valuable information required for communications planning)
20 Main objectives of Transition Planning are to: Planning Process Group (3. Transition Planning) Identify and Plan for transitions from the program team to the recipients of on-going activities that result from the program (this ensures that program benefits are sustained once they are transferred to the organization) Ensure that the scope of the transition is defined, the stakeholders in the receiving organizations or functions are identified, the program benefits are measured and sustainment plans exist, and the transition itself is eventually executed successfully.
21 Planning Process Group (3. Transition Planning ) continued Major inputs and outputs for Transition Planning include: INPUTS 1. Program Scope Statement 2. Program Schedule 3. Stakeholder Analysis Chart OUTPUTS 1. Transition Plan 2. Transition Agreement Please note: Within the life of the program, there may be multiple transition events as individual projects close, as interdependent projects close, or as other work activity within the program close The receiver in the transition process will vary depending on the event and on the program type. A product support organization could be the receiver for a product line that a company develops. For a service provided to customers, it could be the service management organization. If the work products are developed for an external customer, the transition could be to the customer's organization
22 Main objectives of Resource Planning are to: Planning Process Group (4. Resource Planning) Determine the people, equipment, materials and other resources that are needed, and in what quantities, in order to perform program activities Ensure efficient allocation of resources across projects in the program to ensure that they are not overcommitted. Lessons Learned, Organizational Process Assets and Historical information regarding what types of resources were required for similar projects on previous programs should be used if available. Please note(optional): This process is similar to the process, Activity Resource Estimating for projects: for clarifications and better understanding, you may refer to Page 135 Page 143, PMBOK Third Edition
23 Planning Process Group (4. Resource Planning) continued Major inputs and outputs for Resource Planning include: INPUTS 1. Program Schedule 2. Resource Pool Description 3. Program Scope Statement 4. Program Work Breakdown Structure (PWBS) OUTPUTS 1. Resource Management Plan 2. Resource Requirements Please note: In Resource Planning, priority should be given to those skills that are critical to the program but are not possessed by any program team members.
24 Main objectives of Scope Definition are to: Planning Process Group (5. Scope Definition) Develop the program scope statement, which becomes the basis for future program decisions. It also identifies the scope boundaries of the program. Develop the scope management plan which identifies how the scope will be managed throughout the program and how to handle scope change. Please note(optional): This process is similar to the processes, Scope Planning and Scope Definition for projects: for clarifications and better understanding, you may refer to Page 103 Page 112, PMBOK Third Edition
25 Planning Process Group (5. Scope Definition) continued Major inputs and outputs for Scope Definition include: INPUTS 1. Program Charter 2. Benefits Realization Plan 3. Preliminary Program Scope Statement OUTPUTS 1. Program Scope Statement 2. Scope Management Plan Please note: Scope is progressively elaborated i.e. we may have less information about scope early on by the scope will be better defined at the later phases of the program.
26 Planning Process Group (6. Create Program WBS ) Main objectives of Create Program WBS are to: Produce a program work breakdown structure (PWBS) that clearly communicates from the program-level perspective: The technical objectives of the program The final products, services, or results of the work to be performed Clarify the scope of the program, help identify logical groupings of work for the projects/operations involved in the program, identify the program interfaces. The decomposition should stop at the level of control required by the program manager. Typically, this will correspond to the first one or two levels of the WBS of the included project/operations. In this way, the PWBS serves as the controlling framework for developing the program schedule, and defines the program manager's management control points that will be used for earned value management, as well as other purposes. Please note(optional): This process is similar to the process, Create WBS for projects: for clarifications and better understanding, you may refer to Page 112 Page 118, PMBOK Third Edition
27 Planning Process Group (6. Create Program WBS) continued Major inputs and outputs for Create Program WBS include: INPUTS 1. Scope Management Plan 2. Program Scope Statement 3. Benefits Realization Plan OUTPUTS 1. Program Management Plan(updates) 2. Program Work Breakdown Structure 3. Program Work Breakdown Structure Dictionary(PWBS) Please note: The PWBS components at the lowest level of the PWBS are known as program packages. The PWBS Dictionary (which is an integral part of the PWBS) contains the complete description of the PWBS components and any additional relevant details.
28 Planning Process Group (7. Schedule Development) Main objectives of Schedule Development are to: Define the program components needed to produce the program deliverables(this is done through progressive elaboration of the PWBS) Determine the order in which the components should be executed, Identify significant milestones during the performance period of the program Estimate the amount of time required to accomplish each milestone Create a plan by which the schedule will be managed over the life of the program. This schedule management plan becomes part of the program management plan. Please note(optional): This process is similar to the process, Schedule Development for projects: for clarifications and better understanding, you may refer to Page 143 Page 152, PMBOK Third Edition
29 Planning Process Group (7. Schedule Development) continued Major inputs and outputs for Schedule Development include: INPUTS 1. Basis of Estimates 2. Calendars 3. Milestones 4. Program Work Breakdown Structure (PWBS) 5. Project Schedule Information 6. Resource capabilities and availability 7. Internal and External Dependencies OUTPUTS 1. Program Schedule 2. Resource Requirement(updates) 3. Schedule Management Plan Please note: During schedule development, we determine the timing of the program packages this helps to forecast the date on which the program will finish, as well as finish dates for the important milestones within the program
30 Planning Process Group (8. Cost Estimating and Budgeting) Main objectives of Cost Estimating and Budgeting are to: Aggregate all costs at the program level into a program estimate. Establish budgets for the program based on the budgets for the individual projects, the non-project activity and any financial constraints that impose boundaries on the budget. The latter may be a consequence of fiscal year budgetary planning cycles or funding limits for particular periods. Please note (optional): This process is similar to the processes, Cost Estimating and Cost Budgeting for projects: for clarifications and better understanding, you may refer to Page 157 Page 171, PMBOK Third Edition
31 Planning Process Group (8. Cost Estimating and Budgeting) continued Major inputs and outputs for Cost Estimating and Budgeting include: INPUTS 1. Basis for Estimates 2. Funding Availability 3. Program Work Breakdown Structures (PWBS) 4. Resource Management Plan 5. Contingency reserve amount determinations OUTPUTS 1. Cost Management Plan 2. Program Budget Please note: Cost Estimating and Budgeting is done either by the program team for the entire program or aggregated based on individual estimates of projects and work packages.
32 Main objectives of Quality Planning are to: Planning Process Group (9. Quality Planning) Determine which standards that are relevant to the program and specify how to satisfy the standards. Take advantage of existing quality expertise and methodologies (ISO 9000, Six Sigma, etc.) within the program domain. Please note(optional): This process is similar to the process, Quality Planning for projects: for clarifications and better understanding, you may refer to Page 179 Page 187, PMBOK Third Edition
33 Planning Process Group (9. Quality Planning) continued Major inputs and outputs for Quality Planning include: INPUTS 1. Environmental Factors and Legislation 2. Product Description 3. Program Scope Statement OUTPUTS 1. Operational Definitions 2. Program Cost of Quality 3. Quality Checklists 4. Quality Improvement Objectives and plan 5. Quality Management Plan 6. Quality Metrics Please note: Quality Planning must happen early in the program to ensure that the competency is available during the planning stages of critical program activities and processes.
34 Planning Process Group (10. Human Resource Planning) Main objectives of Human Resource Planning are to: Identifying and assign program roles, responsibilities, and reporting relationships. Determine Internal organizational elements e,g. program management team, representatives from functional areas within the enterprise, such as finance and human resources, and key individuals in the project management teams that are under the jurisdiction of the program manager. Determine External organizational entities e.g. external end-users of the products delivered by the program, as well as other organizations with a stake in the program and its successful outcome Please note(optional): This process is similar to the process, Human Resource Planning for projects: for clarifications and better understanding, you may refer to Page 199 Page 209, PMBOK Third Edition
35 Human Resource Planning (10. Human Resource Planning) continued Major inputs and outputs for Human Resource Planning include: INPUTS 1. Core Program Team Assignments 2. Program Interfaces 3. Resource Management Plan 4. Staffing Requirements 5. Stakeholder analysis chart OUTPUTS 1. Organizational Chart 2. Role and Responsibility assignments 3. Staffing Management Plan Please note: The organizational chart is a hierarchical depiction of the organization hierarchy showing the different internal and external resources involved in the program
36 Planning Process Group (11. Communications Planning) Main objectives of Communication Planning are to: Determine the information and communication needs of the program stakeholders, This includes: Who needs what information, When the information is needed How the information will be communicated to stakeholders and by whom. Please note(optional): This process is similar to the process, Communications Planning for projects: for clarifications and better understanding, you may refer to Page 221 Page 228, PMBOK Third Edition
37 Planning Process Group (11. Communications Planning) continued Major inputs and outputs for Communications Planning include: INPUTS 1. Communications Requirements 2. Program Reporting Requirements 3. Program Charter 4. Program Scope Statement 5. Program Work Breakdown Structure (PWBS) 6. Stakeholder Analysis Chart OUTPUTS 1. Communications Management Plan 2. Communications Technology Requirements Plan Please note: Proper communications requirements must be conveyed as input to the projects to ensure that information capture from the projects is fed back into the program.
38 Planning Process Group (12. Risk Management Planning and Analysis) Main objectives of Risk Management Planning and Analysis are to: Identify the risks affecting the program and document their characteristics on a regular basis Perform Qualitative and Quantitative risk analysis of the effects of risks and conditions on the delivery of program benefits. This helps prioritise which risks have the greatest effect on the program objectives and which need to be addressed urgently Conduct Risk response planning to develop procedures and techniques to enhance opportunities and reduce threats to the delivery of program benefits. Please note(optional): This process is similar to the processes for Risk Management Planning for projects: for clarifications and better understanding, you may refer to Page 237 Page 264, PMBOK Third Edition
39 Planning Process Group (12. Risk Management Planning and Analysis) continued Major inputs and outputs for Risk Management Planning and Analysis include: INPUTS 1. Program Schedule 2. Program Budget 3. Program Work Breakdown Structure (PWBS) 4. Risk Categories 5. Stakeholder risk tolerance and thresholds OUTPUTS 1. List of identified and prioritized risks 2. Risk Response Plan Please note: It is important that the program management involvement in risk should support the risk management activities of the program components i.e. individual projects and operations The program manager is also responsible for managing a contingency reserve for the program
40 Planning Process Group (13. Plan Program Purchases and Acquisitions) Main objectives of Plan Program Purchases and Acquisitions are to: Analyze the program scope statement and the product descriptions in the program work breakdown structure (PWBS) to determine which PWBS elements will be produced using internal resources available to the program and which will be obtained from outside suppliers. This can be done through Make-or-buy Analysis techniques and helps us determine what to procure and when. Validate product requirements, and Develop procurement strategies. Please note(optional): This process is similar to the process, Plan Purchases and Acquisitions for projects: for clarifications and better understanding, you may refer to Page 269 Page 281, PMBOK Third Edition
41 Planning Process Group (13. Plan Program Purchases and Acquisitions) continued Major inputs and outputs for Plan Program Purchases and Acquisitions include: INPUTS 1. Program Scope Statement 2. Program Charter 3. Program Work Breakdown Structure (PWBS) 4. Resource Management Plan 5. Stakeholder analysis chart OUTPUTS 1. Contract Statement of work 2. Make-or-buy decisions 3. Procurement Management Plan 4. Program-specific qualified vendor list Please note: This process precedes the Plan Program Contracting Process and generates several outputs that become inputs to contract planning.
42 Planning Process Group (14. Plan Program Contracting) Main objectives of Plan Program Contracting are to: Identify the type and detail of documentation required to implement contracts for suppliers either external to or within the organization Produce the foundation and guidelines on which an effective program-level contract administration process can be implemented. Please note(optional): This process is similar to the process, Plan Contracting for projects: for clarifications and better understanding, you may refer to Page 281 Page 284, PMBOK Third Edition
43 Planning Process Group (14. Plan Program Contracting) continued Major inputs and outputs for Plan Program Contracting include: INPUTS 1. Procurement Management Plan 2. Contract Type 3. Legal Requirement of Contracts 4. Contract Statement of work OUTPUTS 1. Evaluations Criteria 2. Procurement Documents 3. Contracts Management Plan Please note: For a program, the range and complexity of documentation for contracting will be far greater than for a project. For example, most often contracting at the program level needs to address legal issues and considerations.
44 Summary of concepts learnt in this chapter In this chapter, we got a better understanding of : Salient features of Program Management Process Groups Description of all processes in Initiating Process Group Description of all processes in Planning Process Group We also discovered that several processes were similar to the project management processes as described in the PMBOK (appropriate references were provided where required) This will be valuable information for us in the next chapter where we discuss Executing, Monitoring and Controlling and Closing program management process groups in detail
45 Quiz for this chapter Quiz for this chapter (Description of Program Management Processes Initiating, Planning)
This document is part of a series that explain the newly released PMBOK 5th edition. These documents provide simple explanation and summary of the book. However they do not replace the necessity of reading
Project Management Body of Knowledge (PMBOK) (An Overview of the Knowledge Areas) Nutek, Inc. 3829 Quarton Road, Suite 102 Bloomfield Hills, Michigan 48302, USA. Phone: 248-540-4827, Email: Support@Nutek-us.com
Project Processes for a Project Click the Knowledge Area title (below and left in blue underline) to view the details of each Process Group. Project Process Groups and Knowledge Areas Mapping Project Process
1 CIS12-3 IT Project Management Input, Output and Tools of all Processes Marc Conrad D104 (Park Square Building) Marc.Conrad@luton.ac.uk 26/02/2013 18:22:06 Marc Conrad - University of Luton 1 2 Mgmt /
The Project Management Knowledge Areas as defined by PMI (PMBOK, 2004) is the processes required to ensure that the various elements of the project are properly coordinated. the processes required to ensure
PROJECT MANAGEMENT METHODOLOGY SECTION 3 -- PLANNING PHASE Table of Contents Introduction...3-1 Overview...3-1 The Process and the Project Plan...3-1 Project Objectives and Scope...3-1 Work Breakdown Structure...3-1
PROJECT MANAGEMENT PLAN TEMPLATE < PROJECT NAME > Date of Issue: < date > Document Revision #: < version # > Project Manager: < name > Project Management Plan < Insert Project Name > Revision History Name
Integration Initiating ning Executing Monitoring & Controlling Closing 4.1 Develop Charter Statement Of Work Business Case 4.2 Develop 4.3 Direct and Manage Work 4.4 Monitor and Control Work 4.5 Perform
Project Training Company Comparing PMBOK Guide 4 th Edition, Edition and STS Sauter Training & Simulation S.A. Avenue de la Gare 10 1003 Lausanne Switzerland Web: www.sts.ch E-mail: firstname.lastname@example.org Phone:
PORTFOLIO, PROGRAMME & PROJECT MANAGEMENT MATURITY MODEL (P3M3) 1st February 2006 Version 1.0 1 P3M3 Version 1.0 The OGC logo is a Registered Trade Mark of the Office of Government Commerce This is a Value
Minnesota Health Insurance Exchange (MNHIX) 1.2 Plan September 21st, 2012 Version: FINAL v.1.0 11/9/2012 2:58 PM Page 1 of 87 T A B L E O F C O N T E N T S 1 Introduction to the Plan... 12 2 Integration
Chapter 6 Project Time Management (PMBOK Guide) Mohammad A. Rajabi Dept. of Geomatics Eng., University it of Th Tehran Tel: +98 21 8833 4341, Cell: +98 912 132 5823 Email: email@example.com ir Homepage:
PMP Examination Tasks Puzzle game Here is a great game to play to test your knowledge of the tasks you will be tested on in the actual examination. What we have done is take each of the domain tasks in
Project Management Process Prepared by Jay Knape PMI Project Project is... temporary endeavor undertaken to produce a unique products, service or result. UITS Project Definition For Columbus State University
The Plan s Journey From Scope to WBS to Schedule Presented by: Rick Clare, CBAP, PMP, OCP, CSM PM Centers USA, LLC. 2013 Company Background Consulting and Training (Virtual, Public and Private Training)
PROJECT MANAGEMENT PLAN CHECKLIST The project management plan is a comprehensive document that defines each area of your project. The final document will contain all the required plans you need to manage,
Assessment of NCTD Program Management Framework for Positive Train Control Program Subtask 2: Analysis Gap Analysis Prepared for: Brad Hansen, M.S., PMP Director, PMO Capital Projects May 2013 0 icfi.com/transportation
METHOD 12 3 empowering managers to succeed Project Management Guidebook ISBN 0-473-10445-8 A bout this e-book This e-book was created by Method123 (see www.method123.com) to help provide you with a simple
Partnering for Project Success: Project Manager and Business Analyst Collaboration By Barbara Carkenord, CBAP, Chris Cartwright, PMP, Robin Grace, CBAP, Larry Goldsmith, PMP, Elizabeth Larson, PMP, CBAP,
PMP Certification Preparation Course LATVIKON (R.E.P.)Centre ABOUT THIS COURSE Your ability as a project manager to demonstrate best practices in Project Management both on the job and through professional
Develop Project Tasks One of the most important parts of a project planning process is the definition of activities that will be undertaken as part of the project. Activity sequencing involves dividing
Managing IT Projects Chapter 2 The PMI Framework The PMI Framework The Project Management Institute,USA is an internationally acclaimed organization Devoted to Creation & sharing of knowledge in the area
PHASE 3: PLANNING PHASE The ning Phase focuses principally on required project planning work. Proper comprehensive project planning is essential to a successful IT project, and incomplete project planning
PHASE 3: PLANNING PHASE The Planning Phase focuses principally on required project planning work. Proper comprehensive project planning is essential to a successful IT project, and incomplete project planning
Introduction to the ITS Project Management Methodology In September 1999 the Joint Legislative Committee on Performance Evaluation and Expenditure Review (PEER) produced a report entitled Major Computer
A Guide To The Project Body of Knowledge (PMBOK) Significant Changes from the 3 rd edition to the 4 th edition Major Changes The adoption of the verb-noun format for process names Amplification as to Enterprise
Audit Checklist The following provides a detailed checklist to assist the audit team in reviewing the health of a project. Relevance (at this time) How relevant is this attribute to this project or audit?
By Dr. TD Jainendrakumar The main objective of any project is to fulfill the scope of the project on time and within the budget. What is Project Scope? Scope refers to all the work involved in creating
Time Management Part 2 Work Breakdown Structure (WBS) Review Richard Boser WBS Planning Process PMBOK WBS is deliverable-oriented grouping of components that organizes and defines the total scope of the
Application of Standard Project Management Processes in Fiber Optic Cable Plant Project Management Alfred Sankara, DigiBridge TelCo Introduction The Project Management Institute (PMI) is the world's leading
IT Project Management Practices Guide Introduction The IT Project Management Practices Guide (Guide) contains a repeatable, institutionwide approach for the management of application development and/or
Q1. (50 MARKS) A. List the nine PMBOK knowledge areas and give a one sentence description of the purpose of each knowledge area along with at least one output (document etc.) and its purpose. 1.Project
Project Time Management Study Notes PMI, PMP, CAPM, PMBOK, PM Network and the PMI Registered Education Provider logo are registered marks of the Project Management Institute, Inc. Points to Note Please
Introduction This comparison takes each part of the PMBOK and gives an opinion on what match there is with elements of the PRINCE2 method. It can be used in any discussion of the respective merits of the
Errata 1 st Printing NOTE: The following errata only pertain to the first printing of the PMBOK Guide Fifth Edition. In order to verify the print run of your book (or PDF), refer to the bottom of the copyright
TRICK SHEET on Project Management ITTO s (Input, Tool & Techniques, Output) Compiled by Abdulla Al Mamun, MBA, MCAS, PMP Based on PMBOK 5 th Edition Integration Management Project Charter Formal authorization
Agency Centralized IT Reference Model For State of Minnesota Agencies Planning and Version 2.0 March 8, 2012 658 Cedar Street Saint Paul, MN 55155 www.oet.state.mn.us PROVIDING THE LEADERSHIP AND SERVICES
Project Portfolio Management Maciej Bodych, MBA, PMP Bio Maciej Bodych, MBA, PMP Consultant, Trainer and Interim Manager in area of Portfolio Management and PMO PMI Region Mentor in charge of the Eastern
Interpreting the Management Process in IEEE/EIA 12207 with the Help of PMBOK Lewis Gray, Ph.D., PMP Abelia Fairfax, Virginia USA www.abelia.com Copyright 2002 by Abelia Corporation. All rights reserved
PM WORLD TODAY FEATURED PAPER MAY 2009 A Comparison of PMI s PMBOK Guide Versions 4 & 3 By Germán Bernate The Project Management Institute PMI announced on December 31, 2008 the availability of PMBOK Version
Project Standards: A Review of Certifications/Certificates Standards for Project Supporting Certification and Certificates Certificate Certification The Project Body of Knowledge PMBOK Guide Projects in
Scope Definition and Scope Management Purpose - To provide practical assistance for defining and managing project scope. This course will focus on tips for creating a scope statement rather than a step-by-step
The 9 Things in the PMBOK 9/15/2011 The PMBOK Project Body of Knowledge sum of knowledge within the profession of project management used dto document and standardize di generally accepted project management
Project Time Management Study Notes PMI, PMP, CAPM, PMBOK, PM Network and the PMI Registered Education Provider logo are registered marks of the Project Management Institute, Inc. Points to Note Please
Using PRINCE2 and MSP Together Andy Murray, Director, Outperform White Paper October 2010 2 Using PRINCE2 and MSP Together Contents 1 Purpose of this White Paper 3 2 Project and programme management context
5 PROJECT SCOPE MANAGEMENT Project Scope Management includes the processes required to ensure that the project includes all the work required, and only the work required, to complete the project successfully
Appendix V Risk Management Plan Template Version 2 March 7, 2005 This page is intentionally left blank. Version 2 March 7, 2005 Title Page Document Control Panel Table of Contents List of Acronyms Definitions
August 2007 Ten Steps to Comprehensive Project Portfolio Management Part 3 Projects, Programs, Portfolios and Strategic Direction By R. Max Wideman This series of papers has been developed from our work
1.20 Appendix A Generic Risk Management Process and Tasks The Project Manager shall undertake the following generic tasks during each stage of Project Development: A. Define the project context B. Identify
At the end of this chapter Project Charter Describe what a project charter is and why it is critical to project success. Explain what a project scope statement is and why it is important. List the various
Computing Services Network Project Prepared By: Todd Brindley, CSN Project Version # 1.0 Updated on 09/15/2008 Version 1.0 Page 1 MANAGEMENT PLANNING Project : Version Control Version Date Author Change
12 PROJECT PROCUREMENT MANAGEMENT Project Procurement Management includes the processes required to acquire goods and services from outside the performing organization. For simplicity, goods and services,
Project Management Guidelines Overview Section 86-1506 (5) directs the NITC to adopt guidelines regarding project planning and management. The goal of project management is to achieve the objectives of
Project Skills Team FME www.free-management-ebooks.com ISBN 978-1-62620-982-9 Copyright Notice www.free-management-ebooks.com 2014. All Rights Reserved ISBN 978-1-62620-982-9 The material contained within
1 ITIL Service Lifecycles and the Project Manager The intersection of IT Service and Project Delivery Presented to: Kansas City Mid-America PMI Chapter Mark Thomas January 17, 2011 1 Agenda 2 Introduction
1. Background and business case This section explains the context and why the project is being undertaken. It provides the justification for investing the time and resources in the project. 1.1 Reasons
IMEO International Mass Event Organization based on Recent Experience of Euro 2012 1. Name of the project: Project Management 2. Leader of the workshop (materials' author): Szymon Włochowicz 1 Objectives
2.1 Initiation Phase Overview The is the conceptualization of the project. This section describes the basic processes that must be performed to get a project started. Accordingly, the purpose of the is
Demonstrate and apply knowledge of project management in mechanical engineering 22918 version 2 Page 1 of 5 Level 6 Credits 15 Purpose This unit standard is intended primarily for use in diploma courses
The Project Management Life Cycle By Jason Westland (A book review by R. Max Wideman) 11/17/07 Introduction Editor's Note: We liked so much of this book that we asked for the author's permission to quote
Systems Analysis and Design in a Changing World, Fifth Edition Learning Objectives Explain the elements of project management and the responsibilities of a project manager Explain project initiation and
Overview of A Guide to the Project Management Body of Knowledge (PMBOK Guide) Fourth Edition Overview of: A Guide to the Project Management Body of Knowledge (PMBOK Guide) Fourth Edition 1 Topics for Discussion
From Houston S: The Project Manager s Guide to Health Information Technology Implementation. Chicago: HIMSS; 2011; pp 27 39. This book is available on the HIMSS online bookstore at www. himss.org/store.
The Agile PMO Kevin Thompson, Ph.D., PMP, CSP Agile Practice Lead cprime, Inc. 4100 E. Third Avenue, Suite 205 Foster City, CA 94404 Kevin.firstname.lastname@example.org Abstract The development of Agile processes
Project Portfolio Management: Metrics that Work James C. Brown Sr. Manager, Research PMO Pioneer Hi-Bred International Agenda PPM Interest What is Project Portfolio Management? Challenges Myths Benefits
i This Page Intentionally Left Blank i Table of Contents SECTION 1: INTRODUCTION AND OVERVIEW...1 SECTION 2: PROJECT CLASSIFICATION FOR OVERSIGHT...7 SECTION 3: DEPARTMENT PROJECT MANAGEMENT REQUIREMENTS...11
Crosswalk Between Current and New PMP Task Classifications Domain 01 Initiating the Project Conduct project selection methods (e.g., cost benefit analysis, selection criteria) through meetings with the
The Standard for Portfolio Management Paul E. Shaltry, PMP Deputy PM PPMS (2003-06) BNS02 Purpose of this Presentation To provide information about The Standard for Portfolio Management Agenda Background