I Wish There Was No Scrum Master in My Dynamics CRM Teams
When Ken Schwaber and Jeff Sutherland presented the Scrum agile framework in 1995, they borrowed the word scrum from the 1986 HBR article ‘The New New Product Development Game’ by Takeuchi and Nonaka. Nonaka and Takeuchi used the term scrum in a terrible analogy between rugby and new product development. I'm guessing that Schwaber and Sutherland had more experience playing Dungeons & Dragons than rugby. How else would they have arrived at such a lame name: Scrum Master? Does that job come with a pointy hat and a wand?
(For the record, I was a Dungeon Master at the Irish and European role-playing games championships when I was a kid and was a winger for Edinburgh Northern 1st XV rugby team).
There's definitely a role on a Dynamics CRM team that's using Scrum for someone to mentor the stakeholders and the team on the principles and practices of agile software implementation, and to guide the team toward maximum velocity. I just wish that role wasn't called Scrum Master.
Role of the scrum master
The scrum master serves the product owner, the CRM development team, and the consulting firm and the customer in different ways.
The scrum master serves the product owner by helping him or her envision the features that will have the most impact and providing backlog management coaching.
The scrum master serves the CRM team by facilitating sprint events, helping the team find and adopt practices that maximise the value they deliver and by removing impediments to the team's progress. The scrum master ensures the team doesn't over commit to too many stories in a sprint; a good coach ensures they are not becoming complacent either.
The scrum master serves the consulting firm by mentoring the CRM team's resources. They also serve both the customer and the consulting firm by managing risks and issues, and looking after the project's budget.
Do we need a CRM project manager?
There is also a role for someone to perform the traditional project manager responsibilities in CRM projects performed by a consulting team for a client.
Lots of Scrum purists reject the notion of traditional project management. I agree with them that the scrum master's role is not to produce project plans or to assign work to resources, but let's agree that issue logs, budgets, and status reports are still useful artefacts on agile projects.
In a Scrum for Dynamics CRM project, the scrum master, product owner and development team looks after risks and issues, budgets and resources and whatever project status reports are required by the client and the consulting firm. They self-organise and decide how best to share these responsibilities.
In future articles, we'll revisit the role of scrum masters on CRM projects and discover how they can really maximise the value created by the CRM team.
What's your opinion on the scrum master role -- are you more of a Dungeon Master or Scrum Half?