My tip for new Scrum Masters

When I became Scrum Master, I initially felt pretty helpless. I had been trained, but the training told me to nudge people but not manage them. Guide and mentor the team — but let them be the drivers. I originally found these concepts difficult to grasp. I needed to figure out how to be effective.

What the training did not make clear to me is that when acting as Scrum Master, you are not focused on the topic being discussed. Instead, you are focused on how productive the discussion is. Is it in line with the goals of the meeting? Is it taking more time than can be afforded? One of ways a Scrum Master can help the team without interfering in its autonomy is with time discipline. I am still surprised how much the members of my team appreciate having someone who keeps the discussion on track and time-boxes discussions. For new Scrum Masters, I think this is a great way to be a value to your team.

Start by scheduling every meeting the team needs for the next sprint. This way you have the longest lead time to learn about vacations and odd schedule conflicts, and it gives you the best chance to have your favorite rooms.

A couple of days before each meeting, write a time-based agenda. Pay special attention to how long something really takes. For example, assume that you are going to break down Product Backlog Items (PBIs) and you have a one- hour meeting. Subtract ten minutes for late comers, setup, questions, and other beginning meeting noise and then decide how much time an item needs. If the team wants 10 minutes, then the Product Owner (PO) can bring in five items. I usually use 10 minutes to break down an item and give the PO the option to take another 5-10 minutes at the end.

In order to keep meetings moving along, you may need to get the discussion back to the main topic. Interrupting a person mid-sentence to keep a meeting on track is tough when you start as Scrum Master. It’s easier if you make a card, such as “Time” to hold up. Explain that you will do this up front so that everyone understands, and let the speaking team member wind down or summarize. In my experience people appreciate someone doing this, because you are respecting their time.

If you’re uncertain about the importance of the topic being discussed, when time is called, you can let whoever the meeting is for decide whether they need more discussion or just vote – thumbs up for yes and thumbs down for no.

I find it helpful to bring a stopwatch to meetings. A stopwatch is a dedicated device, so it works better than a cellphone, where you might need to mess with the screen turning off. It’s easy to read and operate.

It takes a lot of little things to increase the team’s velocity. Keeping track of time is a good place to start. It ensures all the meetings happen and that they are productive. But more importantly, people will be happier to go to meetings that are valuable and where issues are resolved.

Sample ceremony agendas (assumed attendance: five team members, Scrum Master, and Product Owner).

Standup (15 minutes)

  • Make sure all P1 bugs are being addressed (1-3 minutes)
  • Product quality status (1-3 minutes)
    • Note any failures in acceptance tests
    • Note current bug count
    • State any issues with current release
  • Team member updates (1-2 minutes each)

PBI break down grooming (1 hour)

  • 10 minutes — Noise
  • Five PBIs for 10 minutes each
    • If a PBI runs over, PO has option to continue or move on

PBI bulk estimation (1 hour)

  • 10 minutes — Noise
  • 20 minutes — Team reads easy PBI out loud
    • Assuming that we have 20 PBIs to groom
  • 15 minutes — Sort PBIs by complexity
    • Anyone who has a question marks the PBI with a sticker
  • 10 minutes — Discuss any PBIs with stickers
    • POs go first
  • 5 minutes — Bucket PBIs

Retrospective (1 hour)

  • 10 minutes — Noise
  • 15 minutes — Go around the room asking what went well and what went badly
  • 10 minutes — Deeper discussion in impediments
  • 10 minutes — Prioritize impediments to work on
  • 10 minutes — Go over the team rules and ceremonies and make sure they make sense

Planning meeting (2 hour)

  • 10 minutes — Noise
  • 10 minutes — Discuss bugs for next sprint
  • 15 minutes — PO goes over two sprints worth of backlog items explaining at a high level what they want next
  • 15 minutes — Discuss order of items, missing items, impediments that should be added to top of list
  • 10 minutes — Break
  • 5 minutes each to discuss PBI
  • Any PBIs that needed more discussion get the rest of the time

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: