Why Scrum? Why Agile? Answering a Project Manager


I'm a Project Manager, how will we organize projects with Scrum?


Scrum has no Project Managers. Projects are generally only focussed on developing something, whereas Scrum Teams design, create and sustain something. Managers are generally responsible for something or some people, whereas Scrum Teams are self-organizing.


In Scrum - as long as a product exists, it has a Product Backlog of everything that will be done to it. That includes, but is not limited to what can be termed 'projects', however it is ordered so that working on it, produces the maximum amount of value, first.


In project management, value is assumed to be a function of the 'iron triangle' - this budget, spent in this time, with this scope of solutions will make the project done. Quality is a cost to these variables: running out of time or money whilst still making the same scope will lead to reducing the quality. This is working ‘inside out’ - from what we can make, towards value for customers.


Scrum turns this 'outside in': the Scrum Team aims to continuously add maximum value for its customers. It does this by adding high quality work to the increment at least every sprint, ensured by a transparent definition of "Done".



Instead of predicting scope, the team selects what it will make every Sprint in a Sprint Backlog and defines a Sprint Goal. The Scrum Team learns how to add value empirically by inspecting and adapting the increment, how they create the increment, and their daily progress towards the Sprint goal.

The Product Backlog is also continuously inspected and adapted so that it is possible to forecast how many time-boxed Sprints, so how much time and money will be needed in the future.

So Scrum relies on self-organization and not organization by managers. However, empowerment to remove impediments to customer focus, self-organization, and a healthy system, are required. Consider becoming a Product Owner or a Scrum Master. Otherwise, support the Scrum Team by opening the space they work in, as an agile leader.


Thanks to:
  • https://scrum.org
  • http://professionalscrumtrainer.com/
  • https://valueminds.nl
  • https://scrumguides.org
  • https://agilemanifesto.org

Comments

Post a Comment

Popular posts from this blog

Agile after Corona

Image
The Company to Consumer model under threat teambrunel.com Originally I became interested in agile software development when I started to discover a pattern between great teamwork in yacht racing and teams that produced software.  Some of the greatest software teams that I worked with were people working together on open source projects. Thousands of people worked together in self-organizing teams throughout their technology stack, much as if they had belonged to a single organization.  Could that model work in more organizations? There was an essential thing missing though - most of these teams were making things that were useful to themselves but not necessarily to a user who would be willing to pay.  Motivation was often very idealistic: working on free (as in liberty) software usually entailed working for free (as in beer).  Some projects became wildly successful, imagine a world without Linux , Wikipedia or Bitcoin .  But do you remember Joomla , Mutuala or Erpal ? It was
Read more

Deep Democracy meets Scrum

Image
About a year ago, I went to a training given by Sandra Bouckaert and Lydie van de Laar on the basics of Deep Democracy .  My wife was 35 weeks pregnant and I was working on a project with worryingly limited financing so I was not exactly in the perfect 'zen' mindset for a day of mind-battering brainstorming.  I expected to leave the day dazed and confused, yet found myself in the car buoyed up and even excited about what I had just experienced. Deep Democracy is a method developed in South Africa at the end of the apartheid regime and specializes in getting minority views heard.  It is concurrently a team-building tool and an ideation tool. 
Read more

Agile is dead - Zombies vs Robots

Image
 Agile (a.k.a. the agile industrial complex) is dead (or dying, or undead... read on). Of course Agile has been declared dead many times, but now we can see that there are fewer visitors to Agile conferences, fewer people looking to get certified as something Agile, fewer people are calling themselves Agile Coach. Dying The Agile conferences have talks about how very large companies do Agile, which tools they use to collaborate or how non-IT departments do Agile, topics that were also there ten years ago. Agile conferences have yet to adapt to topics like decentralized enterprises, fluid teams, remote-only organizations, AI helpers and commons governance. The certification crisis seems to follow a similar pattern: was this ever a good measure? Those courses were meant for setting off down a path that makes you better at discovering and uncovering effective ways of working - perhaps we're running out of people who have yet to start, whilst not offering enough to th
Read more