GAH! Do you ever hear that statement in relation to stand-up, planning, retro and demo? I do. I hear it far more often than I would like to. Often I hear it’s because the Scrum Master isn’t good. It’s not just a Scrum Master responsibility though and, generally, that’s not the case. Sure, for a new team, there’s a need for the Scrum Master to facilitate and teach. No doubt about it but, when a team is knowledgeable about Agile and Scrum AND has been together for a while, the team can own the solutions too. However, sometimes, you hear other reasons why I think a team member would feel this way:
1. The ceremonies (I really can’t stand that word) aren’t useful to the team members and take WAY too much time prepare for and conduct.
2. The team wasn’t listening during all that training about what they’re for, who they’re for and who owns making them useful and productive.
Too often, I also hear people blame training for the reason things aren’t working or say training is THE answer to the problem. Since I disagree with this more often than not, I’m going to focus on number 1.
Stand Up – It’s for THE TEAM. It should take no more than 15 minutes and you answer the 3 questions (when you’re just starting out). If it’s taking longer and it feels statusy, then, you’re doing it wrong. It’s not just the Scrum Masters job to point this out and keep the team on track. Come to stand up prepared. Don’t just look at the board once a day. Listen to what your team mates are saying and get in the practice of holding each other accountable.
Planning – It’s for THE TEAM. It’s when you decide what items to pull off the product backlog and how you will as a team execute. It takes a while when a team is starting out. If it’s still taking an inordinate amount of time and feels like overhead, get to the heart of WHY it is that way. Maybe the team isn’t focusing. Maybe the stories aren’t written well. Grumbling about it being overhead won’t fix it though. It WILL make it worse. Discuss, investigate and experiment but don’t continue to complain about it.
Retro – It’s for THE TEAM. It’s where the team takes time for themselves to reflect on how they’re working as a team. It’s to identify ways to improve – AS A TEAM. To me, it’s the most important of the ceremonies (there’s that word again). If it’s not useful, read Esther Derby and Diana Larsen’s book on the topic: Agile Retrospectives: Making Good Teams Great. Continuous improvement is a Hallmark of a high performing team. If you’re complaining it’s overhead, you’re not on one and you should do something about it. By doing something about it I do not mean you should leave the team. I do mean you should step up, learn and apply it.
Demo – It’s for THE TEAM to demo to their Stakeholders how they delivered on their commitment. It’s to get feedback and show off how awesome the team is. If it feels like overhead b/c you’re prepping for three days for it. STOP prepping for three days for it. It shouldn’t be onerous. It should be demonstrative. As a team, decide how you will conduct demos going forward and start experimenting.
Teams are empowered. Team members are empowered. You don’t need to wait for someone else to fix it. As a team member, you can and should fix it. Your Scrum Master can help. If you really, really want to lose the “pain” associated with the ceremonies (dang it!) learn how to make them effective as they’re described and, as you mature, modify them to suit the needs of your team. Also, you need to want to be a part of a team and a solid, if not high-performing one, at that. Teams need to start somewhere and complaining isn’t starting. It’s just complaining. Teams succeed or fail as a TEAM. That applies to how they work together as much as the product(s) they deliver.