The new year has just started and it’s time for the next steps to rile your team mates. So let’s have a look at one of the activities in Scrum that can be easily sabotaged: the retrospective. Here are 10 proofed ways to wreck any retrospective:
Keep the retrospective as short as possible. No need to invest too much time in this meaningless gathering.
Only focus on negative events and ignore any positive things. This is the only valid path to improvement.
Handle a retrospective as any other meeting. Sit around a table and just talk.
Ignore the complexity of the system around you. There is always a cause and effect.
Last week I talked at the ALE Bathtub conference about the evolution of retrospectives. Fortunately, the talk was taped so that I can share it with you. I hope you’ll like it. I’m already looking forward to your comments.
Today I had a lightning talk at the ACE!Conference in Krakow (as you probably know, I’m a lightning talk addict ;)) and talked about seven Agile Myths. You’ll hear about these myths most of the time on management level, but some of them can be found on the development level, too. IMHO it’s important to be aware of these myths to be prepared for possible discussions.
Agile = No documentation
This is one of the most famous myths and I think we have to blame the agile manifesto for this. The line “Working software over comprehensive documentation” is often misunderstood with no documentation at all. But how could agile Frameworks like Scrum survive in highly regulated environments like the medical or financial industry if this would be right. For sure there is documentation, but we don’t waste time on documents that deliver no value to the project.