Why Scrum? Why Agile? CEO Elevator Pitch

The second instalment of why Scrum, why Agile? What to say to a CEO...

“What do you want?”

“I have an idea that could be valuable to the company.”

“You have 60 seconds”


“We have a lot of people working on the product, but [enter employee survey here] shows that they are unhappy. They are also very clever, yet [some percentage of projects - usually ½ to ⅔] of our projects are failing - costing us a lot of money and frustration. Moreover [some big competitor] are moving faster than we are. Many of our people don't know who they create value for or why.


“This is caused by our big plans and need to control the process.


“We could take a small, self-organizing team, with all the necessary skills and permissions, and start releasing customer value early and often. It’s called Scrum - I’ve seen it work at a start-up but it also saved [some competitor] from going under.”


“What’s in it for us? Sounds like we would lose control”


“Scrum would at least show up our dysfunctions transparently and early - better to know we have no control than to have highly controlled, failing projects.”

“Hmm, ok - what if it fails?”

“Well, that’s the charm - you can see success or failing, every few weeks. If you don’t like what you see, you can pull the plug.”

“If we do this - what do you need from me?”

“We need:
  • A project/product/goal
  • A dedicated team - containing one person representing you and a few people with all the skills, tools and permissions to make the product.
  • Your presence at the same time and place every few weeks so you can give this some short but focussed attention.”


    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

    How a yacht race turned me into a Scrum Master

    Image
    Continuous Improvement, Autonomy, Validation - these terms are becoming so worn that they feel like business jargon. But if you have experienced the pain that Stagnation, Command & Control and Big Bang Deployment brings, you have ample reason not to look back.  The mild embarrassment that comes with joining the 'Agile cult' is greatly outweighed by the soul-numbing awfulness that is the alternative. Although the above is my experience too, this is not that story.  I have also had experiences with Chaos - the inferno that regularly erupts in Startupland and in many Open Source projects.  It, not Agile, is the real antithesis to the frozen hell that is Waterfall / Taylorism / TheoryX .  This is not that story either.  I actually started appreciating what I now call the Agile mindset, on a sailing boat. 
    Read more