It's interesting to see

that most of the industry is aware that high utilization chokes the flow of a team, but at the same time often fail to recognize that pairing and mobbing provide that needed availability, enabling fast flow out of the box.

»
Author's profile picture Dragan Stepanović

Do you know that code reviews with Pair/Mob Programming are virtually free?

An abundance of those is what builds the quality in.
Not a staged and expensive, khm Pull Requests khm, process.

»
Author's profile picture Dragan Stepanović

Individual interventions in the system do not help

Systems with high transaction cost will always revert back to big batches no matter how much we try to encourage individual actors to reduce the size of the batch.
Actors act rationally within a given set of constraints imposed by the system, so the intervention point must be at the system level, not on the individual level.

»
Author's profile picture Dragan Stepanović

XP practices to rule the flow

Building quality in and fast flow cannot happen without short feedback loops.
And prerequisites for short feedback loops are high flow efficiency and low inventory.

»
Author's profile picture Dragan Stepanović

Mobbing on the outage if not mobbing on development

It’s more likely that a team will need to mob on an outage if they’re not mobbing during the development.

»
Author's profile picture Dragan Stepanović

Performance management and collaboration

More collaboration dilutes roles, siloed skills, heroes culture, and variance in engagement.

»
Author's profile picture Dragan Stepanović

Big Batches™ and assumptions

Big Batches™ embed:

  • more assumptions
  • way more second-order, compounded assumptions as a product of first order-assumptions (A x B x C x … x N)
  • carry all of these for a longer time
»
Author's profile picture Dragan Stepanović

It's actually not about practices

It’s not about:

  • Continuous Integration
  • Trunk Based Development
  • Pair Programming
  • Mob Programming
  • Limiting WIP
»
Author's profile picture Dragan Stepanović

What is a high transaction cost?

An example is of transaction cost is how long it takes us to get enough confidence that our change didn’t break previous functionality.

»
Author's profile picture Dragan Stepanović

In most cases a big batch is

an indication of a lack of mechanism to reduce the transaction cost.

»
Author's profile picture Dragan Stepanović