The document provides information about a lunch and learn presentation by the EPMO's Program Management Team. The presentation will introduce the EPMO and its portfolio dashboards. The dashboards provide visibility into program health, status, workload and the client implementation pipeline. They allow custom views for different stakeholders and make the database searchable. The agenda includes an overview of the problem statement, dashboard features, a live demo and Q&A.
Business Case Strategies For Integrating Comissioning With Construction And P...mike benedetto
Presentation delivered at National CMAA Conference. Presentation outline considerations and business drivers supporting the integration of comissioning and qualification as part of project delivery strategy.
The Common Goals of Enterprise Project Management SoftwareOrangescrum
A decisive enterprise project management goes beyond the traditional project management level. It provides an expanded role that combines the strategic objectives with individual projects and responsibilities.
Alignment of business and IT is key to any growing organization. IT is an enabler and IT spend has to be fully aligned to enable business goals. An ePMO from Plexlane is a strategic step that companies can take to make sure a defined process exists with check and balances to make sure business goals and IT initiatives are always aligned.
Program Management Offices (PgMOs) serve to provide portfolio, program and project management governance, policy, procedure, process, guidance, standards, tools, techniques, templates, methodologies, evaluation, risk, performance measurement, and reporting expertise in the role of a Center of Excellence. In implementing a PgMO, clients seek to ensure not only successful delivery of programs, projects and operations -- but also to obtain the benefits from a coordinated framework and methodology for continual improvement of program/project management, vendor management, ongoing operations management and resource management. Ideally, the proper setup, management, measurement & services offered at the PgMO will increase the likelihood of benefits realization within their organization and partner agencies.
Program Management Outsourcing: Challenges & Factors Contributing to SuccessMoataz Y. Hussein
Over the past few years, outsourcing the program management function in large-scale programs has been popular amongst public and private sector organizations. It has been implemented in countries with promising national development plans in the sectors of Construction, Oil & Gas, Public Health, Education, and Telecommunication as well as in countries which are hosting special international events like the Olympics, World Cup, or a global exposition. The clients, public or private sectors, tend to go for well-known program management consultants (PMCs). Few reasons justify this strategy, among which are transferring the risks resulting from the administrative and technical complexity of the program to a third party and lack of skills and expertise. Nevertheless, these programs are challenged with meeting budget, schedule, and other program or business objectives.
This study aims at investigating and identifying the common challenges and factors contributing to success in PMC engagements. The study addresses these common challenges expressed as the missing enablers or factors in the program. The absence of these critical factors is considered a challenge that faces the Program Management Outsourcing model used today. In the same way and by the same argument it is shown that the existence of these factors or enablers will increase the likelihood of program success. The focus is on the key factors that pave the road for a productive client-PMC relationship, without going into the details of the program and related technical issues. In order to elicit these factors or enablers, a literature review has been done coupled with a questionnaire survey conducted amongst practitioners & academics. Finally a PMC-led program governance structure has been proposed.
As the large effort of a program, issues of conflict resolution, communication, benefit and change management are some of the main reasons program and project fails to delivery their outcomes.
The program governance integrates with the benefits management domain to help ensure that the program is continuously aligned with organizational strategy and that the intended value can still be achieved by the delivery of program benefits.
Balancing the elements of a program – strategic alignment, governance, stakeholder and benefit management - is the program manager's job.
In this presentation the attendees will have the satisfaction to see a real case framework to approach a program management so as to improve the delivery of intended benefits by setting-up a Project governance, stakeholder management, benefit and change management through a framework within which project decisions are made to improve program and project performances.
Business Case Strategies For Integrating Comissioning With Construction And P...mike benedetto
Presentation delivered at National CMAA Conference. Presentation outline considerations and business drivers supporting the integration of comissioning and qualification as part of project delivery strategy.
The Common Goals of Enterprise Project Management SoftwareOrangescrum
A decisive enterprise project management goes beyond the traditional project management level. It provides an expanded role that combines the strategic objectives with individual projects and responsibilities.
Alignment of business and IT is key to any growing organization. IT is an enabler and IT spend has to be fully aligned to enable business goals. An ePMO from Plexlane is a strategic step that companies can take to make sure a defined process exists with check and balances to make sure business goals and IT initiatives are always aligned.
Program Management Offices (PgMOs) serve to provide portfolio, program and project management governance, policy, procedure, process, guidance, standards, tools, techniques, templates, methodologies, evaluation, risk, performance measurement, and reporting expertise in the role of a Center of Excellence. In implementing a PgMO, clients seek to ensure not only successful delivery of programs, projects and operations -- but also to obtain the benefits from a coordinated framework and methodology for continual improvement of program/project management, vendor management, ongoing operations management and resource management. Ideally, the proper setup, management, measurement & services offered at the PgMO will increase the likelihood of benefits realization within their organization and partner agencies.
Program Management Outsourcing: Challenges & Factors Contributing to SuccessMoataz Y. Hussein
Over the past few years, outsourcing the program management function in large-scale programs has been popular amongst public and private sector organizations. It has been implemented in countries with promising national development plans in the sectors of Construction, Oil & Gas, Public Health, Education, and Telecommunication as well as in countries which are hosting special international events like the Olympics, World Cup, or a global exposition. The clients, public or private sectors, tend to go for well-known program management consultants (PMCs). Few reasons justify this strategy, among which are transferring the risks resulting from the administrative and technical complexity of the program to a third party and lack of skills and expertise. Nevertheless, these programs are challenged with meeting budget, schedule, and other program or business objectives.
This study aims at investigating and identifying the common challenges and factors contributing to success in PMC engagements. The study addresses these common challenges expressed as the missing enablers or factors in the program. The absence of these critical factors is considered a challenge that faces the Program Management Outsourcing model used today. In the same way and by the same argument it is shown that the existence of these factors or enablers will increase the likelihood of program success. The focus is on the key factors that pave the road for a productive client-PMC relationship, without going into the details of the program and related technical issues. In order to elicit these factors or enablers, a literature review has been done coupled with a questionnaire survey conducted amongst practitioners & academics. Finally a PMC-led program governance structure has been proposed.
As the large effort of a program, issues of conflict resolution, communication, benefit and change management are some of the main reasons program and project fails to delivery their outcomes.
The program governance integrates with the benefits management domain to help ensure that the program is continuously aligned with organizational strategy and that the intended value can still be achieved by the delivery of program benefits.
Balancing the elements of a program – strategic alignment, governance, stakeholder and benefit management - is the program manager's job.
In this presentation the attendees will have the satisfaction to see a real case framework to approach a program management so as to improve the delivery of intended benefits by setting-up a Project governance, stakeholder management, benefit and change management through a framework within which project decisions are made to improve program and project performances.
Agile for PPM Professionals Training Course - Wellingtone | FuturePMO 2021Wellingtone
Presenter: Karin Maule - Senior Training Consultant, Wellingtone
Presentation: During this highly engaging and interactive workshop, you will experience the newest Wellingtone learning innovation, our Agile for APM Accredited PPM Practitioners course. Utilising an extract from the latest Wellingtone course, you will begin to understand Agile in the context of non-Agile delivery, and how you can bring some good Agile practice into the day-to-day.
To attend the next FuturePMO conference, please visit www.FuturePMO.com
What are the differences between project and program management? How are they similar? What strategies are necessary for a successful transition from one to the other?
This presentation will address those questions and in addition provide practical guide lines and tips to those individuals aspiring be successful program managers as well as organizations that are in transition.
The IT PMO - A Handbook for Federal ProgramsVergys
The IT PMO is the nexus among strategy, IT initiatives, budget, and business objectives. And as the need for information technology grows, so does the importance of the IT PMO. This handbook outlines the processes and artifacts to initiate, execute, and mature a well-functioning PMO.
Training Slides of PROJECT MANAGEMENT OFFICE (PMO) SETTING UP AND MANAGEMENT, discussing the importance of Project Management.
Some Key-Points:
- The Project Management Context
- Project Life Cycle
- Work Breakdown Structure
For further information regarding the course, please contact:
info@asia-masters.com
www.asia-masters.com
A program description of an IT governance methodology for large and small programs where COBIT or ITIL may not be in your plans.
More at www.sqpegconsulting.com, Square Peg Consulting
John Goodpasture, PMP
This Slideshare presentation is a partial preview of the full business document. To view and download the full document, please go here:
http://flevy.com/browse/business-document/overview-of-program-management-1537
DOCUMENT DESCRIPTION
This presentation provides an overview to Program Management. It broadly follows the PMI's standard for Program Management. This document describes the context of the program, how to initiate and control projects as a part of program lifecycle, how to manage transitions, and how to obtain outcomes towards benefits realization. It also describes the key roles involved in program management and how Program Governance Board can facilitate program success.
Programs are taken up to realize benefits towards achieving organizational strategic objectives. Whereas projects produce discrete outputs, program management focuses on their synergization towards obtaining of outcomes and benefits.
Portfolio management is a key linking factor between program management and the organizational strategy. Programs, in turn consist of multiple inter-related projects collectively creating a coherent capability, which are then transitioned to the concerned functional departments to obtain desired outcomes.
Skeleton for EPMO roll out for large enterprises Ghayas Mansoor
Template provides basic framework addressing EPMO roll out in very large scale organizations that consist of multiple segments / business units with diversity in process definition and practices (v1.1)
A Project Management Office, abbreviated to PMO, is a group or department ... base project management principles on industry-standard methodologies. Daniel outlines best practices for a larger project team.
Agile for PPM Professionals Training Course - Wellingtone | FuturePMO 2021Wellingtone
Presenter: Karin Maule - Senior Training Consultant, Wellingtone
Presentation: During this highly engaging and interactive workshop, you will experience the newest Wellingtone learning innovation, our Agile for APM Accredited PPM Practitioners course. Utilising an extract from the latest Wellingtone course, you will begin to understand Agile in the context of non-Agile delivery, and how you can bring some good Agile practice into the day-to-day.
To attend the next FuturePMO conference, please visit www.FuturePMO.com
What are the differences between project and program management? How are they similar? What strategies are necessary for a successful transition from one to the other?
This presentation will address those questions and in addition provide practical guide lines and tips to those individuals aspiring be successful program managers as well as organizations that are in transition.
The IT PMO - A Handbook for Federal ProgramsVergys
The IT PMO is the nexus among strategy, IT initiatives, budget, and business objectives. And as the need for information technology grows, so does the importance of the IT PMO. This handbook outlines the processes and artifacts to initiate, execute, and mature a well-functioning PMO.
Training Slides of PROJECT MANAGEMENT OFFICE (PMO) SETTING UP AND MANAGEMENT, discussing the importance of Project Management.
Some Key-Points:
- The Project Management Context
- Project Life Cycle
- Work Breakdown Structure
For further information regarding the course, please contact:
info@asia-masters.com
www.asia-masters.com
A program description of an IT governance methodology for large and small programs where COBIT or ITIL may not be in your plans.
More at www.sqpegconsulting.com, Square Peg Consulting
John Goodpasture, PMP
This Slideshare presentation is a partial preview of the full business document. To view and download the full document, please go here:
http://flevy.com/browse/business-document/overview-of-program-management-1537
DOCUMENT DESCRIPTION
This presentation provides an overview to Program Management. It broadly follows the PMI's standard for Program Management. This document describes the context of the program, how to initiate and control projects as a part of program lifecycle, how to manage transitions, and how to obtain outcomes towards benefits realization. It also describes the key roles involved in program management and how Program Governance Board can facilitate program success.
Programs are taken up to realize benefits towards achieving organizational strategic objectives. Whereas projects produce discrete outputs, program management focuses on their synergization towards obtaining of outcomes and benefits.
Portfolio management is a key linking factor between program management and the organizational strategy. Programs, in turn consist of multiple inter-related projects collectively creating a coherent capability, which are then transitioned to the concerned functional departments to obtain desired outcomes.
Skeleton for EPMO roll out for large enterprises Ghayas Mansoor
Template provides basic framework addressing EPMO roll out in very large scale organizations that consist of multiple segments / business units with diversity in process definition and practices (v1.1)
A Project Management Office, abbreviated to PMO, is a group or department ... base project management principles on industry-standard methodologies. Daniel outlines best practices for a larger project team.
The role of Risk Assessment and Risk Management is to continuously Identify, Analyze, Plan, Track, Control, and Communicate the risks associated with a project.
The Webster’s definition of risk is the possibility of suffering a loss. Risk in itself is not bad. Risk is essential to progress and failure is often a key part of learning. Managing risk is a key part of success.
This document describes the foundations for conducting a risk assessment of a large-scale system development project. Such a project will likely include the procurement of Commercial Off The Shelf (COTS) products as well as their integration with legacy systems.
The processes are separated into colors according to knowledge areas and process groups. Based on The Standard for Program Management — Third Edition. Developed under permission from Project Management Institute.
Program Management Processes Flow in English - 3rd Edition - Simplified VersionRicardo Viana Vargas
In this simplified version of the The Standard for Program Management— Third Edition Processes Flow only the processes names are show, without their outputs.
Project Management is a well defined concept found in many guidebooks and Bodies of Knowledge. Putting these guides and BOK’s to work for the benefit of the enterprise is the role of Project Governance
THERE'S A NEW VERSION AVAILABLE: https://www.slideshare.net/ricardo.vargas/pmbok-guide-processes-flow-6th-edition
The 47 processes are separated into colors according to their respective knowledge areas. Only the main connections that are depicted in the PMBOK® Guide are shown in this process flow.
PMBOK® Guide 5th edition Processes Flow in English - Simplified VersionRicardo Viana Vargas
THERE'S A NEW VERSION AVAILABLE: https://www.slideshare.net/ricardo.vargas/pmbok-guide-processes-flow-6th-edition-simplified-version
In this simplified version of the PMBOK® Guide 5th edition Processes Flow only the 47 processes names are show, without their inputs, tools and techniques and outputs.
This was my dream assignment. I set up and built capabilities for a Project Management Office for a new technology division. I worked with my leadership, within the team, across with key stakeholders to design and implement a standardized Project Management approach for the team. The capstone of this experience, however, was working on the next phase of the PMO office. This presentation is what we shared with our division leadership to document our growth and map out ways to strengthen our capabilities.
Read more at leadanddeliver.com.
Simplifying processes for the customers of BC Clinical and Support Service (BCCSS) team was a focal point of their value proposition. Starting with a foundation of consistent, well-documented Standard Operating Procedures (SOP) and complimenting it with sound process governance the BCCSS team set out on a province-wide service mission to reduce risk, control cost and increase predictability. In the highly regulated healthcare industry, one that is experiencing significant business environment change, the need for efficiently managing and maintaining SOPs and process details is not only mission critical but also helps to drive process improvement and build employee engagement
The Institute of Cancer Research - Our PMO Journey - FuturePMO 2018Wellingtone
Presented by Michelle Durkin, Head of Programme Management Office, The Institute of Cancer Research
Presentation Synopsis: Michelle shares with you her journey so far in establishing a PMO, the challenges faced and where she found support along the way in designing and implementing the new function.
Michelle attended the first UK PMO Practitioner course ran by Wellingtone which provided her with tools to design an approach in how to deliver a new PMO. The approach was validated at Project Management Day Of Service and the PMO is now well on its way to meeting the requirements originally identified.
The CAF is an easy-to-use, free tool to assist public-sector organizations across Europe in using quality management techniques to improve their performance.
Establishing measurable performance expectations Feb 2019 Criterion Conferenc...Mark Hocknell
Setting measurable performance expectations; involves using a methodology and :
1 Ensuring the outcome/result is written so it can be measured
2 Measures are designed for the result
3 Targets are set sensible
Sustainability Techniques - Faculty Development Model - Competency-Based Educ...
Program Dashboards and Scorecards_CLEAN
1. 1
Jen Braly, Director, EPMO’s Program Management Team
Date: 15 Sep 15
Lunch and Learn
Getting to know the EPMO
Presenter:
2. 2
• Introduction to the EPMO
- Mission
- EPMO Maturity: Yesterday, Today and Tomorrow
• Introduction to the Lunch and Learn series
• Portfolio Dashboards Session
Lunch and Learn Agenda
3. 3
Agero EPMO Mission:
Through facilitation and collaboration, develop and implement governance
standards, processes and accountability measures that enable and assist the
enterprise to deliver quality products and services that align with Agero’s
strategic initiatives, on time, on budget, and with full transparency.
Key Responsibilities:
• Portfolio Governance: Responsible for governance standards, accountability
measures, conformance, auditing, analysis, reporting, training and
communication
• Program Management: Providing Program Management resources to support
Client Implementations, Product portfolios, and other key programs / projects
• Process Improvement: Identifying and addressing areas throughout Agero
that require improvement and to affect change through analysis, solutions
and implementation
Who Are We? - Mission
4. 4
YESTERDAY (JAN – AUG) TODAY (SEP - DEC) TOMORROW (2016 AND BEYOND)
• Enhanced Steering Committee
process to improve
prioritization, risk identification
and alignment to KI’s
• Establishing a Risk Tracker
and Risk Council to identify
problems early and
recommend corrective actions
• Enterprise risk tracking and
reporting
• Established Prioritization
Process and tracking
mechanism in Planview to align
resources to requirements and
cost tracking
• Tightly manage and understand
new work requests through
prioritization, steering and
change request processes
• Implementation of a series
of Benefits Tools for use in
decision making/prioritization
including Earned Value, NPV
and ROI calculations
• Established the Program
Management team and
processes to support our clients
and products
• Creation of a SharePoint
Knowledge Center as a single
repository of portfolio tools
and information
• Additional resources to
support new product
development and pilots
• Began weekly distribution of
Program Health Dashboards to
improve visibility of program
status’
• Continue to enhance the client
onboarding processes via
implementation tools,
complexity matrices, and client
work kits
• Provide corporate tools,
templates and processes for
use by all areas of the
organization
EPMO Maturity
5. 5
YESTERDAY (JAN – AUG) TODAY (SEP - DEC) TOMORROW (2016 AND BEYOND)
• Enhanced Steering Committee
process to improve
prioritization, risk identification
and alignment to KI’s
• Establishing a Risk Tracker
and Risk Council to identify
problems early and
recommend corrective actions
• Enterprise risk tracking and
reporting
• Established Prioritization
Process and tracking
mechanism in Planview to align
resources to requirements and
cost tracking
• Tightly manage and understand
new work requests through
prioritization, steering and
change request processes
• Implementation of a series
of Benefits Tools for use in
decision making/prioritization
including Earned Value, NPV
and ROI calculations
• Established the Program
Management team and
processes to support our clients
and products
• Creation of a SharePoint
Knowledge Center as a single
repository of portfolio tools
and information
• Additional resources to
support new product
development and pilots
• Began weekly distribution of
Program Health Dashboards to
improve visibility of program
status’
• Continue to enhance the client
onboarding processes via
implementation tools,
complexity matrices, and client
work kits
• Provide corporate tools,
templates and processes for
use by all areas of the
organization
EPMO Maturity
6. 6
YESTERDAY (JAN – AUG) TODAY (SEP - DEC) TOMORROW (2016 AND BEYOND)
• Enhanced Steering Committee
process to improve
prioritization, risk identification
and alignment to KI’s
• Establishing a Risk Tracker
and Risk Council to identify
problems early and
recommend corrective actions
• Enterprise risk tracking and
reporting
• Established Prioritization
Process and tracking
mechanism in Planview to align
resources to requirements and
cost tracking
• Tightly manage and understand
new work requests through
prioritization, steering and
change request processes
• Implementation of a series
of Benefits Tools for use in
decision making/
prioritization including
Earned Value, NPV and ROI
calculations
• Established the Program
Management team and
processes to support our clients
and products
• Creation of a SharePoint
Knowledge Center as a single
repository of portfolio tools
and information
• Additional resources to
support new product
development and pilots
• Began weekly distribution of
Program Health Dashboards to
improve visibility of program
status’
• Continue to enhance the client
onboarding processes via
implementation tools,
complexity matrices, and client
work kits
• Provide corporate tools,
templates and processes for
use by all areas of the
organization
EPMO Maturity
7. 7
YESTERDAY (JAN – AUG) TODAY (SEP - DEC) TOMORROW (2016 AND BEYOND)
• Enhanced Steering Committee
process to improve
prioritization, risk identification
and alignment to KI’s
• Establishing a Risk Tracker
and Risk Council to identify
problems early and
recommend corrective actions
• Enterprise risk tracking and
reporting
• Established Prioritization
Process and tracking
mechanism in Planview to align
resources to requirements and
cost tracking
• Tightly manage and understand
new work requests through
prioritization, steering and
change request processes
• Implementation of a series
of Benefits Tools for use in
decision making/
prioritization including
Earned Value, NPV and ROI
calculations
• Established the Program
Management team and
processes to support our clients
and products
• Creation of a SharePoint
Knowledge Center as a single
repository of portfolio tools
and information
• Additional resources to
support new product
development and pilots
• Began weekly distribution of
Program Health Dashboards to
improve visibility of program
status’
• Continue to enhance the client
onboarding processes via
implementation tools,
complexity matrices, and client
work kits
• Provide corporate tools,
templates and processes for
use by all areas of the
organization
EPMO Maturity
8. 8
x1. Today – Portfolio Dashboards
2. November - EPMO Governance
3. New Client Implementation Process
4. Risk Management Process and the New Risk Council
Introduction to the Lunch and Learn Series
Planned Lunch and Learn Series
If you would like additional sessions or other topics in upcoming sessions,
please reach out to Jen Braly
9. 9
EPMO Lunch and Learn: Session 1
Program Management Team’s Health Dashboards
10. 10
1. Problem Statement and Goals
2. Portfolio Dashboards
• Introduction [Instructions, Key]
• Summary Charts [Executive Summary, Client Forecast]
• Database Views
3. Live Demo
4. Questions
Overview
Backup slides: Links and Preview of Program Scorecards
11. 11
1. Limited visibility into health
and progress
2. Limited visibility into pipeline for
Client Implementation
3. Outdated or inconsistent display
of project information
4. Difficult to customize health
reports to each stakeholder’s
needs
5. Difficult to find information about
your project quickly
Problem Statement and Goals
PROBLEM STATEMENT GOALS
1. Provide visibility into health and
progress by centralizing information
in one location, online
2. Provide visibility into pipeline to
increase awareness of scheduled
go-lives [Forecast]
3. Establish reporting cadence
[weekly] to ensure current
information is available
4. Create custom views for major
stakeholders types
5. Make database searchable like
“google” so you can find info quickly
Programs managed by EPMO [Client Implementations, Product Programs, Key Initiatives]:
12. 12
1. Limited visibility into health
and progress
2. Limited visibility into pipeline for
Client Implementation
3. Outdated or inconsistent display
of project information
4. Difficult to customize health
reports to each stakeholder’s
needs
5. Difficult to find information about
your project quickly
Problem Statement and Goals
PROBLEM STATEMENT GOALS
1. Provide visibility into health and
progress by centralizing information
in one location, online
2. Provide visibility into pipeline to
increase awareness of scheduled
go-lives [Forecast]
3. Establish reporting cadence
[weekly] to ensure current
information is available
4. Create custom views for major
stakeholders types
5. Make database searchable like
“google” so you can find info quickly
Programs managed by EPMO [Client Implementations, Product Programs, Key Initiatives]:
13. 13
1. Limited visibility into health
and progress
2. Limited visibility into pipeline for
Client Implementation
3. Outdated or inconsistent display
of project information
4. Difficult to customize health
reports to each stakeholder’s
needs
5. Difficult to find information about
your project quickly
Mission
Problem Statement and Goals
PROBLEM STATEMENT GOALS
1. Provide visibility into health and
progress by centralizing information
in one location, online
2. Provide visibility into pipeline to
increase awareness of scheduled
go-lives [Forecast]
3. Establish reporting cadence
[weekly] to ensure current
information is available
4. Create custom views for major
stakeholders types
5. Make database searchable like
“google” so you can find info quickly
Programs managed by EPMO [Client Implementations, Product Programs, Key Initiatives]:
14. 14
Portfolio Dashboard
Introduction
Tab Name Tab Focus Target Audience Purpose
Executive
Summary
Health, Status, and
Workload
Executive
Leadership
To provide a Crayon view of the overall portfolio of programs' Health and
Status, and to see a snapshot of client launches, and project's health that are
"at risk" or "critical".
Forecast Planned Go-Lives
Executive
Leadership,
Sales / Client
Services
To provide a high-level forecast of the client launches for <3 months, then 3-6
months from current month.
Health View Health
Senior
Leadership
To provide a High-Level view of the overall portfolio of programs' Health,
filtered by health, to be able to quickly determine those which specific
constraints that are at risk [Scope, Benefits, Resources, Budget, Schedule].
PgM View Workload by PgM
Functional
Leadership
To provide a Team view of your specific program's Health, filtered by the
Program Manager and by phase, to determine if the program is on track or if
it has concerns.
Client View
New Client
Implementations
Client Services
and IT
To provide a Client view of your specific program's Health, filtered by the
program phase, then program type, to determine if the program is on track or
if it has concerns.
Product View
Product Programs
managed by EPMO
Product Team,
Marketing, and
IT
To provide a Product view of your specific program's Health, filtered by the
program phase, then program name, to determine if the program is on track
or if it has concerns.
Full Database
All Active
Programs
EPMO
To provide a the most detailed Team view of the entire portfolio of program,
without any filters, see the same as above, adding Program Manager priority
and expected effort required to see how the work is being sequenced. Data
can be searched, sorted, and filtered to meet specific needs
Completed
View
All Completed
Programs
Executive
Leadership,
EPMO
To provide list of Closed programs, without any filters, to highlight completed
work.
15. 15
Portfolio Dashboard
Key
Category Question Answered via Key Key for Category Description of Key
Type
What type of Program is
this?
Planned
Finish
When is this Program
expected to Launch or be
complete?
Overall
Health
How is this Program Doing,
Overall?
Constraints
Health
What part of my program is
at risk?
[Overall Health is affected if two
or more constraints' health's are
un healthy]
Status
Is this Program Being
Worked on now?
Phase
If not Launched, How far
along is this Program?
Healthy
Early Warning
At Risk
Critical
Under control, no significant concerns
Under control, recoverable impact
Problems approaching unrecoverable threshold
Out of control, unrecoverable impact
Scope
Benefits
Resources
Budget
Schedule
Indicates the volatility of locking requirements down
Indicates likelihood of getting expected value at then end
Indicates if the team has the people they need to succeed
Indicates if the team is managing their budget to plan
Indicates the likelihood of adhering to planned finish
On Hold
Pipeline – In Queue
Active
Closed
Cancelled
Not planned to be worked on – not resourced
Planned to be worked on – not resourced
Actively being worked on – resourced
Completed – no longer resourced
Cancelled – Removed from portfolio; no plan to work on again
Client [Auto, Insurance, Other]
Product
Process Improvement
New Implementations, Existing Client Proj, Large Changes
New or Existing Product Programs
Internal to EPMO, or non -Client or Product
[DATE]
[DATE]
[DATE]
[DATE]
Finish within 31 - 60 days of Planned Finish Date
Finish > 61 days of Planned Finish Date or TBD
Finish within 1-30 days of Planned Finish Date
Finish Missed - Overdue
[G3] Change
[G0] Pre-Proposal
[G1] Initiation
[G2] Planning
Execution
Launched
Change to Original Scope; may be a small project or Large CR
Phase 0 - Pre-Gate 0
Phase 1 - Post Gate 0, Pre-Gate 1
Phase 2 - Post Gate 1, Pre-Gate 2
Phase 3 - Post Gate 2, Pre-Gate 3 [change] or 4 [closure]
Go-Live complete; if active, closeout activity underway
16. 16
Program Management Health Reporting
Health Standards
** Overall Health is affected if two or more constraints' health's are unhealthy, or if any constraint significantly
impacts the program’s ability to succeed.
17. 17
Rating Overall Health Benefits Scope Resources Budget Schedule
Healthy
Under Control,
No Significant
Concerns
>95% KPI
Adherence,
On track to Full
Realization
>95% of Scope
adherence,
No Changes
Needs
Identified,
Approved, and
Available
On Track,
Spend 0-1%
Variance from
approved Plan
On track:
Critical Path on
track, <5%
Variance from
Plan
Early
Warning
Minor Concerns,
Recoverable
Impact
80-94% KPI
adherence,
Minor
Concerns for
Full Realization
Minor
Changes,
Sponsor
approval
required
Needs
Identified,
Approved, only
key resources
Available
Minor
Concerns,
Spend 2-5%
Variance from
approved Plan
Critical Path:
Minor
Concerns, 6-9%
Variance from
Plan
At Risk
Major Concerns,
Approaching
Unrecoverable
Threshold
60-79% KPI
adherence,
Full Realization
very unlikely
Major
Changes,
Gate 3
recommended
Needs
Identified,
Approved, key
resource(s) not
Available
Major
Concerns,
Spend 6-10%
Variance from
approved Plan
Critical Path:
Major
Concerns, 10-
19% Variance
from Plan
Critical
Out of control,
Unrecoverable
Impact
<60% KPI
adherence,
Full Realization
impossible
Out of Control,
Gate 3
Required
Needs not yet
Identified,
Approved, or
Available
Out of Control,
Spend > 10%
Variance from
approved Plan
Critical Path:
Unrecoverable,
>20% Variance
from Plan
Program Management Health Reporting
Health Standards
** Overall Health is affected if two or more constraints' health's are unhealthy, or if any constraint significantly
impacts the program’s ability to succeed.
18. 18
Category Question Answered via Key Key for Category Description of Key
Type What type of Program is this?
Planned
Finish
When is this Program expected to
Launch or be complete?
Overall
Health
How is this Program Doing, Overall?
Constraints
Health
What part of my program is at risk?
[Overall Health is affected if two or
more constraints' health's are un
healthy]
Status Is this Program Being Worked on now?
Phase
If not Launched, How far along is this
Program?
Healthy
Early Warning
At Risk
Critical
Under control, no significant concerns
Under control, recoverable impact
Problems approaching critical threshold
Out of control, unrecoverable impact
Scope
Benefits
Resources
Budget
Schedule
Indicates the volatility of locking requirements down
Indicates likelihood of getting expected value at then end
Indicates if the team has the people they need to succeed
Indicates if the team is managing their budget to plan
Indicates the likelihood of adhering to planned finish
Change [G3]
Pre-Proposal [G0]
Initiation [G1]
Planning [G2]
Execution
Lanched
Change to Original Scope; may be a smallproject or Large CR
Phase 0 - Pre-Gate 0
Phase 1 - Post Gate 0, Pre-Gate 1
Phase 2 - Post Gate 1, Pre-Gate 2
Phase 3 - Post Gate 2, Pre-Gate 3 [change] or 4 [closure]
Go-Live Date has occurred; if still active, final closeout activity has begun
Client
Product
Proc. Improvm’t
New Client Implementations, Existing Client Proj's, Large Change Requests
New or Existing Product Programs
Internal to EPMO, or non -Client or Product
[DATE]
[DATE]
[DATE]
[DATE]
Finish within 31 - 60 days of Planned Finish Date
Finish > 61 days of Planned Finish Date or TBD
Finish within 1-30 days of Planned Finish Date
Finish Missed - Overdue
On Hold
Pipeline – In Queue
Active
Closed
Cancelled
Not planned to be worked on – not resourced
Planned to be worked on – not resourced
Actively being worked on – resourced
Completed – no longer resourced
Cancelled – Removed from portfolio of work; no plan to work on again
Portfolio Dashboard
Key
19. 19
Category Question Answered via Key Key for Category Description of Key
Type What type of Program is this?
Planned
Finish
When is this Program expected to
Launch or be complete?
Overall
Health
How is this Program Doing, Overall?
Constraints
Health
What part of my program is at risk?
[Overall Health is affected if two or
more constraints' health's are un
healthy]
Status Is this Program Being Worked on now?
Phase
If not Launched, How far along is this
Program?
Healthy
Early Warning
At Risk
Critical
Under control, no significant concerns
Under control, recoverable impact
Problems approaching critical threshold
Out of control, unrecoverable impact
Scope
Benefits
Resources
Budget
Schedule
Indicates the volatility of locking requirements down
Indicates likelihood of getting expected value at then end
Indicates if the team has the people they need to succeed
Indicates if the team is managing their budget to plan
Indicates the likelihood of adhering to planned finish
Change [G3]
Pre-Proposal [G0]
Initiation [G1]
Planning [G2]
Execution
Lanched
Change to Original Scope; may be a smallproject or Large CR
Phase 0 - Pre-Gate 0
Phase 1 - Post Gate 0, Pre-Gate 1
Phase 2 - Post Gate 1, Pre-Gate 2
Phase 3 - Post Gate 2, Pre-Gate 3 [change] or 4 [closure]
Go-Live Date has occurred; if still active, final closeout activity has begun
Client
Product
Proc. Improvm’t
New Client Implementations, Existing Client Proj's, Large Change Requests
New or Existing Product Programs
Internal to EPMO, or non -Client or Product
[DATE]
[DATE]
[DATE]
[DATE]
Finish within 31 - 60 days of Planned Finish Date
Finish > 61 days of Planned Finish Date or TBD
Finish within 1-30 days of Planned Finish Date
Finish Missed - Overdue
On Hold
Pipeline – In Queue
Active
Closed
Cancelled
Not planned to be worked on – not resourced
Planned to be worked on – not resourced
Actively being worked on – resourced
Completed – no longer resourced
Cancelled – Removed from portfolio of work; no plan to work on again
Portfolio Dashboard
Key
20. 20
Category Question Answered via Key Key for Category Description of Key
Type What type of Program is this?
Planned
Finish
When is this Program expected to
Launch or be complete?
Overall
Health
How is this Program Doing, Overall?
Constraints
Health
What part of my program is at risk?
[Overall Health is affected if two or
more constraints' health's are un
healthy]
Status Is this Program Being Worked on now?
Phase
If not Launched, How far along is this
Program?
Healthy
Early Warning
At Risk
Critical
Under control, no significant concerns
Under control, recoverable impact
Problems approaching critical threshold
Out of control, unrecoverable impact
Scope
Benefits
Resources
Budget
Schedule
Indicates the volatility of locking requirements down
Indicates likelihood of getting expected value at then end
Indicates if the team has the people they need to succeed
Indicates if the team is managing their budget to plan
Indicates the likelihood of adhering to planned finish
Change [G3]
Pre-Proposal [G0]
Initiation [G1]
Planning [G2]
Execution
Lanched
Change to Original Scope; may be a smallproject or Large CR
Phase 0 - Pre-Gate 0
Phase 1 - Post Gate 0, Pre-Gate 1
Phase 2 - Post Gate 1, Pre-Gate 2
Phase 3 - Post Gate 2, Pre-Gate 3 [change] or 4 [closure]
Go-Live Date has occurred; if still active, final closeout activity has begun
Client
Product
Proc. Improvm’t
New Client Implementations, Existing Client Proj's, Large Change Requests
New or Existing Product Programs
Internal to EPMO, or non -Client or Product
[DATE]
[DATE]
[DATE]
[DATE]
Finish within 31 - 60 days of Planned Finish Date
Finish > 61 days of Planned Finish Date or TBD
Finish within 1-30 days of Planned Finish Date
Finish Missed - Overdue
On Hold
Pipeline – In Queue
Active
Closed
Cancelled
Not planned to be worked on – not resourced
Planned to be worked on – not resourced
Actively being worked on – resourced
Completed – no longer resourced
Cancelled – Removed from portfolio of work; no plan to work on again
Portfolio Dashboard
Key
21. 21
Category Question Answered via Key Key for Category Description of Key
Type What type of Program is this?
Planned
Finish
When is this Program expected to
Launch or be complete?
Overall
Health
How is this Program Doing, Overall?
Constraints
Health
What part of my program is at risk?
[Overall Health is affected if two or
more constraints' health's are un
healthy]
Status Is this Program Being Worked on now?
Phase
If not Launched, How far along is this
Program?
Healthy
Early Warning
At Risk
Critical
Under control, no significant concerns
Under control, recoverable impact
Problems approaching critical threshold
Out of control, unrecoverable impact
Scope
Benefits
Resources
Budget
Schedule
Indicates the volatility of locking requirements down
Indicates likelihood of getting expected value at then end
Indicates if the team has the people they need to succeed
Indicates if the team is managing their budget to plan
Indicates the likelihood of adhering to planned finish
Change [G3]
Pre-Proposal [G0]
Initiation [G1]
Planning [G2]
Execution
Lanched
Change to Original Scope; may be a smallproject or Large CR
Phase 0 - Pre-Gate 0
Phase 1 - Post Gate 0, Pre-Gate 1
Phase 2 - Post Gate 1, Pre-Gate 2
Phase 3 - Post Gate 2, Pre-Gate 3 [change] or 4 [closure]
Go-Live Date has occurred; if still active, final closeout activity has begun
Client
Product
Proc. Improvm’t
New Client Implementations, Existing Client Proj's, Large Change Requests
New or Existing Product Programs
Internal to EPMO, or non -Client or Product
[DATE]
[DATE]
[DATE]
[DATE]
Finish within 31 - 60 days of Planned Finish Date
Finish > 61 days of Planned Finish Date or TBD
Finish within 1-30 days of Planned Finish Date
Finish Missed - Overdue
On Hold
Pipeline – In Queue
Active
Closed
Cancelled
Not planned to be worked on – not resourced
Planned to be worked on – not resourced
Actively being worked on – resourced
Completed – no longer resourced
Cancelled – Removed from portfolio of work; no plan to work on again
Portfolio Dashboard
Key
22. 22
Category Question Answered via Key Key for Category Description of Key
Type What type of Program is this?
Planned
Finish
When is this Program expected to
Launch or be complete?
Overall
Health
How is this Program Doing, Overall?
Constraints
Health
What part of my program is at risk?
[Overall Health is affected if two or
more constraints' health's are un
healthy]
Status Is this Program Being Worked on now?
Phase
If not Launched, How far along is this
Program?
Healthy
Early Warning
At Risk
Critical
Under control, no significant concerns
Under control, recoverable impact
Problems approaching critical threshold
Out of control, unrecoverable impact
Scope
Benefits
Resources
Budget
Schedule
Indicates the volatility of locking requirements down
Indicates likelihood of getting expected value at then end
Indicates if the team has the people they need to succeed
Indicates if the team is managing their budget to plan
Indicates the likelihood of adhering to planned finish
Change [G3]
Pre-Proposal [G0]
Initiation [G1]
Planning [G2]
Execution
Lanched
Change to Original Scope; may be a smallproject or Large CR
Phase 0 - Pre-Gate 0
Phase 1 - Post Gate 0, Pre-Gate 1
Phase 2 - Post Gate 1, Pre-Gate 2
Phase 3 - Post Gate 2, Pre-Gate 3 [change] or 4 [closure]
Go-Live Date has occurred; if still active, final closeout activity has begun
Client
Product
Proc. Improvm’t
New Client Implementations, Existing Client Proj's, Large Change Requests
New or Existing Product Programs
Internal to EPMO, or non -Client or Product
[DATE]
[DATE]
[DATE]
[DATE]
Finish within 31 - 60 days of Planned Finish Date
Finish > 61 days of Planned Finish Date or TBD
Finish within 1-30 days of Planned Finish Date
Finish Missed - Overdue
On Hold
Pipeline – In Queue
Active
Closed
Cancelled
Not planned to be worked on – not resourced
Planned to be worked on – not resourced
Actively being worked on – resourced
Completed – no longer resourced
Cancelled – Removed from portfolio of work; no plan to work on again
Portfolio Dashboard
Key
23. 23
Category Question Answered via Key Key for Category Description of Key
Type What type of Program is this?
Planned
Finish
When is this Program expected to
Launch or be complete?
Overall
Health
How is this Program Doing, Overall?
Constraints
Health
What part of my program is at risk?
[Overall Health is affected if two or
more constraints' health's are un
healthy]
Status Is this Program Being Worked on now?
Phase
If not Launched, How far along is this
Program?
Healthy
Early Warning
At Risk
Critical
Under control, no significant concerns
Under control, recoverable impact
Problems approaching critical threshold
Out of control, unrecoverable impact
Scope
Benefits
Resources
Budget
Schedule
Indicates the volatility of locking requirements down
Indicates likelihood of getting expected value at then end
Indicates if the team has the people they need to succeed
Indicates if the team is managing their budget to plan
Indicates the likelihood of adhering to planned finish
Change [G3]
Pre-Proposal [G0]
Initiation [G1]
Planning [G2]
Execution
Lanched
Change to Original Scope; may be a smallproject or Large CR
Phase 0 - Pre-Gate 0
Phase 1 - Post Gate 0, Pre-Gate 1
Phase 2 - Post Gate 1, Pre-Gate 2
Phase 3 - Post Gate 2, Pre-Gate 3 [change] or 4 [closure]
Go-Live Date has occurred; if still active, final closeout activity has begun
Client
Product
Proc. Improvm’t
New Client Implementations, Existing Client Proj's, Large Change Requests
New or Existing Product Programs
Internal to EPMO, or non -Client or Product
[DATE]
[DATE]
[DATE]
[DATE]
Finish within 31 - 60 days of Planned Finish Date
Finish > 61 days of Planned Finish Date or TBD
Finish within 1-30 days of Planned Finish Date
Finish Missed - Overdue
On Hold
Pipeline – In Queue
Active
Closed
Cancelled
Not planned to be worked on – not resourced
Planned to be worked on – not resourced
Actively being worked on – resourced
Completed – no longer resourced
Cancelled – Removed from portfolio of work; no plan to work on again
Portfolio Dashboard
Key
24. 24
Executive Summary
Tab Name Tab Focus Target Audience Purpose
Executive
Summary
Health, Status,
and Workload
Executive
Leadership
To provide a Crayon view of the overall portfolio of
programs' Health and Status, and to see a snapshot of client
launches, and project's health that are "at risk" or "critical".
32. 32
Program Forecast
Tab Name Tab Focus Target Audience Purpose
Forecast Planned Go-Lives
Executive Leadership,
Sales / Client Services
To provide a high-level forecast of the client
launches for <3 months, then 3-6 months
from current month.
33. 33
Tab Name Tab Focus Target Audience Purpose
Health View Health
Senior
Leadership
To provide a High-Level view of the overall portfolio of programs'
Health, filtered by from most critical to healthy, to be able to
quickly determine those which are in trouble.
Health View
Header will appear when you scroll down, like “freeze” line in excel
34. 34
Tab Name Tab Focus Target Audience Purpose
PgM View
Workload by
PgM
Individuals working
directly on specific
program
To provide a view of your specific program's Health, filtered
by the Program Manager, then by program Phase, to
determine if the program is on track or if it has concerns.
Program Manager View
35. 35
Tab Name Tab Focus Target Audience Purpose
Client View
New Client
Implementations
Client Services and
IT
To provide a Client view of your specific program's Health,
filtered by the program phase, then program type, to
determine if the program is on track or if it has concerns.
Client View
36. 36
Tab Name Tab Focus Target Audience Purpose
Product View
Product Programs
managed by EPMO
Product Team,
Marketing, and IT
To provide a Product view of your specific program's Health,
filtered by the program phase, then program name, to
determine if the program is on track or if it has concerns.
Product View
37. 37
Tab Name Tab Focus Target Audience Purpose
Full
Database
All Active
Programs
Individuals
working directly
on specific
program
To provide a the most detailed Team view of the entire portfolio of
program, without any filters, see the same as above, adding Program
Manager priority and expected effort required to see how the work is
being sequenced. Data can be searched, sorted, and filtered to meet
specific needs
Full Database View
38. 38
Tab Name Tab Focus Target Audience Purpose
Completed Program Senior Leadership, EPMO
To provide a more detailed Team view of Closed
programs, without any filters, to highlight
completed work.
Completed View
42. 42
[Mitigation]
• [List Accomplishments]
• X
• X
• X
RISKS AND ISSUES
LOOK BACK LOOK AHEAD
[Justification]
HEALTHHealthy
1. [Mitigation]1. [Risk]
2. [Mitigation]2. [Risk]
3. [Mitigation]3. [Risk]
• [List Next Steps]
• X
• X
• X
Scorecard
Project: [Name] Sponsor: [Name]
P
I
P
I
P
I
Initiate Planning Execution Transition Closeout
Date Date Date Date Date
43. 43
EPMO PROGRAM SCORECARD Priority
Program Category
Discussion
RISKS & ISSUES
8/12/201516:42
[Program Name]
LowPriority
Product - New
Owner
[Name]
[Name]
[Name]
[Name]
[Name]
[Name]
X
X
X
X
X
X
Early Warning
Current Rating
SCHEDULE & MILESTONES
Topic
X
X
X
X
X
X
Critical
N/A
Remove [X] by [date]
Increase [X] by [X% or #]
Reduce [X] by [X% or #]
Remove [X] by [X% or #]
Remove [X] by [X% or #]
Benefits Mitigation
Mitigation
Mitigation
Mitigation
Mitigation
Mitigation
HEALTH & BENEFITS
[x% or#]
[x% or#]
[x% or#]
[x% or#]
[x% or#]
[X % or #]
[X % or #]
[X % or #]
[X % or #]
[X % or #]
[date]
[date]
[date]
[date]
[date]
Prob Imp Score Risk Mitigation
[Name] 5 5
25%ProjectRisk Quality
Business Risk Safety
Area of Concern Health Mitigation
[comments about how to improve the health,includingscope changes,crashingschedule,addingfunding,mitigating
risks,andreassessingplannedbenefits]
Top Risk / Issue - #2 Owner Prob Imp Score Risk Mitigation
Score Risk MitigationProb Imp
85
Schedule
Legal / Compliance
ProjectRisk
Business Risk
Top Risk / Issue - #1
[Name]
Owner
40%
[Name] 1 8
8%ProjectRisk Resources
Business Risk Environ. Condition
Top Risk / Issue - #3 Owner
Current Rating DueCurrentTargetBenefits and KPIs
Healthy
Early Warning
At Risk
4
5
6
7
Project 1 or Phase
Project 1 or Phase
Project 1 or Phase
Project 1 or Phase
Project 1 or Phase
Project 1 or Phase
2
PM [Name] Sponsor [Name]
[Date]Early Warning
0
100
[deliverables for Milestone}
[deliverables for Milestone}
Major Milestone or Required Task Major Deliverables
[deliverables for Milestone}
[deliverables for Milestone}
[deliverables for Milestone}
[deliverables for Milestone}
[deliverables for Milestone}
[deliverables for Milestone}
[Key Milestone]
[Key Milestone]
[Key Milestone]
[Key Milestone]
[Key Milestone]
[Key Milestone]
[Key Milestone]
[Key Milestone]
10
11
Project 1 or Phase
Project 1 or Phase
[Date] [Date]At Risk
[Date] [Date]Early Warning
0
25
[deliverables for Milestone}
[deliverables for Milestone}
[Key Milestone]
[Key Milestone]
8
9
Project 1 or Phase
Project 1 or Phase
[Date] [Date]At Risk
[Date]
[Key Milestone]
[Date] [Date]At Risk
[Date] [Date]At Risk
25
90
[Date] [Date]Critical
[Date] [Date]N/A
60
0[deliverables for Milestone}
Open Items
4
[Date]Early Warning 10
%
Complete
Progress
Key Milestones and Deliverables
Progress
%
Complete
Finish
Planned Proj / Act
At Risk 34% [date] [date]
[General updates about Schedule]
Project 1 or Phase1
Comments
[comments about benefits healthoverall]
X [date]
4
1
5
6
PROGRESS UPDATES
5 X [date]
2
3
6 X [date]
2
Completed
1 X [date]
2 X [date]
X [date]
Look Ahead - Key Planned Activities Planned
3
Healthy
0
30
Project or Phase
Finish
Planned Proj / Act
[Date]
X [date]
Schedule Summary
4 X [date]
5 X [date]
3
X [date]
3
1 X [date]
Look Back - Key Accomplishments
[Date] [Date]Critical 65[deliverables for Milestone}[Key Milestone]12 Project 1 or Phase
6 X [date]
[Date] [Date]Early Warning
[Date] [Date]
Overall Health
Early Warning
Early Warning
Early Warning
Early Warning
Early Warning
Scope
Benefit
Resources
Budget
Schedule
[Indicate why youturnedthe overall healththe current rating]
Program Scorecards
Risk
Health
Progress
Roll-up: Scorecard health and mitigation would
be used as input to portfolio health dashboards
Highest Risks or issue for the week
Shows Progress and Open items in one place
Schedule Shows Milestone updates in one place
Objective: Consolidate weekly status updates to
stakeholders into repeatable and standardized format
44. 44
Overall Health and Risks
Project: [Name] Sponsor: [Name]
[Select] [Select] [Name]
Project Risk
Business Risk
[Select] [Select] [Name]
Project Risk
Business Risk
[Select] [Select] [Name]
Project Risk
Business Risk
1 Situation [If this Occurs...]
2 Situation [If this Occurs...]
3 Situation [If this Occurs...]
Resources
Scope
KPI or Benefit
[how to improve schedule health including crashing schedule by adding resources, or removing scope]
[how to improve the budget health, including reassessing planned budget, adding funding]
[how to improve the resources health]
[how to improve the Scope health including reducing scope, clarifying scope]
[how to improve the benefit or KPI health, including reassessing planned benefits/KPIs]
Risk Mitigation [...Plan to reduce impact]Impact [...This will happen] = Risk/Issue
Impact [...This will happen] = Risk/Issue Risk Mitigation [...Plan to reduce impact]
Impact [...This will happen] = Risk/Issue Risk Mitigation [...Plan to reduce impact]
#VALUE![Select Category]
[Select Category]
OwnerProb Imp Score
#VALUE![Select Category]
[Select Category]
OwnerProb Imp Score
#VALUE![Select Category]
[Select Category]
TOP RISKS & ISSUES
OwnerProb Imp Score
[Select Health]
OVERALL HEALTH
Health Justification
Current Rating Area of Concern
[Impacting Overall Health]
Health Mitigation
[Select Health]
[Indicate why you turned the overall health the current rating] [Select Health]
[Select Health]
[Select Health]
[Select Health]
Schedule
Budget
KPI, Graphs, etc
45. 45
1 1
2 2
3 3
4 4
5 5
Comments or Details
[date]
[date]
[date]
[date]
Accomplishments [Look Back]
X
X
X
X
X
Next Steps [Look Ahead]Completed
[date]
[date]
[date]
[date]
[date]
Planned
8
9
10
6
7
4
5
2
3
Actual
1
SCHEDULE
Progress
%
Complete
Finish Dates
Major Deliverables or Outcome Dependencies or CommentsPlannedMajor Phase, Milestone, or Task
[date]
4 X X [Name]
5 X X [Name]
2 X X [Name]
3 X X [Name]
Open Items [Parking Lot]
Topic or Decision Needed Owner
1 X X [Name]
PROGRESS UPDATES
Schedule and Progress
Project: [Name] Sponsor: [Name]
Initiate Planning Execution Transition Closeout
Date Date Date Date Date
Roadmap