One of the 12 principles behind the Manifesto for Agile Software Develop is: At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. This adjustment of behavior can take many forms: from stopping a practice that is not fruitful to simply doing more or less …
While a team can rollback a code push that didn’t go well, refactor a feature that didn’t hit the mark, the one thing they can never recover is lost time. Use this retrospective technique to expose the thieves of time pestering your team,
TL;DR Limit the WIP by process step Finish what is started When “blocked” instead of picking up something new resolve the bottleneck The end result will be a self-optimizing system of continuous improvement in which value throughput is always increasing.
Hawthorn, Goodhart and Friedman Walk Into an Agile Team Room – What Happens Next Will Amaze You… Velocity is one of the most commonly used agile team metrics. Teams (and their stakeholders) often focus on “improving velocity” without either a proper consideration for root causes that impact velocity or a …
If you’ve read my tag-team post w Tanner, you’ll remember Ed, the command and control boss. Ed now has a choice: embrace change to become an effective leader of his team (and perhaps ultimately a change agent) or find a new C2 gig. The first path is going to be quite …
