Skip to main content

Sprint Review Meetings

At the end of every sprint my team has a sprint review.  It’s been a bit of a tradition and I think
everyone agrees that we all got a lot out of it.  People share best practices, things to watch out for and generally check in with each other. To have a great review meeting you need to get people to open up. How do you create a comfort zone where people can speak up? It is the sticky issues that generally slow people down, annoy them and sometimes cause people to quit their job.

Here are a couple of tricks I’ve accumulated over my twelve years of management:

Ask people to write things that they consider “accelerators” and “blockers” on sticky notes.  Ask them to come up with at least 2 of each.  It will take a little effort on everyone’s part but it’s better to have a bunch of things that are minor rather than miss one major issue.  Somehow writing things on a sticky note and not adding your name to it makes people more comfortable than speaking up in front of everyone.  After everyone has their stickies, I ask people to randomly put them into two areas of the whiteboard.  This generally gets the group going with ideas for improvement and shared lessons.

Second tactic that I’ve employed is asking people what they learned in the last iteration.  I found that for technical folks it’s easier to say: “I learned that the build is really unstable” rather than “you know that our build system is total crap” in front of people who might actually be maintaining the system.

Last method, which I rarely use, but it could work for a distributed team is SurveyMonkey.  Any anonymous system where you can create a safe environment is a great way to get your team to talk.

How about your team?  How do you get opinions from everyone?  Get in touch with me via twitter @mikebz, post a comment on www.mikebz.com or find me in other ways.

Post a Comment

Popular posts from this blog

SDET / QA Engineer Interview Checklist

After interviewing and hiring hundreds of engineers over the past 12+  years I have come up with a few checklists.  I wanted to share one of those with you so you could conduct comprehensive interviews of QA Engineers for your team.

I use this checklist when I review incoming resumes and during the interview.  It keeps me from missing areas that ensure a good team and technology fit.  I hope you make good use of them.  If you think there are good questions or topics that I have missed - get in touch with me!


SDE/T or QA Engineer interview checklist from Mike Borozdin
If you like this checklist you might want to check out these posts:
Emotional Intelligence in Software Teams  and Good-bye manual tester, hello crowdsourcing!

Two Critical Questions for Your Next Interview

I’ve interviewed probably over 500 engineering and management candidates over the last several years.  There have been a lot of really smart people who have applied at DocuSign, Microsoft and Tempo Automation. A surprising number of them didn’t have a clear answer to these two essential questions:

Why are you interested in joining our team?Why should we be interested in you? 
If you are an applicant, having a prepared answer for these questions is critical.  If you are a hiring manager, you should ask them and have a clear answer to these questions at the end of the first interaction with your future team mate.

In a field where work is somewhat predictable and static, those questions are less critical, but in software development perseverance, ingenuity and focus make all the difference. These are the two main questions that will separate a subpar and a superb hire.

When I discuss those two questions with an applicant I try to go below the surface.  Generic answers like “it says you ar…

Chief Collaboration Officer

When you search for the word “collaboration” on the Internet, the top hits are mostly software packages you can buy.  Software can facilitate collaboration, but it doesn’t make people collaborate on its own.

One of the key functions of a technical leader is to bring a team together, help people share ideas, and facilitate team members helping each other.  When a software leader overlooks this key function, you end up with a group of individual contributing engineers instead of a cohesive team.
Before we get into tactics, we should ask “Why is collaboration important for an engineering team?” 
It’s critical to examine your assumptions, so here are my reasons for why a group of engineers working on their own are worse than a team working together: Smart people learn from each other.Getting your plans and designs reviewed by other people allows you to leverage their experience and check your assumptions.Collaboration produces artifacts that stay after collaboration has taken place (such…