Unfortunately, the team was listening and was in the process of responding with progressively less meaningful updates from day-to-day.
We have all heard the relentless “no blocking” statement but these updates are particularly troubling. Here’s why:
- It’s incredibly vague
- The only thing it really says is that he is doing something the team didn't agree to
- Because of Bart’s position on the team it is a dangerous and potentially damaging to overall team communication and productivity, this becomes the model behavior if allowed to continue
- There are customers in the room with very poor poker faces, it’s obvious they are confused and worried that the team lead isn’t working on Sprint commitments
After four consecutive days of this it was clear that it had to be addressed and as Scrum Master this falls right to me for immediate action.
I’m a believer in the concept of “criticize in private, praise in public” so I grabbed Bart for a quiet hallway chat ten minutes prior to stand-up to make sure that there won’t be anymore of this type of “update.” I made no bones about the negative impact and made it clear that he must provide an example for all to mimic. The non-update update is not acceptable. In our discussion I made the above points and really didn’t get any pushback at all.
What I did get was an explanation of a change in his responsibilities that I wasn’t aware of. His boss has directed him to serve in more of a leadership role and technical mentor role and commit to significantly less coding each sprint. Ok, great. How does this impact his responsibilities to the team?
Obviously, he will have fewer stories and tasks that will require updates during stand-up. However, the team, of which he is a part, still has to make its commitments.
After some discussion we arrived at the following conclusion; rather than providing updates on tasks etc. he will provide specifics on what he did and will be doing to help the team meet every commitment.
Enough time remained for him to spend some time thinking from this perspective prior to stand-up. Bart went first. Response to his retooled update was immediate. The quality and value of every update went back to where it was before the change.
Lessons Learned
- Don’t wait to address a performance issue, end it as soon as you identify it
- Communication is key, we could have addressed the subtle role change proactively had it been communicated
- Everyone on the team is responsible for the team meeting or not meeting its goals
- People in leadership positions lead, good or bad, whether they intend to or not
