Skip to main content

Yes - You Need a Full Time Scrum Master


Many organizations adopting Scrum ask these questions.

  • Do we need a full time Scrum master for each team?
  • Why do we need a full time Scrum master, can't they do other roles also?

Now allow me to give you the answers: 
  • Yes, you need a full time Scrum Master.
  • Why - watch the video.
Let me explain:

Yes, you need a full time Scrum master, because they will be constantly watching for the actions of the team.  Making sure that the team member are working in flow as often as possible.  This is a full time job.

Why can the scrum master not do other roles on the team? Because of the human ability of selective attention.  First let me show you a video - a little test of your superior ability to follow instructions.  Perhaps you've seen this video - if so, just play along, maybe you will be surprised at how well you do on the test.

The Monkey Business Illusion

Now do you understand why we need a Scrum master watchhttp://www.infoq.com/articles/case-dedicated-scrum-mastering out for impediments all the time.  If they are tasked with doing something else, I'm sure they will miss the obvious impediments the subtle changes in the team members and the environment.

Here is Jeff Sutherland's reasoning (from Scrum Development Yahoo group):
"One of the leading Agile teams in software development asked me how to go hyperproductive. I was their coach as my venture group had invested in them. They had a fuzzy ScrumMaster definition and it was not clear who owned this role. I told them to get a ScrumMaster. The experienced team thought they were better than that and could never go hyperproductive. A new team was formed with a ScrumMaster which immediately went hyperproductive."

"So a lot of teams that think they don't need a ScrumMaster are a long way from 10 times the performance of a waterfall team. This was the design goal for Scrum and every team should be getting a 10% velocity increase sprint to sprint until they hit that number."

"Teams without ScrumMaster's don't do this. Usually they are flatlined and will never reach their full potential."

  --  Jeff Sutherland
Have you heard of the Fleas in the Jar Experiment - watch the video:

Where should Scrum Masters report? - Ryan Dorrell
An analytical approach to the same question:  Scrum Master Allocation: The Case for a Dedicated Scrum Master  by  Melinda Stelzer Jacobson on InfoQ
Can you use a Scrum Master by Bob Marshall the FlowchainSensei
The Scrum Master as the Change Leader by Barry Overeem


1 comment

Most Popular on Agile Complexification Inverter

David's notes on "Drive"

- "The Surprising Truth about what Motivates Us" by Dan Pink.

Amazon book order
What I notice first and really like is the subtle implication in the shadow of the "i" in Drive is a person taking one step in a running motion.  This brings to mind the old saying - "there is no I in TEAM".  There is however a ME in TEAM, and there is an I in DRIVE.  And when one talks about motivating a team or an individual - it all starts with - what's in it for me.

Introduction

Pink starts with an early experiment with monkeys on problem solving.  Seems the monkeys were much better problem solver's than the scientist thought they should be.  This 1949 experiment is explained as the early understanding of motivation.  At the time there were two main drivers of motivation:  biological & external influences.  Harry F. Harlow defines the third drive in a novel theory:  "The performance of the task provided intrinsic reward" (p 3).  This is Dan Pink's M…

Exercise:: Definition of Ready & Done

Assuming you are on a Scrum/Agile software development team, then one of the first 'working agreements' you have created with your team is a 'Definition of Done' - right?



Oh - you don't have a definition of what aspects a user story that is done will exhibit. Well then, you need to create a list of attributes of a done story. One way to do this would be to Google 'definition of done' ... here let me do that for you: http://tinyurl.com/3br9o6n. Then you could just use someone else's definition - there DONE!

But that would be cheating -- right? It is not the artifact - the list of done criteria, that is important for your team - it is the act of doing it for themselves, it is that shared understanding of having a debate over some of the gray areas that create a true working agreement. If some of the team believes that a story being done means that there can be no bugs found in the code - but some believe that there can be some minor issues - well, …

What is your Engagement Model?

What must an Agile Transformation initiative have to be reasonably assured of success?

We "change agents" or Agilist, or Organizational Development peeps, or Trouble Makers, or Agile Coaches have been at this for nearly two decades now... one would think we have some idea of the prerequisites for one of these Transformations to actually occur.  Wonder if eight Agile Coaches in a group could come up with ONE list of necessary and sufficient conditions - an interesting experiment.  Will that list contain an "engagement model"?  I venture to assert that it will not.  When asked very few Agile Coaches, thought leaders, and change agents mention much about employee engagement in their plans, models, and "frameworks".  Stop and ask yourselves ... why?

Now good Organizational Development peeps know this is crucial, so I purposely omitted them from that list to query.

One, central very important aspect of your Agile Transformation will be your Engagement model.  

Refactoring - examples from the book

Martin Fowler's book Refactoring:  Improving the Design of Existing Code has a simple example of a movie rental domain model, which he refactors from a less than ideal object-oriented design to a more robust OO design. Included in this Refactoring_FirstExample.zip Zip file are the Java source code files of the Movie, Rental, and Customer classes. Along with a JUnit CustomerTest class. Using these example source files you too can follow along with the refactoring that Fowler presents in the first few chapters of his book.


Metrics for a Scrum Team (examples)

What metrics do you collect to analyze your scrum team?

We live in a world of data and information.  Some people have a mindset that numbers will diagnose all problems – “just show me the data.”  Therefore many directors and senior managers wish to see some list of metrics that should indicate the productivity and efficiency of the Scrum team.  I personally believe this is something that can be felt, that human intuition is much better in this decision realm than the data that can be collected.  However, one would have to actually spend time and carefully observe the team in action to get this powerful connection to the energy in a high-performing team space.  Few leaders are willing to take this time, they delegate this information synthesis task to managers via the typical report/dashboard request.  Therefore we are asked to collect data, to condense this data into information, all while ignoring the intangible obvious signals (read Honest Signals by Sandy Pentland of MIT).
What if …