It’s about time to nag the product owner, isn’t it. Fortunately, there are plenty ways to do this. To help you in your quest to do so I created a list of 10 proofed ways to drive your Product Owner crazy:
Five minutes before the Sprint Review is the right time to tell your Product Owner that your team wasn’t able to finish anything. It is even more fun, if this was a planned release. Transparency is for milquetoasts.
Don’t invite the Product Owner to any Scrum meeting. He is a chicken and you are the pigs, right.
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.