Profile picture
John Cutler @johncutlefish
, 11 tweets, 8 min read Read on Twitter
[Thread] This is a super basic hybrid #kanban board. The basic idea is that we prioritize opportunities to tackle, pull the topmost opportunity, and then run experiments to "intervene" and generate an outcome. (1/11) #prodmgmt #kanban
This can scale to multiple teams. Here we have two "opportunities" in progress. (2/11) #prodmgmt #kanban
So why not just give teams their own backlogs? Why do we even need to view this on one board? Well..chances are the teams don't have 100% dedicated team members. To do their job, roles like Ops, Marketing, UX will need an overview (3/11) #prodmgmt #kanban
If we don't have a single prioritized list, it will take extra work for UX (in this example) to decide whether to help Team A or Team B.

Team A is the right place to focus. (4/11) #prodmgmt #kanban
Visualizing it like this could help, and might better reflect reality...though you'd have to ask why Team B is working on something 1/4 the value. Is there anything better they could be working on? (5/11) #prodmgmt #kanban
For teams that make quarterly commitments, what you observe is a box filling problem. Just like "sprints", you'll see teams try to optimize how much work they can fit into the quarter, pre-solution to "reserve" shared services, etc. (6/11) #prodmgmt #kanban
The problem with that to fill the box, you'll try to figure out the size of the packages. So you get this solutioning step right here. This can occupy a big chunk of PM/designer/eng time...and often happens w/o involving the whole team. Problematic. (7/11) #kanban
The rationale for qrtr filling is that "the biz" (and all the people trying to manage shared services) want to see something like this so they can plan ahead. Sounds reasonable...except planning this way enacts a very high price.

Why? Pre-solutioning. Big batches. Etc. (8/11)
Luckily there is an alternative. Take an organization I worked with ... 90% of the time, this org "pulled" new opportunities between every 25 days and 35 days. That made it pretty easy to do something like this (and the didn't need to pre-solution): (9/11) #prodmgmt #kanban
There's another very important point here. In many cases you'll find value in doing two types of work

* Very valuable, size unknown, experiment friendly
* Size known very small, med-high valuable

If very valuable goes "long"...that's ok. It's valuable! (10/11) #prodmgmt #kanban
In summary:
* There are benefits to program level boards
* ..even when you have theoretically "dedicated" teams
* when possible, "start together" and avoid pre-solutioning
* quarter packing = antipattern
* alternatives exist to give reasonable forecasts
* VALUE! (11/11) #kanban
Missing some Tweet in this thread?
You can try to force a refresh.

Like this thread? Get email updates or save it to PDF!

Subscribe to John Cutler
Profile picture

Get real-time email alerts when new unrolls are available from this author!

This content may be removed anytime!

Twitter may remove this content at anytime, convert it as a PDF, save and print for later use!

Try unrolling a thread yourself!

how to unroll video

1) Follow Thread Reader App on Twitter so you can easily mention us!

2) Go to a Twitter thread (series of Tweets by the same owner) and mention us with a keyword "unroll" @threadreaderapp unroll

You can practice here first or read more on our help page!

Did Thread Reader help you today?

Support us! We are indie developers!

This site is made by just three indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member and get exclusive features!

Premium member ($30.00/year)

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!