今日推荐英文原文：《How To Have an Awful Daily Scrum》
今日推荐英文原文：《How To Have an Awful Daily Scrum》作者：Chris Cooney
How To Have an Awful Daily Scrum
A story of Skype, punctuality and… Quentin.Monday. You’re standing in a misshapen semi-circle, taking it in turns to yawn and drink coffee while someone plays with a laptop. “Bloody Skype”, mutters one of the engineers, as she hovers over her laptop, logging back into Skype for the third time.
“Since Microsoft took over this damn thing it’s…” she continues speaking, but it crumbles into the angry sounds developers make when faced with a product following a Microsoft acquisition.
Skype Begins to Behave Itself…After some time, the connection is made and the sound of background chatter from an office 250 miles away confirms that the guest of honour has arrived. At this point, you and the team have been stood there making idle, awkward chatter for five minutes.
Speaking of the team, you’re one member short. Harry is late almost every day because he lives somewhere on the set of The Lord of the Rings. His commute involves three trains, a donkey and silver coin to cross the River of Styx. While Harry makes his voyage, the team waits.
After another minute, Harry rushes in. He discards his bag on someone else’s desk with a dismissive sling and stands at the periphery of the not-so-semi-circle. He holds a bright green apple in his right hand and leans against the board, a thin sheen of sweat glistening just beneath his hairline. The team stares at the apple, then at Harry. Surely not.
He makes his first, 100 decibel assault of the apple. “So we’re just thinking about how to refactor CRUNCH the class, it’s a little CHOMP complex…”.
Each bite is punctuated by sharp, satisfied crunches and while Harry has the decency to chew with his mouth closed, he doesn’t have the decency to go and do it somewhere else. Harry smiles. Everyone bristles.
Harry you son of a…
Okay, You’ve Got a Full Team. Let’s Get GoingYou each answer the big three questions. Robotically, without so much as a fleck of enthusiasm, your test engineer begins to speak.
- “Yesterday I worked on selenium tests for the UI. Today I am working on selenium tests for the UI. No blockers.”
The cycle repeats, with each person taking their turn in a counter clockwise fashion (for some reason). Everyone answers the dreaded three questions. You’re 12 minutes in. Your patience is on a diet.
Suddenly, Some Rogue Nonsense Appears!
- “Okay, so there’s a lot of odd stuff going on across the business. I’m not sure if this is really the place for this but since you’re here, next sprint I’m thinking about how we’re going to solve… and there’s another team with concerns about… and my hair just isn’t quite as smooth as usual today…”
The 15 minute timebox is a distant memory. This… is Quentin.
By the time Quentin has finished going on, a silent pact has formed between the developers. First, murder. Then, beers. At 19 minutes and 38 seconds, everyone signs off and returns to whatever they were doing before. The closest thing they’ve formed to a plan is an alcohol-fuelled homicide.
So Whose Fault Is It?I could blame Quentin and play to a bunch of engineers and their god complexes (including my own), but the truth is that the whole team is to blame. Let’s go back to the Scrum guide to review what the point of a stand up is:
The Daily Scrum is held every day of the Sprint. At it, the Development Team plans work for the next 24 hours.What coherent plan was formed in that story? What joined up move on the sprint goal was communicated? All they did was stand there and say words at each other until they were permitted to sit down. Their segment of the daily scrum became an incantation. A magic spell to speed up time toward their inevitable return to headphones and anti-social coding.
And How Would We Fix It?I’m so glad you asked.
- If everyone is there who can form a plan, begin talking. If Skype isn’t working for the benefit of someone else, someone can always catch them up after. Standing around and waiting to start drains all of the energy out of the meeting.
- Keep it punchy. Ask questions when needed but encourage engineers to be succinct in their points. 15 minutes is the absolute maximum. It’s a guard rail, not a goal.
- Form a plan. That means ask each other questions and constantly refer to the sprint goal. At the end of the stand-up, every team member should be acutely aware of how to tackle the next 24 hours.
- Walk the board, not the team. People might be pairing up and you don’t wanna force random waffle. Focusing on the work means you only talk about the work.
- STOP BRINGING FOOD TO STAND-UPS YOU ANIMALS!