Get certified - Transform your world of work today


Enthralling Einstein

"I never teach my pupils. I only attempt to provide the conditions in which they can learn.ΓÇ¥

17 December 2010

Enthralling Einstein: "I never teach my pupils. I only attempt to provide the conditions in which they can learn.”

Einstein was a Scrum pioneer; look at his quotes and see how they all included messages from the Agile Manifesto or Scrum process & philosophy

“I never teach my pupils. I only attempt to provide the conditions in which they can learn.”
This quote relates to self-managed teams and empowered individuals. People tend to learn more when they discover things themselves instead of being dictated on how to do or interpret something.
And a self managed team is one of the cornerstones of the Scrum framework. In more traditional environments there is usually a clear chain of command in which:
  • Top management defines the Why & What (mission, objectives)
  • The middle management then decides Who of their team will do it and by When it will be ready. (projects, tasks)
  • Typically middle management also tells their team How to do it; or corporate rules prescribe How things should be done (guidelines, procedures)
This doesn’t create an innovative & challenging environment for the team members. With Scrum you can turn this situation around and build a healthy & pleasant environment in which team members are happy to work in and are invited to learn and find out their own solutions to issues. In Scrum,
  • The product owner (which can be top management) still defines the What & Why of things to be done
  • It is also the product owner who defines to urgency / importance of a story; via the business priority.
  • Using planning poker or any other estimation technique, the team implicitly determines the timing of when the stories will be delivered. On top of this, the team also decides Who will do it.
  • And it’s also the team who decides How to execute / deliver a story / task.
The table below scores the decision power on the five key topics of getting things done (Why, What, When, Who, How). It’s clear that in more traditional environments teams have, most of the time, no empowerment to decide anything. While in Scrum the distribution of decision power is much more evenly distributed (this actually creates a much healthier working environment)
Empowerment Index
And what about the middle management in Scrum?
Well, they become the “Einstein teachers”.
They will be responsible of creating these conditions for their teams, helping the team finding solutions, coaching them to take up responsibility, removing impediments and guarding the Scrum process. Actually they’ll become the ScrumMaster ‘Plus’ (because the management tasks in big corporations extend the role of ScrumMaster: HR, Corporate governance, team budgeting, …)

Opinions represent those of the author and not of Scrum Alliance. The sharing of member-contributed content on this site does not imply endorsement of specific Scrum methods or practices beyond those taught by Scrum Alliance Certified Trainers and Coaches.

Article Rating

Current rating: 0 (0 ratings)


Mike Self, CSM, 12/22/2010 10:12:43 AM
We just started Scrum/Agile this year. I've read a lot of articles about Scrum conerning how the team sets the date. What I don't see a lot about is mandated dates. Our business interacts with the federal government and our own association. The majority of projects' implementation dates are dictated by outside entities. We're simply told, 'the project has to go in on -----'. I'm curious how other scrum teams deal with it or if they even can deal with it? Thanks, Mike
Jan Van den Nieuwenhof, CSM, 12/29/2010 2:10:28 AM
It's probably not only a Scrum related question but a general project management topic about the triple constraint (scope-budget-time). What I tell my stakeholders is that they can pick 2 to fix and 1 to be variable. In Scrum, it's usually the scope that is the variable. You deliver the project within budget and time, but with a variable scope.

You must Login or Signup to comment.

The community welcomes feedback that is constructive and supportive, in the spirit of better understanding and implementation of Scrum.


Newsletter Sign-Up