Scrum Masters:The Full-Time Role Conundrum

Presentation by Craig Smith at Scrum Australia 2013 in Sydney in March 2013. The Scrum Guide defines the Scum Team as being made up of three primary roles: Product Owner, Development Team and Scrum Master. The role of the Scrum Master is often misunderstood, particularly by management, so often questions start to get asked such as “can I share the Scrum Master across teams”, “can the Scrum Master do Project Management” and “can the role be rotated”? In this talk we will take a look at some of the misconceptions around the Scrum Master role, discuss how it fits into the organisational structure and tackle the age-old question of whether the Scrum Master is a full time role. We will also look at an improvement plan template to help Scrum Masters improve in their role.

Transcript of "Scrum Masters:The Full-Time Role Conundrum"

3.
Show of Hands… Image: http://www.thelicensingplate.com/wp-content/uploads/2009/05/charitable-hands.jpg

4.
“ Scrum is an agile framework for completing complex projects. Scrum originally was formalized for software development projects, but works well for any complex, innovative scope of work. The possibilities are endless. The Scrum framework is deceptively simple. …No matter which impetus stops work,Scrum Scrum ensures that the most valuable work has been completed when theDefined “” project ends. What Is Scrum (Scrum Alliance)

5.
Deliver Stuff Right Deliver the Right Stuff at the Right Time Image: http://img.ehowcdn.com/article-new/ds-photo/getty/article/129/186/86481282_XS.jpg

7.
“ The Scrum Master is responsible for ensuring Scrum is understood and enacted. Scrum Masters do this by ensuring that the Scrum Team adheres to Scrum theory, practices, and rules. The Scrum Master is a servant-leader for the Scrum Team.Scrum The Scrum Master helps those outside the Scrum Team understand which of theirMaster interactions with the Scrum Team are helpful and which aren’t. The Scrum Master helps everyone change theseDefined interactions to maximize the value created “” by the Scrum Team. The Scrum Guide, 2011

21.
Water Scrum Fall Upfront Iterative and Controlled, project adaptive infrequent planning approach to production process that achieving the release cycle typically overall plan that is happens that was first governed by between IT laid out in the organizational and the Water stage. policy and business. infrastructure limitationsWater-Scrum-Fall