Category Archives: Agile

10 things to wreck your retrospectives

http://www.flickr.com/photos/21976354@N07/2348969927
http://www.flickr.com/photos/21976354@N07/2348969927

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:

  1. Keep the retrospective as short as possible. No need to invest too much time in this meaningless gathering.
  2. Only focus on negative events and ignore any positive things. This is the only valid path to improvement.
  3. Handle a retrospective as any other meeting. Sit around a table and just talk.
  4. Ignore the complexity of the system around you. There is always a cause and effect.
  5. Always use crappy material such as cheap post-its that easily fall from the walls or old pens that hardly write. Continue reading 10 things to wreck your retrospectives

10 more things to drive your Scrum Master crazy

CrazyIt’s been a long time since I wrote “10 things to drive your Scrum Master crazy” and it’s about time to give you some new weapons. So, here they are:

  1. Hide the SM’s beloved moderation markers.
  2. Play on your smartphone during the (planning) meetings, as long as they are not talking about YOUR tasks.
  3. Always lament about the same things but don’t change anything.
  4. Keep blaming and finger pointing everyone else except yourself for all the problems, you are only a victim.
  5. Ignore all agile values as they don’t apply to you.

Continue reading 10 more things to drive your Scrum Master crazy

7 Agile Myths

Dragon
http://www.flickr.com/photos/michaelransburg/3855808163/

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.

Continue reading 7 Agile Myths