Posts Tagged Retro
At first glance, this is not a board hack. I’ve been working more and more with remote teams lately, and that makes the use of physical, easily hackable materials much more difficult. So my concept of a hack has altered slightly. What ‘hacks’ to the physical process will make it work for a team that is not co-located?
I’ve run retros where a couple of team members have been remote. And I always make sure to enable them to participate as fully as possible in the physical sticky note activities – by getting them to message/slack.text them to me so I can write them up. But what about when everyone is remote? What happens then? Last week I ran my first retro where the entire team was remote. That’s right, not one of us was in the same room!
So my beloved post-it notes were replaced with a tool called stickies.io. It lets everyone log into a shared ‘wall’ where they can individually create sticky notes, then we can group them, vote on them and discuss them. We used Google hangouts, with chat and also Slack for text communication. It certainly was not as good as a physical interaction, but it turned out better than I expected.
What did we learn?
- The experience was “equalizing” – we all learned what it felt like to be someone working remotely. Usually this team has 4 or 5 people co-located, and they tend to get most of the air time in meetings, having everyone remote meant the interactions were more equal.
- Facilitating when you can’t see people’s faces is difficult. It took a while to get used to scanning Hangouts, watching the chat, Slack and reading the sticky notes. Practice makes perfect!
- We had to turn off video because the connection was dropping out. This improved the connection, but the facilitating was even harder.
- stickies.io is tricky to use on a small screen with so many people (easy to stick notes on top of one another, and group them by mistake). But it is infinitely scalable so a big screen made a big difference.
- For me, the cognitive load of interacting with the technology (typing, organising stickies) whilst facilitating was much more difficult than dealing with physical post-its, so having a second person move the sticky notes around and another capture actions while I facilitated helped a lot. This will probably get easier the more time I do it.
- It’s can be to tell who someone is from their stickies.io avatar, especially if it doesn’t match their Slack and their Hangouts avatars. Next time we might preface each sticky with the author’s name.
- We were pretty good at not talking over each other. This team is used to having 3 or 4 remote members at any one time, so they are aware of this already, if you’ve working with a team not used to this then you might need some tactics to combat it.
stickies.io has a handy feature that allows the facilitator to switch the board to incognito mode so that everyone can focus on just their own stickies – solo brainstorming. Of course, there’s always someone who wants to game the system, so in less than a minute one of our developers had hacked this too. Not quite the kind of hack I hope for…
Retrospectives are the place for everyone to have their say on what’s working and what isn’t. But does everyone have their say? Who’s talking? Who’s not?
Sometimes it’s hard to tell who speaks and who gets drowned out. To get to the bottom of this, one of our team began mapping who spoke during the retro, almost as a doodle. It’s a simple idea which has been evolved by other members of the team as they had a go at it. The latest incarnation of the heat map shows who is interacting with who. The secret sauce here is empowerment. This mapping process started because Dan felt empowered to just do it, and each subsequent team member who evolved the map felt empowered to adapt and improve it.
When you can easily see who’s interacting and who’s not, you can see where the whole team is missing out on important contributions from some members, and we can ask why.
“We wanted a way to notice recurring patterns in glitches.”
This team gets through an enormous amount of work which requires many hand-offs with other departments. When there’s a glitch in a part of the process, the team member adds a little red sticker to a card, often with an accompanying note about why there was a glitch. If a story accumulates a few of these, we can see it’s in trouble. Also, the little stickers are an excellent reminder for retro, where we have a chance to talk about how to address any larger issues that might be driving them, or even use “5 whys” to delve into the root cause of glitches.
Spotted: Lonely Planet
Dan says: “Just for interest – I thought it would be interesting to see whether any notable patterns came out of it.” – Dan Heath
Sometimes at retro it’s hard to remember everything that went on during the iteration. And sometimes you don’t spot problems at the time they are actually happening. There’s just too much going on.
The brilliant Dan Heath set up a camera with a script which took a photo every 5 minutes and stitched them together as a movie. The team can watch the iteration at retro and can see the cards moving (or not moving) on the wall. Where did they become blocked? Anyone remember why? Who took the last bit of cake?
Dan’s script stitches the images together into a month by month archive of activity on the board, and it only captures images during working hours, so you don’t get hours of spooky darkness.
He was happy to share his scripts. Here are the crontab entries, other scripts are available by email (although Dan warns they were done as a really quick hack job – “the nastiest hack I’ve written since uni”):
# ************* Crontab ***************
# m h dom mon dow command
*/5 8-18 * * mon-fri export DISPLAY=:0 && /home/robh/boardcam/vlc-cmdline/run.sh
1 19 * * mon-fri /home/robh/boardcam/vlc-cmdline/run_daily.sh
Spotted: LPOS development team