Cutting Slack in Scrum

Doing Scrum can feel like a rat race: Sprint leads on to sprint leads on to sprint. There is no untracked time. That’s intentional. It helps you find time sinks aka waste.

But after sprinting for quite a while our developers pointed out the following problems:

  1. No time for technical innovation out of the development team
    • That includes trying out new technologies as well implementing cool new project ideas
  2. No time for knowledge transfer between teams
  3. At least 50% of planned work (!= sprint commitment) gets kicked
    • Some stuff might not have been vital to begin with, but other stuff is important maintenance that cannot be delayed forever

The interwebs know several remedies:

  • Leave time between sprints
    • Depending on your sprint duration, leave 4h up to 2 days between ending the old sprint and planning the new one
    • Might solve all three problem
  • 6×2 + 1
    • After 6 2-week sprints, you have 1 week to recuperate and tie loose ends
    • Might solve all three problems
    • Mike Cohn described this first
  • Developer’s Friday
    • Developers have 1 day per week to work on pet projects
    • Meant to address problem 1 (innovation)
    • Ascribed to Google
  • Gold Cards
  • FedEx-Day

To top it off, the scrum masters reported one more problem:

  • No time for the developers to reach cross-team consensus
    (The hardest kind of impediment: those that require discussion and votes)

During the last four sprints we tried a variation of “Developer’s Friday” to address all four problems. Behold:

  • NDS-Thursday
    • The first day of each new sprint is developer’s day
    • Devs can do anything they want that’s somehow work-related: research, maintenance, pet projects, impediment meetings, …
    • The name is completely random. We wanted to keep everyone’s minds as open as possible.
    • The day itself
      • In the morning we meet in a huge circle and everybody says what they’re planning. Maybe someone wants to join.
      • Those who don’t have ideas of their own may work on stories as a last resort. (Hasn’t happened yet.)
      • In the evening we repeat the circle and everyone tells the results of their work. We provide cake to celebrate 🙂
    • There’s an spreadsheet in which the developers can track their work as a memo to themselves and for future reference by others

It’s a little early to pinpoint trends, but in the beginning activities were mainly innovation-centered, whereas now they’re mainly maintenance-centered. It’s definitely a bad sign that we need that much maintenance. We need to make sure that the NDS doesn’t mitigate problems rooted in our development process. But it would be a shame to lose the NDS as it has been great for developer morale and motivation.

I can only advise not to introduce slack when you’re just starting out with scrum. We scrum for a year now and it might have been too early for us, at least with this special variant. We’ll inspect the NDS soon, so stay tuned for how it turns out…

PS: Right after I named this blog post, I stumbled across a reference to “Slack” by Tom DeMarco. Seems like it’s the book for those not yet convinced that slack is needed.

Advertisements
This entry was posted in Scrum. Bookmark the permalink.

2 Responses to Cutting Slack in Scrum

  1. Corinna says:

    Here’s an interesting link for slack = “buffer within a sprint”: http://jamesshore.com/Blog/Slack%20and%20Scheduling%20in%20XP.html

What do you think?

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

WordPress.com Logo

You are commenting using your WordPress.com 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 )

Google+ photo

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

Connecting to %s