Please enable JavaScript.
Coggle requires JavaScript to display documents.
Reopening for project noms ~19th June and FY24 - Coggle Diagram
Reopening for project noms ~19th June and FY24
Why
Longer closed is bad for field perception
Opp to test out Gen3 like features
Try, Evaluate, Adapt, Repeat
Intentionally Selecting Projects
Prioritising Projects
Differing Delivery methods
Balance busyness in team - new projects for those that desire them
Shows forward momentum to team
What
Utilise the 65+ Projects we said 'No' to since 9th May
Group these into workload area
Use couple of PM leads and Eng Prin to prio
Rejection email stops as of new FY
Open to Farming the 'right' projects
Ensure business continuity. In incremental steps - less big bang. E.g. Q1 more like FY23
How
'Silent reopen' not a field big bang - at least for ~19th
Do not create confusion!
This is not == Gen3, but is Alpha testing features of Gen 3 while ensuring business contiuity
Test Gen3 like features
Intentionally Selecting Projects
Revisit 'No' Projects since 9th May list for Compelling Reasons
Compelling Reasons:
Exec Sponsor or Escalation
Competitive Win/Loss Mitigation (i.e. it's ours to lose)
Taking opportunity of available capability
Effort vlow, Reward vhigh
AMMP Adv obligation
Big
ACR Opp
Prioritised Scenario
Prioritising Projects
P1, P2, P3
Agreed by PM+Eng, based on Compelling Reasons AND Effort
Captured in Ceres. Adjustable over project life
<> Workload or Capacity. But facility to enable this
Dictates Energy put in, and Delivery Methods available
Differing Delivery methods
Avoiding saying "No" vs "Yes, and..." e.g. here are docs/recordings/sessions that would help...
Build on AVD tiered concept
"Continuum of love"
Not a No