Skip to content

Scrumphony - Marc Löffler
Syndicate content
agile, scrum, coaching, lean
Updated: 2 hours 40 min ago

10 things the Product Owner can do to drive the team crazy

Thu, 01/23/2014 - 11:58
Insanity

http://www.flickr.com/photos/14347196@N00/394867154

It’ about time to give the Product Owner a chance to fight back. With the help of Heiko Weltin I created a list as a base for the revenge. I hope you’ll like it:

  1. Create your product backlog without any prioritization. In the end you need all of the features before you can bring the product to the market.
  2. Only create the headline of your user stories and don’t add any additional content, even if the team asks. You can’t prepare everything for the team.
  3. Only use two types of priorities: “Urgent” and “Can be done later”. Anything else would be a waste of time.
  4. Always promise release dates and scope to your customer without talking to your development team upfront. You are a skilled estimator.
  5. Always add one task to a user story that keeps the team from finishing it. The Definition Of Ready (DOR) is for wimps.
  6. Insist in long running sprints of at least four weeks. If the team has more time, more features can be done.
  7. Only prepare as many stories as needed to finalize half of the sprint. The rest of the time it is the task of the developers alone to clarify the rest of the stories.
  8. Only meet once a week with the team and keep this meeting as short as possible. You don’t want to hang out with those sissies.
  9. Always answer your phone during any team meeting. Don’t leave the room as the team shouldn’t be able to continue the discussion without you.
  10. Never attend the daily scrum. Instead, talk to single developers afterwards. This makes it easier to build pressure on them.

What do you think? Do you have some additions to this list? Feel free to add them in the comments.

Categories: Blogs

10 things to drive your Product Owner crazy

Thu, 01/16/2014 - 16:44
Crazy

http://www.flickr.com/photos/ishane/1083667978

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:

  1. 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.
  2. Don’t invite the Product Owner to any Scrum meeting. He is a chicken and you are the pigs, right.
  3. Ignore the Sprint backlog and work on the features you like the most. Who cares about the Product Owner’s vision?
  4. Assign all tasks that were created during your retrospective to your Product Owner. He is the root of all evil and responsible for all the problems in the project.
  5. Don’t attend the Sprint Review. You already know how your product looks like.
  6. Never show the real product in the Sprint Review. Instead, prepare a nice and shiny power point presentation.
  7. Never talk to the Product Owner if you have questions about a feature. Instead, implement it based on your favorite assumptions.
  8. If it is difficult to establish a stable communication to your Product Owner, define someone in your team to become the so called Product Owner proxy.
  9. Always break your release date promises. Everyone loves surprises.
  10. Question everything that is in the product backlog and try to start lengthy discussions about as many features as possible. At least, that’s what your mother told you.

Try this out and post your experiences in the comments. If you have additional ideas, feel free to add them, too.

Categories: Blogs

10 things to wreck your retrospectives

Wed, 01/08/2014 - 16:48
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.
  6. Forgo a facilitator for your retrospectives. It is only a burden and will slow the whole “meeting” down.
  7. Don’t use any agenda and deliberately ignore the retrospective’s phase model.
  8. Directly start with defining what has to be changed in the next sprint. Everybody already knows what has to be done.
  9. Never check if the defined tasks of the last retrospectives were done or even had the desired effect.
  10. Never bring food to your retrospectives. Hungry participants will do anything to finish a retrospective as fast as possible.

What else could you do? I’m looking forward to your suggestions in the comments.

Categories: Blogs

10 more things a Scrum Master can do to drive the team crazy

Thu, 12/19/2013 - 16:04

Aaahhh!Now that the team is armed with new weapons, it is time to help the Scrum Master to fight back. If you didn’t read my first post on this topic have a look at the 10 things a Scrum Master can do to drive the team crazy blog post I wrote two years ago. Here we go:

  1. Get you own office, if possible in a different city or even country. Working at the same location as your team could be harmful.
  2. Count the number of finished tasks per team member and confront those lazy buggers with the obvious low performance.
  3. Try to restrict the communication with the team to Email only. You don’t want to hear their whiny voices.
  4. Don’t tell the team what you are working on. Transparency only applies to the rest of the team.
  5. Always cite the Scrum guide if members don’t stand to the Scrum rules. Continuous repetition will help raising the team’s understanding for this process.
  6. If a team member has a question, point them to Google. Google has all the answers, right?
  7. Ignore the Product Owner. It is his responsibility to create and maintain the backlog, not yours.
  8. Don’t attend the Sprint Review. It is a meeting exclusively between the PO and the team.
  9. Nurture your lack of interest about the product the team is building. This is something the PO has to take care of.
  10. Bring drums to the team’s office and play them like on a slave ship. Every good team needs a beat.

I’m looking forward to your additions in the comments :)

Categories: Blogs

10 more things to drive your Scrum Master crazy

Mon, 12/16/2013 - 11:44

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.
  6. Simply ignore your Scrum Master, especially when he tries to coach you. Coaching is evil!
  7. Ignore the findings from your latest retrospective because you have more important stuff to do.
  8. Write as many things as possible on ONE post-it. Clustering is much more fun this way.
  9. Don’t put your tasks on the sprint backlog. Your Scrum Master is an evil micro manager. I swear. Transparency sucks.
  10. Ask your boss to put the Scrum values into the performance goals of every employee.
Categories: Blogs