Do you want to see several different ways agile and scrum burn-down charts can lie? If so, you are in the right place! This month I went on a burn-down chart craze and posted several blog entries about the different ways those charts can lie to us or expose us to team dysfunction. In order, the blog entries are:
- Agile antipattern: Burndown charts that hide the truth
- Agile antipattern: Taking on large stories
- Which led to New to agile? Learn how to split stories
- Agile antipattern: Burndown “wall”
- Agile antipattern: Changing the definition of done
- Agile antipattern: Another burndown chart that lies!
The whole series had a LOT of web hits, so clearly I’ve touched a nerve. Good luck improving your agile or scrum metrics. Sometime next year I’ll do a series on metrics in general. Our current state of the art for agile teams is pretty pathetic because the data can be skewed so badly (as shown by all of these blog posts).
Until next time I’ll be Making Agile a Reality® by helping people understand the real meaning behind their agile burn down charts.
Related posts:
- Agile antipattern: Another burndown chart that lies! That burndown chart looks sweet doesn’t it? The team finished the iteration...
- Agile antipattern: Burndown “wall” Does your team have an iteration burndown chart (giving credit only for...
- Agile antipattern: Taking on large stories Earlier this week I posted a blog entry “Agile antipattern: Burndown charts...
RSS feed
{ 1 trackback }
{ 0 comments… add one now }