You can forget about reducing WIP
through co-creation if a culture is not optimized for T-shapeness and nurtures learning.
Otherwise, you get entrenched siloing with unbalanced capacities that very often lead to blockers and pulling in more stuff.
through co-creation if a culture is not optimized for T-shapeness and nurtures learning.
Otherwise, you get entrenched siloing with unbalanced capacities that very often lead to blockers and pulling in more stuff.
Without the ability to learn and experiment faster in order to inform your product decisions, you’re mostly left with relying on the opinions of people inside the company.
»Instant feedback loop guarantees that participating actors won’t have time to start anything else while waiting for response/feedback.
»but a feature envied, tightly coupled, Asking instead of Telling production code.
»is that you have too many specializations.
»is when it looks like it’s too soon.
»(via associated rework) on two things running in parallel is more expensive than the questionable progress being made on those two.
»reduces the cost of starting something new (the other side doesn’t have to be available) which eventually kills the ability to finish anything.
»
the countermeasure is not to deploy less often in order to not break things too often (spoiler: makes things even worse) but to build in mechanisms/practices that enable you to keep deploying often while breaking things way less often.
»