Discover and read the best of Twitter Threads about #modernagile
Most recents (5)
Just read a story about a new COO who started their first day on the job by cleaning the kitchen.
They drew a line saying that " spread the word that the next person I caught leaving a mess for their fellow employees to clean up would be shown the door."
They drew a line saying that " spread the word that the next person I caught leaving a mess for their fellow employees to clean up would be shown the door."
Leaving a mess for their colleagues to clean up?
Sounds like Business As Usual in a lot of corporate software groups.
"If I don't do a good job, then that's okay. I can close the ticket and someone else will fix it."
Sounds like Business As Usual in a lot of corporate software groups.
"If I don't do a good job, then that's okay. I can close the ticket and someone else will fix it."
Because, sadly, in many shops "getting things done" is "closing tickets."
"Look how much we did! We closed 20 tickets!"
"What can we demo today?"
"Well, nothing. It doesn't work yet and we can't deliver, but 20 tickets!"
"That's fine, then. Next sprint, we want 30 tickets."
"Look how much we did! We closed 20 tickets!"
"What can we demo today?"
"Well, nothing. It doesn't work yet and we can't deliver, but 20 tickets!"
"That's fine, then. Next sprint, we want 30 tickets."
I can estimate how long it will take me to drive to Des Moines, and be "close enough." There are lights, stops, traffic, weather to consider, but mostly it's me choosing route and rate.
Route has speed limits, traffic features, raw distance. Those are not up to me, really. I have limits, but the limits make the trip predictable.
The fewer items are under my control, the less likely the estimation.
Can I get to des moines in 3 hours? Probably, if you provide me a fast plane or fast helicopter and clear weather. Otherwise, no.
Can I get to des moines in 3 hours? Probably, if you provide me a fast plane or fast helicopter and clear weather. Otherwise, no.
Realized I had some posts that actually make sense as a series... a little blook
1/10 Moving beyond the platitudes of outcomes vs. outputs....it is all a spectrum
hackernoon.com/beyond-outcome…
#prodmgmt #ux #design #agile #modernagile
1/10 Moving beyond the platitudes of outcomes vs. outputs....it is all a spectrum
hackernoon.com/beyond-outcome…
#prodmgmt #ux #design #agile #modernagile
2/10 Distinguising value and sequencing. Start with opportunities before getting bogged down in “LOE”
hackernoon.com/value-and-sequ…
#prodmgmt #ux #design #agile #modernagile
hackernoon.com/value-and-sequ…
#prodmgmt #ux #design #agile #modernagile
3/10 Prioritizing non-feature work and continuous improvement ... there’s value here too.
hackernoon.com/prioritizing-n…
#prodmgmt #ux #design #agile #modernagile
hackernoon.com/prioritizing-n…
#prodmgmt #ux #design #agile #modernagile
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
My product-nerd-friend @atheus...hey you should post a thread of some drawings. Here goes:
1. The classic “here’s why you do incremental delivery” drawing ... aka “how not to dig a deep hole”. Yet legacy budgeting practices encourage one/not other
#prodmgmt #ux #design @atheus
1. The classic “here’s why you do incremental delivery” drawing ... aka “how not to dig a deep hole”. Yet legacy budgeting practices encourage one/not other
#prodmgmt #ux #design @atheus
2. Here’s is the “perpetual cone of uncertainty” ... namely, unless you are a project shop, you’re likely to ALWAYS have uncertainty, even if you are also reducing it constantly
#prodmgmt #ux #design @atheus @ProductPlan
#prodmgmt #ux #design @atheus @ProductPlan
3. I’m seeing this crazy symmetry in terms of systems / technology & org design. They are all feeding into each other. Exhibit 1: the shift from batch processing to stream processing (cc @gwenshap ) and networked orgs @NielsPflaeging
#prodmgmt #ux #design @atheus @productplan
#prodmgmt #ux #design @atheus @productplan
