Because the cost of code review when pairing/mobbing is literally zero (reviewer immediately available next to a developer typing the code), it is more likely to both:
simply by encouraging people to collaborate more.
»you’ll do Continuous Integration with centralized (e.g. Subversion) than with a distributed versioning control system (e.g. Git).
»#mobprogramming is actually an implementation of the “Andon Cord” principle from Lean.
»a practice of minimizing inventory of unintegrated code.
»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.
»An abundance of those is what builds the quality in.
Not a staged and expensive, khm Pull Requests khm, process.
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.
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.
tends to be inversely proportional to the amount of mobbing needed during outages.
»