The document outlines the knowledge areas and processes involved in program management. It provides a table mapping the major processes within each knowledge area against their primary inputs, tools and techniques used, and primary outputs. There are 12 knowledge areas described including program integration, scope, time, communications, and risk management. For each knowledge area there are typically 4-8 major processes defined such as develop program plan, monitor and control schedule, and plan risk management.
netmind - PMBOK 5 vs ISO 21500: diferencias y compatibilidadesnetmind
El año 2012 finalizó con dos importantes hitos en el avance y reconocimiento de la profesión de Project Management: la publicación de la quinta edición de PMBOK y la creación de un nuevo estándar internacional ISO para la dirección de proyectos.
¿Cómo afectará la aparición de esta nueva norma a la manera en qué las empresas gestionan sus proyectos? ¿Qué relación tiene con las metodologías y guías de conocimiento existentes? En concreto, ¿cuál es su relación con la guía PMBOK? ¿Son compatibles? ¿Cuáles son las principales diferencias entre ellas? ¿Qué novedades aporta PMBOK en su quinta edición?
Project Management is crucial for any company to accomplish project targets since it provides structured methods and systematic procedures. Thus, project management guarantees compliance with time, cost and quality constraints, e.g. in strategy, IT, R&D, web or constructions projects, ultimately ensuring the efficiency of the project. The presentation explains the most important terms, relationships, tasks and goals of project management, in particular the definition of project targets, project planning and project controlling practices.
netmind - PMBOK 5 vs ISO 21500: diferencias y compatibilidadesnetmind
El año 2012 finalizó con dos importantes hitos en el avance y reconocimiento de la profesión de Project Management: la publicación de la quinta edición de PMBOK y la creación de un nuevo estándar internacional ISO para la dirección de proyectos.
¿Cómo afectará la aparición de esta nueva norma a la manera en qué las empresas gestionan sus proyectos? ¿Qué relación tiene con las metodologías y guías de conocimiento existentes? En concreto, ¿cuál es su relación con la guía PMBOK? ¿Son compatibles? ¿Cuáles son las principales diferencias entre ellas? ¿Qué novedades aporta PMBOK en su quinta edición?
Project Management is crucial for any company to accomplish project targets since it provides structured methods and systematic procedures. Thus, project management guarantees compliance with time, cost and quality constraints, e.g. in strategy, IT, R&D, web or constructions projects, ultimately ensuring the efficiency of the project. The presentation explains the most important terms, relationships, tasks and goals of project management, in particular the definition of project targets, project planning and project controlling practices.
[AgileCMMI] Practical Experience Report: Application of Project Management ar...davidobama
The Capability Maturity Model Integration (CMMI) has been broadly used for assessing organizational maturity and process capability throughout the world. Although most of the customers give priority to CMMI certified organizations over others for guaranteeing the quality, the nature of their rapid market change can no longer accept heavyweight plans, requirements specification, change requests, contract negotiation, and other documentation. Moreover, the rapid change in information technology has caused increasing the frustration more, especially that there are new competitors started using lightweight processes that invite to customer collaboration over contract negotiation and working software over comprehensive documentation that is called “Agile” methodologies that have been adopted to tackle this challenge. Agile development methods and CMMI are often perceived to be at odds with each other. In fact, it’s possible to embrace both to dramatically improve business performance. This paper focuses on the verification of implementing CMMI Project Management process areas in agile organizations based on a real and practical experience in Agile and CMMI successful projects.
The authors are going to share their practical experiences in interpreting the CMMI model's project management practices in an Agile environment to address the model intent and not compromising on the credibility or value of the practices.
From http://www.ndia.org/meetings/0110
and http://www.agilecmmi.blogspot.com
I am Continuously seeking to improve my competencies and skills to provide first class professional Project Management training courses; and develop my scope experience in Project Management functions.
I am confident that my innovative and results-focused approach would make significant contribution to the continued success of your organization.
this is the first presentations uploaded to Slide Share,
For more information do not hesitate to contact me.
Ahmad H. Maharma - PMP®
Ramallah, Palestine
Phone: + (972) (2) 2968644
Mobile: + (972) (599) 001155E-Mail: ahmad.maharma@gmail.com
I am Continuously seeking to improve my competencies and skills to provide first class professional Project Management training courses; and develop my scope experience in Project Management functions.
I am confident that my innovative and results-focused approach would make significant contribution to the continued success of your organization.
this is the first presentations uploaded to Slide Share,
For more information do not hesitate to contact me.
Ahmad H. Maharma - PMP®
Ramallah, Palestine
Phone: + (972) (2) 2968644
Mobile: + (972) (599) 001155E-Mail: ahmad.maharma@gmail.com
George Jucan: Using PMCDF to Advance One's CareerPMI SWOC
George Jucan
George Jucan is a well known in the project management community as a successful IT project management consultant, speaker at public events, trainer and author of high-impact project management articles.
George is an experienced Project Manager Professional (PMP) with 20 years of technical and management experience in complex environments, both in public and private sector. He provides consulting services in methodology definition and capability assessment, business reengineering and organizational restructuring, projects audit and recovery, as well as hands-on management of projects.
George Jucan is currently a member of the Core Team for the upcoming PMBOK® Guide 5th Edition.
Moreover, George is currently the Vice-Chair of the Canadian Advisory Committee for the upcoming ISO 21500 project management standard. He is also the Chair of PMI Information Systems SIG, as well as a Board member of PMI Southern Ontario Chapter.
Agile Project Management for elearning developmentDon Bolen
Deck used in eLearning Guild DevLearn 11 presentation. See more links, resources at http://marginallycompetent.wordpress.com/2011/10/31/resources-for-elg-agile-pm-for-elearning-development/
Webinar on identifying, preventing and securing against the unidentifiable at...Intergence Ltd.
In this webinar we look at how the majority of today’s networks are vulnerable to a set of advanced attacks which can go undetected by many security systems. Advanced Evasion Techniques exist which can pass through firewalls and intrusion prevention systems, allowing an attacker to deliver a malicious payload to a vulnerable device, undetected.
Stonesoft’s Alan Cottom will demonstrate a live attack on an IPS-protected system using their Predator tool and how this attack can be blocked via the Stonesoft security suite of products.
Intergence will be demonstrating their cutting edge 3D visualisation tool Hyperglance which integrates with a number of network management and security systems including the Stonesoft products. Hyperglance will be used to visualise the IT infrastructure and identify where systems are vulnerable and pinpoint real time attacks, allowing administrators to take immediate action to secure their network.
[AgileCMMI] Practical Experience Report: Application of Project Management ar...davidobama
The Capability Maturity Model Integration (CMMI) has been broadly used for assessing organizational maturity and process capability throughout the world. Although most of the customers give priority to CMMI certified organizations over others for guaranteeing the quality, the nature of their rapid market change can no longer accept heavyweight plans, requirements specification, change requests, contract negotiation, and other documentation. Moreover, the rapid change in information technology has caused increasing the frustration more, especially that there are new competitors started using lightweight processes that invite to customer collaboration over contract negotiation and working software over comprehensive documentation that is called “Agile” methodologies that have been adopted to tackle this challenge. Agile development methods and CMMI are often perceived to be at odds with each other. In fact, it’s possible to embrace both to dramatically improve business performance. This paper focuses on the verification of implementing CMMI Project Management process areas in agile organizations based on a real and practical experience in Agile and CMMI successful projects.
The authors are going to share their practical experiences in interpreting the CMMI model's project management practices in an Agile environment to address the model intent and not compromising on the credibility or value of the practices.
From http://www.ndia.org/meetings/0110
and http://www.agilecmmi.blogspot.com
I am Continuously seeking to improve my competencies and skills to provide first class professional Project Management training courses; and develop my scope experience in Project Management functions.
I am confident that my innovative and results-focused approach would make significant contribution to the continued success of your organization.
this is the first presentations uploaded to Slide Share,
For more information do not hesitate to contact me.
Ahmad H. Maharma - PMP®
Ramallah, Palestine
Phone: + (972) (2) 2968644
Mobile: + (972) (599) 001155E-Mail: ahmad.maharma@gmail.com
I am Continuously seeking to improve my competencies and skills to provide first class professional Project Management training courses; and develop my scope experience in Project Management functions.
I am confident that my innovative and results-focused approach would make significant contribution to the continued success of your organization.
this is the first presentations uploaded to Slide Share,
For more information do not hesitate to contact me.
Ahmad H. Maharma - PMP®
Ramallah, Palestine
Phone: + (972) (2) 2968644
Mobile: + (972) (599) 001155E-Mail: ahmad.maharma@gmail.com
George Jucan: Using PMCDF to Advance One's CareerPMI SWOC
George Jucan
George Jucan is a well known in the project management community as a successful IT project management consultant, speaker at public events, trainer and author of high-impact project management articles.
George is an experienced Project Manager Professional (PMP) with 20 years of technical and management experience in complex environments, both in public and private sector. He provides consulting services in methodology definition and capability assessment, business reengineering and organizational restructuring, projects audit and recovery, as well as hands-on management of projects.
George Jucan is currently a member of the Core Team for the upcoming PMBOK® Guide 5th Edition.
Moreover, George is currently the Vice-Chair of the Canadian Advisory Committee for the upcoming ISO 21500 project management standard. He is also the Chair of PMI Information Systems SIG, as well as a Board member of PMI Southern Ontario Chapter.
Agile Project Management for elearning developmentDon Bolen
Deck used in eLearning Guild DevLearn 11 presentation. See more links, resources at http://marginallycompetent.wordpress.com/2011/10/31/resources-for-elg-agile-pm-for-elearning-development/
Webinar on identifying, preventing and securing against the unidentifiable at...Intergence Ltd.
In this webinar we look at how the majority of today’s networks are vulnerable to a set of advanced attacks which can go undetected by many security systems. Advanced Evasion Techniques exist which can pass through firewalls and intrusion prevention systems, allowing an attacker to deliver a malicious payload to a vulnerable device, undetected.
Stonesoft’s Alan Cottom will demonstrate a live attack on an IPS-protected system using their Predator tool and how this attack can be blocked via the Stonesoft security suite of products.
Intergence will be demonstrating their cutting edge 3D visualisation tool Hyperglance which integrates with a number of network management and security systems including the Stonesoft products. Hyperglance will be used to visualise the IT infrastructure and identify where systems are vulnerable and pinpoint real time attacks, allowing administrators to take immediate action to secure their network.
[FR] Cercle Premier RSE : COP 21, comment le digital peut aider ? #CercleRSEOrange Business Services
Vendredi 15 janvier 2016, Orange organisait une matinée #CercleRSE pour faire le point quelques semaines après la fin de la COP21 et explorer les pistes et leviers numériques capables d'aider les entreprises à réduire leur empreinte écologique.
Uncover tips for better integrating sales and marketing strategies. This session will provide insights and examples into how messages that revolve around customers’ and prospects’ and are delivered in a compelling and actionable ways help to close more deals.
For more than a decade Perron has been recognised for the quality and innovative design of some landmark New Zealand properties.
A privately owned group, Perron, through its specialist operating divisions has a reputation for producing quality developments, which include luxury apartments, hotel, retail, commercial offices, and storage facility developments.
Perron’s commitment to quality is more than just a by-line, Perron has been well recognised in the past two years with 19 National and International awards for construction and design excellence.
Fortalecimiento y desarrollo rural integral de los Afrocolombianos: el caso d...Fundación Acua
El presente documento fue elaborado entre mayo y agosto
de 2014 por la Fundación Activos Culturales Afro –acua–,
para el Fondo Internacional de Desarrollo Agrícola –fida–.
Su punto de partida es el trabajo que la Fundación realiza
desde 2007 con comunidades afrodescendientes en América
Latina, en la puesta en valor de sus activos culturales.
Programme start up document - Optimised Programme Methodology Simon Misiewicz
Optimise-GB provides you with a free template for the programme start up document. This is the first phase of a three phased programme methodology. This document is based on MSP, Lean and Six Sigma programme methodologies. The key difference and unique perspective for this methodology is that the programme never closes down but focuses on continuous improvement. This document reduces the number of documents that can often lead to confusion as identified in a number of methodologies. The document sets the reason for the programme in regards to operational strategies, objectives and balanced scorecard reporting. As with most programme management methodologies, the document focuses on the now (Current state / as is) again the future (to be / future state). There are several inbuilt excel templates to boot including objectives weighting mechanisms, SIPOC flow diagrams and business cases. The programme start up phase leads into the Programme Improvement plan, which identifies a number of initiatives to be authorised within the project portfolio. The third and final document in this methodology is the programme delivery report, another template, that reports back on the progress made against the strategic goals. Please contact me should you have any questions on simon@optimise-gb.com and visit www.optimise-gb.com for more details. Many thanks Simon Misiewicz
Version 5 is out, and this applies for the now older version 4 PMP exam. I will not likely update this, but if someone is interested in completing or revising this to version 5 standards let me know.
The Presentation is a part of Webinar held on 18-12-2011 and consists of the following topics:
1. PMP Quick Facts-What is PMP, PMI
2.How is Exam structurd and what are the associated expenses
3. What are Process Groups, Knowledge Areas and Processes
The Last Slide contains link to my site, where brief details about the topics mentioned in the presentation has been posted.
1. Program Management Process Groups and Knowledge Areas
Knowledge Initiation Planning Process Execution Monitoring Closing
Areas Process Process Process Process
1.1 Initiate 1.2 Develop Program 1.4 Direct and 1.6 Monitor and 1.8 Close
Program Management Plan Manage Control Program Program
1. Program 1.3 Develop Program Program Performance
Integration Infrastructure Execution
Management (8) 1.5 Manage 1.7 Manage
Program Program Issues
Resources
2.6 Manage
2.1 Plan Program Scope 2.8 Monitor and
Program
2.2 Define program Control Program
2. Program Architecture
Objectives and Goals Scope
Scope 2.7 Manage
2.3. Develop Program Component
Management (8) Requirements Interfaces
2.4. Develop Program
Architecture
2.5 Develop Program WBS
3.1 Develop Program 3.2 Monitor and
3. Program Time
Schedule Control Program
Management (2) Schedule
4. Program Cost
Management
5. Program
Quality
Management
6. Program HR
Management
7. Program 7.1 Plan Communication 7.2 Distribute 7.3 Report
Communication Information Program
Management (3) Performance
8.1 Plan Program Risk 8.5 Monitor and
Management Control Program
8. Program Risk 8.2 Identify Program Risks Risk
Management (5) 8.3 Analyze Program Risks
8.4 Plan Program Risk
Responses
9. Program 9.1 Plan Program 9.2 Conduct 9.3 Administer 9.4 Close
Procurement Procurements Program Program Program
Management (4) Procurements Procurements Procurement
10.1 10.2 Develop Program 10.5 Monitor and
Establish Financial Plan Control Program
10. Program
Program 10.3 Estimate Program Financials
Financial
Financial Costs
Management (5) Framework 10.4 Budget Program
Costs
11.1 Plan Program 11.3 Engage 11.4 Manage
11. Program Stakeholder Program Program
Stakeholder Management Stakeholders Stakeholder
Management (4) 11.2 Identify Program Expectations
Stakeholders
12.1 Plan and Establish 12.4 Approve 12.5 Provide 12.8
Program Governance Component Governance Approve
Structure Initiation Oversight Component
12.2 Plan for Audits 12.6 Manage Transition
12.3 Plan Program Quality Program Benefits
12. Program 12.7 Monitor and
Governance (8) Control Program
Changes
Sridhar Peddisetty - PgM ITTOs Page 1 of 10 Last Updated 9/1/2010
2. Program Integration Management
Knowledge Areas Major Processes Primary Inputs Tools & Techniques Primary Outputs
INTEGRATION
Initiate Developing the 1. Strategic Business 1. Expert Judgment 1. Assignment of
program charter that directive 2. Feasibility Studies Program Manager
Program formally authorizes 2. Business Case 3. Comparative 2. Program Charter
and initiates the 3. Existing Organizational Advantage Analysis 3. Business case
program structure and Policies 4. Cost/Benefit Analysis updates
4. Existing Organizational 4. Program Roadmap
Work
5. Existing Components
Develop The process of 1. Program Charter 1. Expert Judgment 1. Program
consolidating and 2. Program Roadmap 2. PMIS Management Plan
Program coordinating all 3. Existing Organizational 3. Tolerances 2. Program Roadmap
Management Subsidiary plans into a Work 4. Planning Techniques (updated)
program 4. Best Practices Library 5. Procurement Processes 3. Program Transition
Plan management plan as 6. PMO Plan
well as updating the
program roadmap
Develop The process of 1. Program Management 1. Expert Judgment 1. Core Team Assignments
identifying, assessing, Plan 2. Review meetings 2. Program Resource Plan
Program and developing the 2. Organizational Policies 3. Component Analysis 3. Program Infrastructure
Infrastructure infrastructure required and Guidelines 4. Capacity Planning 4. Program Management
to support the 3. Best Practices Library Processes
program 4. Program Roadmap
Direct and The process of 1. Program Management 1. Expert Judgment 1. Approved Change
managing the Plan 2. PMIS request
Manage execution of the 2. Program Performance 3. PMO 2. Component Initiation
Program program Reports 4. Contract Management Requests
management plan to 3. Change requests Plan 3. Component Transition
Execution
achieve program 4. Work Results 5. Decision Logs Request
objectives 5. Audit Reports 6. Impact Analysis 4. Program Issues Register
6. Go/No Go Decision 7. Tolerances 5. Program Roadmap
7. Program Roadmap (updated)
Manage The process of 1. Program Management 1. Expert Judgment 1. Program Resource Plan
tracking, assessing, Plan 2. PMIS (updated)
Program and adapting to the 2. Component Status 3. PMO
Resources use of resources Reports
throughout the 3. Resource Availability
program’s lifecycle 4. Program Resource Plan
Monitor and The process of 1. Program Management 1. Expert Judgment 1. Program Performance
monitoring and Plan 2. PMIS Reports
Control controlling 2. Program Performance 3. Earned Value 2. Forecast
Program the program’s Reports Management (EVM)
execution to meet 4. Review Meetings
Performance
performance 5. Program Performance
objectives as defined Analysis
in the program
management plan
Manage The process of 1. Program Management 1. Expert Judgment 1. Change Requests
addressing unplanned Plan 2. Issues Analysis 2. Program Issues register
Program Issues risks and events that 2. Audit Report (updated)
may impact the 3. Program Risk Register
program’s planned 4. Program Performance
directives. Reports
5. Program Issues Register
Close Program The process of 1. Program Management 1. Expert Judgment 1. Released Resources
finalizing all activities Plan 2. PMIS 2. Final Reports
across all of the 2. Program Transition Plan 3. Contract Closure 3. Knowledge Transition
program process 3. Program Closure Procedure 4. Closed Program
groups to formally Recommendation
close the program .
Sridhar Peddisetty - PgM ITTOs Page 2 of 10 Last Updated 9/1/2010
3. Program Scope Management
Knowledge Areas Major Processes Primary Inputs Tools & Techniques Primary Outputs
SCOPE
Plan Program The process of 1. Business Case 1. Expert Judgment 1. Program Scope
identifying and 2. Program Charter 2. PMIS Statement
Scope developing activities 2. Program Scope
to produce Management Plan
deliverables and
benefits that meet the
program goals and
objectives
Define The process for 1. Program Scope 1. Expert Judgment 1. Benefit Realization Plan
establishing the Statement 2. Interviewing 2. Program Scope
Program Goals overall goals and 2. Program Scope 3. Focus Groups Statement (updated)
and objectives of the Management Plan 4. Customer Acceptance
program and Review
Objectives ultimately what is to
be delivered
Develop The process for 1. Program Scope 1. Expert Judgment 1. Program Requirements
development and Statement 2. Requirement Gathering Document
Program formal identification of 2. Change Request 3. Requirement Analysis 2. Component
Requirements the program 3. Business Case 4. Brainstorming Requirements Document
requirements and 4. Program Roadmap 5. Design Reviews
specifications to 6. Requirement Validation
deliver the program & Verification
goals and objectives
Develop The process of 1. Program Requirements 1. Technical Knowledge 1. Program Architecture
defining the structure Document Baseline
Program of the programs
Architecture components and
identifies the
interrelationships
between all of the
program components
Develop This subdivides the 1. Program Architecture 1. Expert Judgment 1. Program WBS
program into its Baseline 2. WBS Templates 2. WBS Matrix
Program WBS constituent parts 2. Program Requirement 3. Management Planning
(components, Document Process
deliverables, and 3. Component Requirement 4. Task Responsibility Matrix
activities). Document 5. System Configuration
Tools
Manage The process for 1. Program Architecture 1. Expert Judgment 1. Program Architecture
managing the Baseline 2. Change Impact Analysis Baseline (updated)
Program relationships between 2. Program Management 2. Approved Change
Architecture all of the program Plan Request
components to ensure 3. Change Requests 3. Program Management
the program Plan (updated)
architecture remains
up to date
Manage The process for 1. Program Architecture 1. Expert Judgment 1. Approved Change
maintaining the Baseline 2. Communication Request
Component adherence of 2. Program Management Methods 2. Program Management
Interfaces program delivery and Plan 3. Review Meetings Plan (updated)
its constituent parts 3. Change Request 4. Conflict Management 3. Program
and managing 4. Communications Communications
interrelationships Management Plan Management Plan
between the Program 5. Component Stakeholder (updated)
components Management Guideline
Monitor and The process for 1. Program Scope 1. Expert Judgment 1. Approved Change
ensuring the Statement 2. PMIS Requests
Control program’s scope is 2. Approved Change 3. Review Meetings 2. Program Management
Program controlled to meet the Request 4. Decision Making Plan (updated)
agreed-upon goals 3. Component Transition 5. Audits 3. Program Scope
Scope
and realize the Request Statement Plan (updated)
agreed program 4. Governance Plan 4. Program Requirements
objectives and 5. Program Architecture (Updated)
benefits identified in Baseline 5. Program Document
the program charter. 6. Program Mgmt Plan Repository (updated)
Sridhar Peddisetty - PgM ITTOs Page 3 of 10 Last Updated 9/1/2010
4. Program Time Management
Knowledge Areas Major Processes Primary Inputs Tools & Techniques Primary Outputs
TIME
Develop Schedule 1. Program WBS 1. Schedule Management 1. Program Master
development is the 2. Program Constraints Tools Schedule
Program process of defining 3. Program Architecture 2. Benefit Analysis 2. Component
Schedule the program Baseline 3. Cash Flow Analysis Milestones
components needed 4. Program Charter 3. Program Schedule
to produce the 5. Contracts Management Plan
program deliverables, 6. Program Risk Register 4. Program Charter
to determine the (updated)
order in which the 5. Program Risk Register
components must be Updates
executed, to estimate
the amount of time
required to
accomplish each
component and to
identify the major
Program level
milestones during the
performance period.
Monitor and Schedule control is 1. Program Master Schedule 1. Schedule Management 1. Program Master
the process of 2. Component Status Tools Schedule (updated)
Control ensuring the 3. Program Risk Register 2. Program Metrics 2. Component Schedule
Program program produces 4. Approved Change 3. Earned Value (updated)
the required Requests Management 3. Program Performance
Schedule deliverables and Reports
solutions on time
Sridhar Peddisetty - PgM ITTOs Page 4 of 10 Last Updated 9/1/2010
5. Program Communications Management
Knowledge Areas Major Processes Primary Inputs Tools & Techniques Primary Outputs
COMMUNICATIONS
Plan Determining the 1. Program Charter 1. PMIS 1. Program
information and 2. Program Management 2. Communication Communications
Communications communications Plan Requirements Analysis Management Plan
needs of the 3. Governance Plan 3. Communication Method 2. Communications
Program 4. Program Stakeholder Strategy
stakeholders. Management Plan 3. Communications Log
5. Organizational
Communication Strategy
6. Program Scope
Statement
7. Program WBS
8. Communications
Requirements
9. Stakeholder Register
10. Program Master
Schedule
Distribute Making needed 1. Program 1. Communication Skill 1. Program Performance
information Communication Plan 2. Information Gathering Reports
Information available to 2. Communications and Retrieval System 2. Lessons Learned
program Messages 3. Information Distribution (updated)
stakeholders in a 3. Stakeholder Register Methods 3. Program
timely manner 4. Change Request Log 4. Lessons Learned Communications
5. Governance Decisions Database Management Plan
6. Component Charter (updated)
7. Program Master 4. Communications Log
Schedule (updated)
8. Program WBS
9. Communications Log
10.Communication
Strategy
Report Program The Collecting and 1. Program Performance 1. Information Presentation 1. Program Performance
distributing Reports Tool Reports
Performance performance 2. Program Budget 2. Status Gathering and 2. Program Forecasts
information. This Baseline Compilation 3. Communication
includes status 3. Program Management 3. Status Review Meetings Messages
reporting, progress Plan 4. Time Reporting System 4. Benefits Realization
measurement, and 4. Program Master 5. Cost Reporting System Report
forecasting. Schedule
5. Go/No Go Decision
6. Variance Reports
7. Performance
Measurements
8. Approved Change
Requests
9. Program Risk Register
10. Program Issues Register
11. Benefits Realization
Plan
12. Forecasts
Sridhar Peddisetty - PgM ITTOs Page 5 of 10 Last Updated 9/1/2010
6. Program Risk Management
Knowledge Areas Major Processes Primary Inputs Tools & Techniques Primary Outputs
RISK
Plan Program Deciding how to 1. Program Scope 1. Planning Meetings and 1. Program Risk
approach, plan, and Document Analysis Management Plan
Risk execute the risk 2. Program Management 2. Lessons Learned Review
Management management Plan
activities for a 3. Program Architecture
program, including Baseline
risks identified in the 4. Program Stakeholder
individual program Management Plan
components. 5. Program Governance
Structure
6. Resource Plan
7. Lessons Learned
Database
Identify Determining which 1. Program Scope 1. Documentation Review 1 Program Risk Register
risks might affect the Document 2. Information Gathering 2. Root Causes of Risk
Program Risks program and 2. Program Risk Techniques Updates
documenting their Management Plan 3. Checklist Analysis
characteristics. 3. Component Risk 4. Assumption Analysis
Management Plan 5. Diagramming
4. Program Management Techniques
Plan 6. SWOT Analysis
5.Program Governance 7. Lessons Learned Review
Structure 8. Scenario Analysis
6. Lessons Learned
Database
7. Program Stakeholder
Management Plan
Analyze Prioritizing risks for 1. Program Architecture 1. Risk Data Quality 1. Program Risk Register
further analysis or Baseline Assessment (updated).
Program Risks action by assessing 2. Program Management 2. Risk Probability and
and tabulating their Plan Impact assessment
probability of 3. Program Risk Register 3. Probability and Impact
occurrence and 4. Lessons Learned Matrix
impact, analyzing the Database 4. Risk Categorization
effect on the overall 5. Program Risk 5. Risk Urgency Assessment
program and its Management Plan 6. Impact Assessments of
components, and Interdependencies
managing 7. Data Gathering and
interdependencies. Representation Techniques
8. Quantitative Risk
Analyses and Modeling
Techniques
9. Independent Reviewers
Plan Program Developing options 1. Program Risk Register 1. Strategies for Negative 1. Program Risk Register
and actions to 2. Component Risk Risk Or Threats (updates)
Risk Responses enhance Response Plans 2. Strategies for Positive Risk 2. Contingency Reserves
opportunities, and to 3. Program Risk Or Opportunities 3. Contingency Plans
reduce threats to Management Plan 3. Contingency Plan 4. Change Requests
program objectives Preparation
4. Risk Response Action
Plan
Monitor and Tacking identified risks, 1. Program Architecture 1. Risk Review Meetings 1. Preventive Actions
monitoring Baseline 2. Risk Audits 2. Program Register
Control residual risks, 2. Program Risk 3. Lessons Learned Review (updates)
Program Risks identifying new risks, Management Plan 4. Monitor the Program 3. Program Risk
executing risk 3. Program Risk Register Environment Management Plan
response plans, and 4. Program Performance 5. Monitor Legal Issues and (updates)
evaluating Reports Climate 4. Lessons Learned
their effectiveness 5. Contingency Reserve Database (updated)
throughout program 6. Program Issue Register
life cycle. 7. Contract Review
Sridhar Peddisetty - PgM ITTOs Page 6 of 10 Last Updated 9/1/2010
7. Program Procurement Management
Knowledge Areas Major Processes Primary Inputs Tools & Techniques Primary Outputs
PROCUREMENT
Plan Program Plan Program 1. Market Environmental 1. Competitive Analysis of 1. Program Budget
Procurement is the Factors Service Providers Estimate (updated)
Procurement process of 2. Program Budget 2. Procurement Planning 2. Program Procurement
(a) determining Allocation 3. Expert Judgement Management Plan
what to procure and 3. Component Scope 4. Assessment of 3. Contract Management
when and Statements Organisational Plan
(b) developing 4. Program Charter Competencies 4. Qualified Seller List
procurement 5. Make or Buy Analysis
strategies. This process
precedes all other
procurement efforts.
Conduct This is the process of 1. Program Assets 1. Procurement Practices 1 Selected Sellers
how to conduct the 2. Subcontract Procurement 2. Bidder Conferences 2. Identified Internal
Program procurement plans 3. Distribution of Request Service Providers
Procurement activities for a 3. Program Procurement for Proposals 3. Request for Proposals
program. It includes Management Plan 4. Develop Qualified 4. Contract Management
strategy, tools, 4. Program Management Seller’s List Plan (updated)
methods, metrics Plan 5. Contract Negotiation 5. Program Procurement
gathering, reviews 5. Qualified Seller List 6. Proposal Evaluation Management Plan
and update 6. Contract Management System (updated)
mechanism, standard Plan 7. Expert Judgment 6, Contracts
assessment 7. Component Cost 8. Contract Management 7. Component Payment
parameters, and Schedules Procedures Schedules (Updated)
report requirements to 9. Change Control
be used by the Procedure
program in 10. Seller Selection
conducting the
procurement activities
for the program.
Administer Administer Program 1. Program Procurement 1. Change Control System 1. Program Budget
Procurement is the Management Plan 2. Engage and Manage Baseline (Updated)
Program process involved in 2. Program Budget Baseline Suppliers 2. Procurement
Procurement managing the 3. Contracts 3. Payment Control System Management Plan
contracts during the 4. Approved Change 4. Contract Performance (Updated)
program to ensure Requests Review 3. Contracts (updated)
that the deliverables 5. Program Performance 5. Inspect ion and Audits 4. Program Budget
meet requirements, Reports 6. Budget Management (Updated)
deadlines, cost, and 6. Payment Approval System 5. Program Performance
quality established in Requests Reports
the contract 7. Component Payment 6. Payment Approvals
Requests 7. Program Payment
Schedules (updated)
Close Program Cost Program 1. Program Management 1. Contract Closeout 1. Closeout Contracts
Procurement are Plan Procedure 2. Procurement
Procurement those processes that 2. Contracts 2. Supplier Performance Performance Reports
formally close out 3. Program Budget Review 3. Closed Budget
each contract on the 4. Program Performance 3. Budget Allocation Allocation
program after Reports Reconciliation
ensuring that all 5. Component Closure
deliverables have Notification
been satisfactorily
completed, that all
payments have been
made, and that there
are no outstanding
contractual issues.
Sridhar Peddisetty - PgM ITTOs Page 7 of 10 Last Updated 9/1/2010
8. Program Financial Management
Knowledge Areas Major Processes Primary Inputs Tools & Techniques Primary Outputs
FINANCIAL
Establish Identifying the overall 1. Program Funding Source 1. Program Financial 1. Program Financial
financial environment 2. Funding Goals Analysis Frame work
Program for the program and 3. Funding Constraints 2. Payment Schedules 2. Business Case
Financial pinpointing the funds 4. Program Business Case 3. Funding Methods (updated)
that are available
Framework according to
identified milestones
Develop Creating the 1. Program Financial 1. Program Financial 1. Program Financial Plan
processes for Framework Analysis 2. Program Payment
Program developing and 2. Funding Constraints 2. contract Management Schedules
Financial Plan managing the 3. Program WBS 3. Analysis of Program 3. Component Payment
Program budget and 4. Program Management Operational Costs Schedules
the payment Plan 4. Program Operational
schedules to the Cost
components. 5. Program Financial
Metrics
Estimate Developing the initial 1. Program Architecture 1. Total Cost of Ownership 1. Program Cost Estimates
program cost Baseline Analysis 2. Component Cost
Program Costs estimates that will be 2. Contingency Reserves 2. Architecture/Cost Estimates
presented to the 3. Program Management trade-off Analysis
decision-makers for Plan 3. Reserve Analysis
approval and further 4. Program Risk Register 4. Estimating Techniques
funding. 5. Contracts 5. Procurement Analysis
6. Computer Cost
Estimating Tools
7. Expert Judgment
Budget Developing the 1. Program Architecture 1. Cost Analysis 1. Program Budget
detailed budgets for Baseline 2. Reserve Analysis Baseline
Program Costs the program and for 2. Program Cost Estimates 2. Program Payment
the components 3. Program Management Schedules
based on the Plan 3. Component Payment
estimates provided by 4. Contracts Schedules
the components. 5. Component Cost
Estimates
Monitor and Influencing the factors 1. Program Financial Plan 1. Cost Change 1. Contract Payments
that create cost 2. Program Management Management System 2. Component Budgets
Control variances, controlling Plan 2. Contract Cost Closed
Program those variances at the 3. Program Budget Baseline Management 3. Program Budget Closed
program level, and 4. Contracts 3. Status Reviews 4. Program Budget
Financials
closing out the 5. Change Requests 4. Cost Forecasting Baseline (updated)
program and Techniques 5. Approve Change
component finances 5. Program Operational Request
Cost Analysis 6. Estimate at Completion
6. Earned Value 7. Program Management
Management (EVM) Plan (update)
8. Corrective Actions
Sridhar Peddisetty - PgM ITTOs Page 8 of 10 Last Updated 9/1/2010
9. Program Stakeholder Management
Knowledge Areas Major Processes Primary Inputs Tools & Techniques Primary Outputs
STAKEHOLDER
Plan Program Plan Stakeholder 1. Strategic Plan 1. PMIS 1. Program Stakeholder
Management covers 2. Program Charter 2. Stakeholder Analysis Management Plan
Stakeholder planning how 3. Program Sponsor 2. Component
Management stakeholders will be Identification Stakeholder Management
identified, analyzed, Guidelines
engaged, and
managed throughout
the life of the
program.
Identify Identify Program 1. Contracts 1. Expert Judgement 1. Stakeholder Register
Stakeholders 2. Request for Proposals 2. Organisational Analysis 2. Stakeholder Inventory
Program addresses the 3. Organizational Chart 3. Brainstorming 3. Program Stakeholder
Stakeholders systematic 4. Program Stakeholder 4. Stakeholder analysis Management Plan
identification and Management 5. Interviews Updates
analysis of program 6. Focus Groups 4. Stakeholder
stakeholders and 7. Questionnaires and Management Strategy
creates the Surveys
Stakeholder Register. 8. Program Impact Analysis
9. Stakeholder Checklist
Engage The process of 1. Program Charter 1. Stakeholder Analysis 1. Stakeholder Metrics
engaging Program 2. Program Stakeholder 2. Program Impact Analysis 2. Stakeholder
Program Stakeholders is where Management Plan 3. Stakeholder Impact and Management Strategy
Stakeholders the program 3. Stakeholder Inventory Issue Trading and (updated)
management team 4. Stakeholder Register Prioritization Tool
ensures that 5. Stakeholder
stakeholders are Management strategy
involved in the
program.
Manage Manage Program 1. Stakeholder 1. Negotiations 1. Stakeholder
Stakeholder Management Plan 2. Conflict Management Management Strategy
Stakeholder 2. Stakeholder Register 3. Communications (updated)
Expectations is the
Expectations process of managing 3. Stakeholder Inventory 4. Influencing 2. Program Stakeholder
communications to 4. Stakeholder Metrics Management Plan
satisfy the 5. Communications (updated)
requirements of, and Management Plan 3. Communications
resolve issues with, Management Plan
program stakeholders (updated)
Sridhar Peddisetty - PgM ITTOs Page 9 of 10 Last Updated 9/1/2010
10. Program Governance
Knowledge Areas Major Processes Primary Inputs Tools & Techniques Primary Outputs
GOVERNANCE
Plan and The process of 1. Strategic Directive 1. PMIS 1. Governance Plan
identifying governance 2. Program Management Plan 2. Organisational 2. Audit Plan
Establish goals and defining the 3. Benefits Realization Plan Planning 3. Issue Escalation Process
Program governance structure, 4. Organizational Charts 3. Program
roles and responsibilities. Management Office
Governance 4. Issue Management
Structure 5. Expert Management
6. Best Practice Library
Plan for The process for ensuring 1. Notification Audit 1. Audit Planning 1. Program Management
the program is prepared 2. Audit Plan 2. Written Deviations Plan (updated)
Audits for both external and 3. Program Management 3. Program Document 2. Audit Plan (updated)
internal audits of Processes Repository
program finances,
processes and
documents and
demonstrates
compliance with
approved
organizational program
management
processes.
Plan Program The process of 1. Benefit Realization Plan 1. Cost Benefit Analysis 1. Program Quality
identifying quality 2. Program Management Plan 2. Bench Marking Management Plan
Quality standards applicable to 3. Organizational Quality 3. Checklist
the program, the Standards 4. Cost of Quality
processes and 4. External Relations
standards to be applied,
and ensuring
compliance to these
standards.
Approve The process of defining 1. Program Management Plan 1. Reviews 1. Go/No-Go Decision
the decision-making 2. Component Charters 2. Expert Judgment 2. Change Request
Component structures 3. Component Initiation
Initiation and processes enabling Request
initiating and changing 4. Component Initiation
the program and/or Criteria
components within the
program
Provide The process for 1. Governance Plan 1. Reviews 1. No/No-Go Decision
providing governance 2. Gate Review Decision 2. Expert Judgment 2. Governance Decision
Governance and auditability Request Register
Oversight throughout the course 3. Program Performance 3. Governance Plan
of the program. Reports (updated)
4. Program Issues Register 4. Program Closure
5. Program Risk Register Recommendation
6. Program Management Plan
Manage The process for ensuring 1. Program Management Plan 1. Reviews 1. Benefit Realization Report
governance of 2. Program Charter 2. Benefit Realization 2. Governance Plan
Program expected program 3. Program Performance Analysis (updated)
Benefits benefits is delivered Reports 3. Change Requests
consistently throughout 4. Governance Plan
the program life cycle.
Monitor and The process for ensuring 1. Program Management Plan 1. Reviews 1. Approved Change
the appropriate level of 2. Change Request Log 2. Impact Analysis Requests
Control governance is applied 3. Change Requests 2. Change Request Log
Program to decision making of (updated)
proposed changes to
Changes the program plan.
Approve The process for ensuring 1. Component Transition 1. Reviews 1. Component Transition
transition of knowledge, Request Decision
Component responsibilities and 2. Benefits Realization Report 2. Benefits Realization
Transition benefit realization from Report (updated)
the program to ongoing 3. Lessons Learned
operations. 4. Program Management
Plan (updated)
Sridhar Peddisetty - PgM ITTOs Page 10 of 10 Last Updated 9/1/2010