WS1 – PMO & Strategy�Project Charter & Governance
Workstream
Administration / Organisation | Subject Matter Expertise | Leadership | Problem Solving & Analytics |
| | | |
| | | |
| | | |
| | | |
Core objectives
Key Roles
high
med
med
med
low
high
low
high
high
high
med
med
high
low
technical
technical
2
low
1-2 hours per week
2-4 hours per month
med
3-6 hours per week
Troy, Jack,
David
Chris, Andrew
David
Rebecca
Chris
Andrew (ad hoc)
SLT
Andrew
Irwin
Chris (ad hoc)
Executive leaders of the organization who define success criteria according to their needs and make all go or no-go decisions
EMCOR persons assigned to use the Presto P-D-C-A software to achieve target state in six months & their Presto coaches.�Weekly coaching provides clarity on the tasks of the project as well as ‘check-in’ to maintain focus on priorities.
Subject matter experts (SMEs) (e.g. EMCOR staff) in training to be the next generation of Presto users. They are responsible to support the Core Team in key moments and feed key information into the system either as users or verbally
The PMO Administrator and development team engaged in daily quality reporting, the security and functionality of Presto software
We will use a 4-tier Governance Program with a monthly Steering Committee meeting for all Go/No-Go decisions
Executive
Steering
Committee
Core
Team
Extended Team
PMO & Tech Sup
WS1 – PMO Strategy
OBJECTIVES
CORE PRINCIPLES
DEPENDENCIES
PROJECT CHARTER
| % | W 1-2 | W 3-4 | W 5-6 | W 7-8 | W 9-10 | W 11-12 |
1. Project Charter, Governance agreed | 100% | g | g | | | | |
2. Data load (all KPIs) | 100% | | g | g | | | |
3. Core team (users) begin training on KPI reporting & IM functions | 100% | | g | g | g | | |
4. KPI training commencement | 100% | | | g | g | | |
5. Integrate the process into SteerCo | 100% | | | | g | | |
6. BAU / Ongoing CI | 100% | | | | g | | |
Key Metrics (KPIs)
|
TYPE | R | A | C | I |
QUALITY | | JS | | |
CW, Dave, RCD
SLT
AL
Risks & constraints
# of e-mails pushed/day, license daily usage, # of users trained, # of modules being used, # of tasks opened & closed per week, # of KPIs reported, # of mgmt reports delivered to Sr. mgmt
ongoing
ongoing
ongoing
ongoing
ongoing
Invoice 1
Invoice 2
Invoice 3
Project Milestone
Steering Meeting
Risk of delay
Week | | Monday | | Tuesday | | Wednesday | | Thursday | | Friday |
| | | | | | | | | | |
1 | | | | | | | | 1° SteerCo Meeting (kickoff) | | |
30-Jul-2024 | | 30-Jul-2024 | 30-Jul-2024 | 25-Jul-2024 | 26-Jul-2024 | |||||
| | | | | | | | | | |
2 | | | | | | | | | | Core Team Weekly Workshop (2-hours) |
29-Jul-2924 | 30-Jul-2024 | | 31-Jul-2025 | | 01-Aug-2025 | | 02-Aug-2025 | |||
| | | | | | | | | | |
3 | | | | | | Fixed mtgs agreed with Extended Team | | Data upload complete & Kanbans configured | | Core Team Weekly Workshop (2-hours) |
05-Aug-2024 | | 06-Aug-2024 | | 07-Aug-2024 | | 08-Aug-2024 | | 09-Aug-2024 | ||
| | | | | | | | | | |
4 | | | | Product Gaps & Key Success Metrics ID’d | | | | Project Charter Signoff | | Core Team Weekly Workshop (2-hours) |
12-Aug-2024 | | 13-Aug-2024 | | 14-Aug-2024 | | 15-Aug-2024 | | 16-Aug-2024 | ||
| | | | | | | | | | |
5 | | | | | | | | | | Core Team Weekly Workshop (2-hours) |
19-Aug-2024 | | 20-Aug-2024 | | 21-Aug-2024 | | 22-Aug-2024 | | 23-Aug-2024 | ||
| | | | | | | | | | |
6 | | | | | | | | | | Core Team Weekly Workshop (2-hours) |
26-Aug-2024 | | 27-Aug-2024 | | 28-Aug-2024 | | 29-Aug-2024 | | 30-Aug-2024 |
15-Aug-2024
We are delighted to
working with you in bringing operational excellence discipline to your company
The PRESTO P-D-C-A test pilot is conducted in 5 phases to allow you maximum control and confidence throughout the entire go / no-go decision making process
Welcome!
phase
01
PROJECT
SETUP
(define your team, milestones and core support information)
phase
02
CURRENT STATE ASSESSMENT &
DATA LOAD
INTO PRESTO P-D-C-A
(the ‘heavy lifting’)
phase 03
TARGET STATE
DESIGN ARCHITECTURE
(identify target user group, usage frequency, reporting gaps (if any) and customization opportunities)
phase
05
SUSTAIN / BAU
(Off on your own. call us if you need us)
phase 04
LEARN-BY-DOING
IMPLEMENTATION
(partner with your trainer until you feel ready-to-go)
Key decisions & milestones
Identify in-scope business
Agree core participants
Identify & agree deliverables
Agree estimated $avings
Go /
No-go
Load initial information in PRESTO
Validate reporting
Agree target users & frequency
Finalise historical data load
Train extended user group
YES
NO
1
Project setup
2
Current State Assessment
3
Target state design architecture
4
Implementation & training
5
Business-as-usual
Reporting gaps ?
No
Resolve reporting gaps
YES
Agree long-term support model
Business as usual
Ready to spread our wings?
YES
| 3-month implementation plan | ||||||||||||||||||||||||||||||
| Week 1-2 | Week 3-4 | Week 5-6 | Week 7-8 | Week 9-10 | Week 11-12 | |||||||||||||||||||||||||
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ||
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
I. Project setup | % | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
a. Project participants identified | 85 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
b. Project charter agreed | 85 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
C Activity roadmap agreed | 65 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
d. Document repository created | 85 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
e. Steering committee formalizes goals (per person) | 50 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
II.Initial data load in PRESTO & CSA | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
a. All reporting requirements gathered | 65 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
b. Organizational structure | 75 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
c. Goals, objectives & KPIs | 75 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
d. Processes & touchpoints (optional) | 0% | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
III. Target state design – build | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
a. Gap analysis performed | 50 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
b. Priority given to customization | 50 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
c. Target model workflow agreed | 0% | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
d. Job aids delivered to end users | 0% | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
e. Steering committee agrees next steps | 0% | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
IV. Implementation and training | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
a. Train administrators | 0% | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
b. Train extended user group | 0% | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
c. Agree long-term support model | 0% | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
V. Functional specs and next steps | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
a. Review best practices- lessons learnt | 0% | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
b. Review portfolio of added opportunity | 0% | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
d. Next steps & opportunity horizon view | 0% | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
Steering Committee | | | | g | | g | | g | | g | | g | | | g | | | g | | | g | | | g | | | g | | | g | |
Core Team | | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g |
Extended Team | | | | | | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g |
PMO & Tech Support | | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g | g |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
effort g low (g medium g high | | ||||||||||||||||||||||||||||||
Activity roadmap
5 days
KPI | Description | Frequency | Recipient |
1. # of e-mails pushed | The # of e-mails pushed daily by each of the Presto licensed users | Daily | All |
2. # of logins | The # of logins by each licensed user | Daily | All |
3. # of strategic projects | The # of strategic projects catalogued into the system | Weekly | Steering |
4. # of action plans opened/closed | The # of action plans opened & closed per user | Weekly | All |
5. # of users trained | The # of Presto users trained | Weekly | Steering |
6. # of modules active | The # of Presto modules actively being used by Core Team | Weekly | Steering |
7. # of KPIs reported | The # of KPIs being reported on the Presto dashboard | Weekly | Steering |
8. # of Management reports sent | The # of management reports created, sent & reviewed with the Steering committee & Core team | Weekly | Steering |
| | | |
| | | |
| | | |
| | | |
Key Success Metrics
Represents the key metrics that will be reported on a set schedule to the Steering Committee and Core Team