Izboljšajte proces z iskanjem pravega ozkega grla s podatki, spreminjanjem ene stvari in merjenjem učinka — ne z vnašanjem metodologije v celoti. Proces obstaja, da služi ekipi; ko preneha služiti, ga spremenite.
Zanka za izboljšanje
1. MEASURE → where does work actually slow down? (cycle time, review wait,
deploy frequency, incident rate)
2. FIND THE CONSTRAINT → optimizing anything but the bottleneck is wasted effort
3. CHANGE ONE THING → small, reversible experiments
4. MEASURE AGAIN → did it help? keep, adjust, or revert
5. INVOLVE THE TEAM → they know the pain; they'll own the fix
Primer
Če trajajo funkcije tri tedne, vendar je samo dva dneva kodiranja, je omejitev — čakalni vrsti za pregled kode, razpoložljivost okolja, odobritve — ne hitrost razvijalca. Dodajanje pritiska na kodiranje ne bi storilo ničesar.
