Please enable JavaScript.
Coggle requires JavaScript to display documents.
Prioritized Project Backlog - Coggle Diagram
Prioritized Project Backlog
Problem Statement
What we have today is close to FIFO with some light reorder
ACK Team is smaller in numbers
ACK Some crunch points in capability
FTA remit to also help the 'underserved segments'
1:1 where not entirely necessary
1:1 by default
Field
used
to 1:1
In the absence of Prioritisation it's hard for FTA org to get cycles on key things. Otherwise 'always_busy'
Principles
Lockstep with Differentiated Delivery (i.e. we do different things for different projects)
Feed into and assist Workload Planning
Feed into and assist Capacity Planning
Prioritization a joint effort between PM and Eng roles
Simple few pulse points of a project. These could change during project life
Priority is not the same as Effort (aka t-shirt size)
Expected outcomes/Proposal/Imagine if...Start with the end in mind
We could serve as many, if not more customer projects
We're able to lessen repeated conversations
Engineer and PM time is used more presciously
We help those projects that need helping first
We spend less time on the lowest prio projects
Some Projects are a Yes, some a No, some are a Maybe (which is new). Sliding scale of Yes
PM liaising with Eng to agree offering/Conditional Approval
Make this transparent/paletable for nominators and customers
Outstanding questions
Exactly
what
is Priority a measure of?
Which we take first (an outcome)
Urgency (a consideration factor)
Importance to FTA (I'd vote this as a high level Definition, led by other factors)
Most insightful projects (a consideration fatctor)
Most aligned with our Gen3 business (a consideration factor)
[P]arking Lot
Differentiated Delivery or Prioritisation - what comes first?
How do we manage customer + AT expectations?
How do we ensure we do get to the low prio ones?
How do we keep it simple but effective. Avoiding mega-complex matrix
How do we align 4 tech Domains and 3 TZs. And 3 PM TZs
Does this take effect just at Engineer assignemt, or through life of the Project?
Consideration factors in determining Priority
ACR
Exec sponsor/Escalation
AMM Project
Gen 3 Prio Scen
Lower prio Solutions
Exceptional circumstance, the ace card (e.g. cyber attack, loss of rep, life&death)
Risks
Introduces unnecessary complexity
Lower Prio projects have extended or unclear wait times
Challenge to articulate expectations to AT/Customer
Ensure that Low Prio isn't jumped over constantly
Actions/Next Steps
Get feedback from some EMEA PMs
Get feedback from EMEA PM leads
Get feedback from EMEA Eng leads
Get feedback from Marco, Ricardo, Katie
Bounce off with others cross TZ doing similar
Pilot somehow in a Domain/Geo etc
Dare to dream... what might a Solution look like?
PM has consideration factors in their mind from the moment of pickup
Either quantitatively or subjectively 'score' Project on consideration factors
Capture Priority in a simple way in Ceres (H/M/L)?
When sourcing an Engineer this is taken into account
Do we continue this Priority into the life of the Project? I'd say Yes