Dragan Stepanović

Actually, most often they hurt predictability because of a narrow focus on achieving the short term goal of meeting an estimate and piling up cruft, which then hurts predictability.

In order to shorten lead times and increase throughput of the system focus on managing (reducing) the queues, not the work.

I have a feeling that decision making in organizations in which everyone is so busy that they have no time to build relationships with other people in the company and talk about the topics that are not related to the task at hand will necessarily grind to a halt.

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:

• get the feedback in a timely manner (as you type the code) and
• get very rich feedback (which tends to be the case because it’s verbal and immediate, in context)

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.