Does a ScrumMaster need a technical background? Do they need to be able to read code and coach developers on their day to day work?
Scrum and agile certification is now very much in focus. The 'certification story' is unfolding to become a major subject of debate in 2010. The story has several facets, with action from the Scrum Alliance, Scrum.org and the community-at-large, including notable bloggers and the Agile Skills Project. At issue is the basic value of certification.
Scrum Certification is one debate that refuses to die down. First, it was about the hollow nature of certification for which there was a comment “Pay the tuition, sit through a couple days of class, and you're in”. Subsequently a new format was devised, which too failed to enthuse the Agilists who were against this certification philosophy. Is there another makeover on the anvil?
A ScrumMaster as the name suggests is the guardian of the scrum process. He is a change agent supporting his team and socializing Scrum throughout the organization. He ensures smooth functioning of the team by eradicating impediments and keeping the team shielded from distractions. However, in certain scenarios, Agile teams feel that the Scrum Master is the biggest impediment.
Patrick Wilson-Welsh, Chris Beale, Gary Baker, John Huston, Daryl Kulak, and others are attempting to popularize the idea of a new role, the "Agile Team Lead", to supplant many of the existing leadership roles found in and around agile teams.
The ScrumMaster or Iteration Manager is a crucial role on Agile teams, and selecting which organisation/team to work with is important – when considering taking on a new project it’s important to set the environment up for success. This article provides interviewing advice for ScrumMasters considering taking on a project or team.
Mishkin Berteig, a Certified Scrum Trainer, took the Beta CSM Exam on Orlando Scrum Gathering this March, and posted his feedback on Agile Advice.