Hopefully there are only positive stories to go around, but sometimes a new ScrumMaster enters into a team that has been well established and set in its ways. Sometimes, a team has no idea what a daily Scrum meeting or Retrospective Meeting is.
A quick reminder of the Daily Scrum:
- About 15 minutes
- Everyone stands
- Everyone shares three things: What they accomplished yesterday. What they will work on today. Any blockers or impediments they have.
- Only developers and people involved with development may speak.
- Product Owners and other Stakeholders can stay silent.
A quick reminder of a Retrospective Meeting:
- It is a meeting to review what went well (celebrated) during the last development cycle and what can be improved.
- It happens after every sprint.It includes the entire team.
- It is a safe haven of feedback of any kind (as long as it’s tactful and nice).
- It needs the participation of every single person.
- It needs a good facilitator who can stay out of the conversation and maintain the flow of ideas and thoughts.
In most cases the ScrumMaster will always lead the Daily Scrum and Retrospective Meeting. But this need not always be the case.
David Bland has a very solid article on “Rotating Team Roles” when doing these two types of meetings. What he means by this is that a different person should lead these meetings every time. His reasons for this are very good:
- It gets the entire team involved.
- It opens up new channels for communication.
- It builds trust between the ScrumMaster and developers (When he helps them prepare for the meetings and answering questions).
- It gives different leaders of the Retrospectives different techniques for leading the meetings.
He reminds us that we need to do this in cycles using the ScrumMaster as the example first, and then assigning a different leader next, etc.
What a great way to increase participation and collaboration!
Read the full article here.