Discover and read the best of Twitter Threads about #Kanban
Most recents (6)
When this happens, we’re in a pickle. In true pull-system fashion, the developer has pulled another card. Test finds an issue that demands developer’s attention. What to do? (2/11) 
One solution is to say “hey dev, you can only be on two things at once...one of which is developing”. Seems reasonable...and keeps their bandwidth open to fix issues. (3/11)
#kanban tips (1/3)
Model the work, not the “workers”. With team member magnets, checklists, and markers...the bottom design can more than adequately model the work
If work ever “moves left” (e.g. QA/demo passes an item “back to dev”), then the top dsgn breaks. It is all doing.
Model the work, not the “workers”. With team member magnets, checklists, and markers...the bottom design can more than adequately model the work
If work ever “moves left” (e.g. QA/demo passes an item “back to dev”), then the top dsgn breaks. It is all doing.
Another classic anti-pattern is team/individual lanes and “splitting” the work. The bottom option will probably catalyze the right conversations....though the top option with string can also do the trick. (2/4) #kanban
A compromise if teams want their own card for some reason... is a hybrid board with “epics” (larger chunks of work), and all of their related cards.(3/4) #Kanban
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
The main excuse I've heard for tolerating abuse of women has been "We ignore him and are there for each other and the community." 1/n
I'm glad now that great competing events have arisen which not only create a safe environment for women but which repudiate harassment 2/n
Events such as @LeanAgileUS & @LeanAgileScot not only actively steward the respect & safety of those in attendance but are creating 3/n
