“Daily Scrum are micro-management! Let’s skip them!”
– anonymous ignorant

I will comment on this very recent statement soon. Meanwhile, feel free to comment on this statement to share your thoughts with me.

A couple of weeks ago I discussed a way to run Sprint retrospectives with the scrumdevelopment user group on Yahoo. I proposed to use the recent Sprint burn down chart during the Sprint retrospective as a guideline for the team: Instead of putting sticky notes with significant events on a rather abstract timeline representing the Sprint we put them directly on the respective Sprint burndown chart.
If you would like to know more, you may find a summary of the discussion on InfoQ: Tips to Improve Retrospectives.

Today I found a brilliant and emotional video promoting Agile over Waterfall on Boris Gloger’s blog Scrum 4 You. He posted it quite a while ago but actually it cannot be promoted often enough. It’s a great story about how software development could and should work. 8 minutes absolutely worth watching:

I found an interesting article written by Srikant Chellappa and Jerry Buchanan about how Scrum can be adapted to a globally distributed delivery model. It describes that Scrum, as a framework, can and needs to be adapted to your own global organizational environment.

“Scrum is not fault-tolerant! It causes too many issues! Hence Scrum does not work!”
– anonymous ignorant
Of all the ignorant statements about Scrum I heard during the last weeks, this is my favorite one. It clearly shows that some people still don’t get the principles of Scrum: Scrum is not meant to be fault-tolerant. If it was, projects and teams would not be able to improve. Instead, Scrum has been designed to make everything clearly visible which is blocking the team from getting their work done (to deliver working software at the …