Scrums, as we’ve talked about before are an integral part of Agile software development. Frankly, even if you’re not Agile, you can participate in Scrums. I suggested a little while back to a friend and CEO of a company that he start doing scrums for his development team even if they aren’t really doing anything Agile. Reason? To begin the process of disclosure and transparency to the company about what is going on so communication and collaboration can permeate the business. So far, he reports that it’s been a great step in their business!
So let’s review the purpose of the ScrumMaster:
- To remove escalated obstacles or resolve dependencies between team members and teams
- Remind the team of mission/value statements for each project
- Quickly document any necessary follow ups with team members
- Give updates and information regarding enterprise releases an pertinent information
- And… to remove dependencies between teams!
Some points to remember for your scrum group:
- No more talking about meetings (Meetings don’t show work). If there are actionable items from meetings that people need to know about, talk about that. Remember, we’re looking for input.
- Project Leaders, show up!
- Project Leaders, set the example. Main purpose of PM’s are to take away impediments!
- Project Leaders, should share the most, give direction, and give information.
- Project Leaders, ask questions that follow up on people’s issues:
- “Who do we need to help on that.”
- “What does that mean?”
- “When do we need to meet on that?”
- “I think that ___ should be involved with that, correct?
- Yesterday, today, what blocks me?