I don't hear enough people talking

about the way XP practices improve all four Accelerate metrics.

»
Author's profile picture Dragan Stepanović

If getting feedback is cheap

it gets invited more often, which means it becomes more timely, which means it’s both more likely to be incorporated and that incorporating it is also cheap.

»
Author's profile picture Dragan Stepanović

If you feel the urge

to write that “How to conduct humane code reviews” document, there’s something deeper wrong with a given way of working and its inherent incentive structure than the lack of that document.

»
Author's profile picture Dragan Stepanović

Add enough integration and e2e tests

and the frequency of running them becomes approximate to not running them at all. Meaning, as if you don’t have them at all.

»
Author's profile picture Dragan Stepanović

The biggest problem with async work

When it comes to flow, the biggest problem inherent to systems based on async work is that they make the cost of starting new work effectively zero (the other side doesn’t have to be available in order to start new work)

»
Author's profile picture Dragan Stepanović

An environment where people have no ways of exercising vulnerability

in the first place is an environment without psychological safety.

»
Author's profile picture Dragan Stepanović

For any type of async work, I can always find you a batch size

small enough for which the flow efficiency is terrible.

»
Author's profile picture Dragan Stepanović

Two parallel universes

When it comes to PRs and code reviews, if you are optimizing for these metrics in order to improved the process (and I believe you should)

»
Author's profile picture Dragan Stepanović

Enable then nudge

If you reduce the transaction cost in the system but don’t see a follow-through behavior of reducing the batch size, consider ways of, even artificially, increasing the holding cost in order to incentivize that batch size reduction.

»
Author's profile picture Dragan Stepanović

Separate refactoring tasks and PRs

I noticed that teams that use a process that makes reviews expensive (PRs and async code reviews are one of those) also tend to have refactoring as a separate task or a separate PR.

»
Author's profile picture Dragan Stepanović