Parallelization of work
can only make a team slower if people need to integrate often. And some teams don’t realize how often they actually need to integrate.
»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.
Product reflects the organizational power structure
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.
»WIP drops as a side effect of focusing on minimizing the length of feedback loops
Instant feedback loop guarantees that participating actors won’t have time to start anything else while waiting for response/feedback.
»You most probably don't have a problem with mocks
but a feature envied, tightly coupled, Asking instead of Telling production code.
»Maybe the reason you have a too big team
is that you have too many specializations.
»Just-in-time moment for exponential scenarios
is when it looks like it’s too soon.
»The cost of delayed feedback
(via associated rework) on two things running in parallel is more expensive than the questionable progress being made on those two.
»Async way of working
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 key to building the quality in is to make making changes very cheap
