Almost every discussion I have that starts with “we need to go faster” ends with me asking the team to “define value”, and then do less once and work in smaller batches.
It is at this point that the reality sets in ...1/3
#agile #kanban #prodmgmt
It is at this point that the reality sets in ...1/3
#agile #kanban #prodmgmt
... the reality is that the current system is optimized for:
-saying “yes we’re on it”
-keeping people busy
-brokering resource capacity
-keeping track of all the work in progress
-providing plausible reasons why nothing is shipping
Well...2/3
#agile #kanban #prodmgmt
-saying “yes we’re on it”
-keeping people busy
-brokering resource capacity
-keeping track of all the work in progress
-providing plausible reasons why nothing is shipping
Well...2/3
#agile #kanban #prodmgmt
This should be easy to unwind, right? It’s math. Do less smaller stuff = go faster. Limit WIP ... discover/remove bottlenecks.
Well no. Because those optimizations run so, so deep. Reputations. Ego. Agendas. Promises to investors ... 3/4
#agile #kanban #prodmgmt
Well no. Because those optimizations run so, so deep. Reputations. Ego. Agendas. Promises to investors ... 3/4
#agile #kanban #prodmgmt
...and probably hardest of all ... in a pull system that is transparent, there’s no way to avoid having the hard conversations. You either face your issues, or you don’t.
Which highlights the #modernagile principle:
“Make safety a prerequisite” 4/4
#agile #kanban #prodmgmt
Which highlights the #modernagile principle:
“Make safety a prerequisite” 4/4
#agile #kanban #prodmgmt
• • •
Missing some Tweet in this thread? You can try to
force a refresh
