- Agile Leadership Development
- AgileSafari
- Coaching
- Facilitation
- Leadership
- Practices
- Principles
- Product Owner
- Scaling
- ScrumMaster
Agile antipattern: Sizing or estimating bug fixes
Is the bug to the left a large bug or a small bug? It looks HUGE to me! Well, in reality it is probably between .5 and .75 inches long. Not really a very big bug at all. Why do we
Agile antipattern: Taking on large stories
Earlier this week I posted a blog entry “Agile antipattern: Burndown charts that hide the truth” which dealt with one way a burndown chart could hide reality. This blog entry shows another way it is possible for a burndown chart to be misleading. The burndown
Agile antipattern: Comparing velocity between teams
I recently saw an excellent blog post about iteration velocity. Good reading in general, but the last paragraph really got my attention and is why I’m writing this blog post. Do NOT compare velocities between teams! All teams will size (or estimate) with a slightly different scale. When I teach a course on
New to agile? Do the simplest thing that works – THEN STOP!
As an agile trainer and coach I often see new teams struggle with a simple question: “How much to do on a user story?” A lot of people say the simplest thing that works is what should be implemented. I agree with that wholeheartedly and even have a blog entry on how
Ten Ways to Improve Your Planning Poker Results
People who promote the use of Planning Poker understand some of the main reasons why it is successful. People like Mike Cohn have been very instrumental in pushing planning poker and even created www.planningpoker.com for people to be able to play planning poker with
Agile antipattern: But the development lead said it would take way less time than that
I’d be rich if I had a nickel for every time I’ve heard this, or something very similar to it, in the past 30 years! Alright, that’s taking it too far, but I think I could at least afford a really nice dinner out with my family on the amount I’d have received. But that isn’t