Categories
Extreme Programming Fit for Purpose Kanban Programming Team Topologies

Start Small, Prove Value, Scale

Change efforts often stall because we try to convert the entire team at once. Mandating TDD, pairing, or any new practice for all ten people tomorrow usually triggers resistance, token compliance, and a dip in delivery. Sandro Mancuso’s reminder is pragmatic: you don’t need universal adoption to move the needle if three or four engineers adopt better habits and keep them, flow improves for everyone, fewer defects, clearer code paths, and less rework. The problem to solve isn’t “how to convince all”; it’s “how to create visible gains that pull others in.”

The lesson: improvement spreads by evidence, not edict. Treat new practices as enabling constraints that reduce variability and reveal waste. A small nucleus of early adopters can become a lever: they shorten feedback cycles, stabilize the build, and raise the quality bar. When outcomes improve, lead time down, change failure rate down, throughput up, and skeptics don’t need persuasion; they need access to the playbook.

Action: launch a six-week “lighthouse” experiment. Recruit volunteers; don’t coerce. Pick one value stream and set a clear hypothesis (e.g., “TDD + pairing on top 2 hotspots will cut escaped bugs by 30% and PR cycle time by 25%”). Make policies explicit: small batches, trunk-based dev, fast CI, WIP limits, definition of done with tests/observability. Measure lead time, CFR, and MTTR weekly. Publish a one-page Decision Note at the end: what changed, what stayed hard, what scales next. Pair lighthouse engineers with neighbors for one day a week; host short internal demos and keep a living “Golden Path” doc.

Tech Manager playbook for flow & continuous improvement: protect the experiment’s time (no drive-by work), visualize work on a single board across roles, and enforce WIP to prevent local heroics. Run a 20-minute weekly improvement kata (obstacle → next step → expected result). Fund a small, recurring Code Health budget tied to actual flow metrics, not opinion. When the numbers move, scale by invitation: expand the Golden Path, create office hours, and let teams opt in with your support. Significant improvements from a few people today are the fastest route to sustainable change for everyone tomorrow.