Scrum is Hard! (Scrum is fun!)

This content is syndicated from LeanAgileTraining by Joe Little. To view the original post in full, click here.

The classic phrase from Sutherland and Schwaber is: Scrum is simple, but Scrum is hard.

And yet, with almost any decent Team, Scrum is fun. Unless the personal chemistry is dysfunctional.

So: If I don’t warn you  that Scrum is Hard, I am lying.

But if I don’t ‘warn’ you that Scrum will be fun, I am also lying.

OK, but why is Scrum hard?  Here are a few reasons. There are other ways to put it. And probably other reasons.

1. A person does not want to admit that he is imperfect.

Very common, right? And understandable. So, when you see and talk about imperfections, find some way not to let people get defensive.

2. People don’t like to admit that ‘we’ are imperfect.

From a certain point of view, this is silly. But it is also how humans are. We don’t like to ‘air our dirty linen’ we sometimes say.

So, this can be a hard thing to change. Again, a lot of it is how we talk about it. So, one cliche is that we phrase it as ‘opportunities for improvement’.  Sometimes very useful.

The key here: Scrum makes obvious lots of personal, team and organizational ‘problems’ or impediments. Makes them very obvious. And some people find this very very hard. And for us Scrum guys, getting those people not to make a mess can be very hard.

3. Change

Scrum is a change. And Scrum demands more changes.

And any change is often hard. You surely have experienced this many times personally.

Now, for a given person, some changes are felt as good. So, not everyone every day will find that changes of Scrum hard. But almost always someone, to some degree finds ‘the change’ hard.

Be sympathetic, to some degree. Bend them, but don’t break them. The next key statement is: Most people don’t resist change, they resist most being changed (by you).

4. Pressure or Stress

Our business of new product development is, by its nature, somewhat stressful.

New products MUST be built ‘quickly’ or ‘on time’.  Time, and quickly delivery are fundamental.

In the old waterfall way, the stress was ‘controlled’ a certain way.  Usually low for a long time, and then very high at the end.  Typically.  In Scrum, the stress is continual, all along the way.

Some people think Sprint means that stress is too HIGH every sprint. (That is not what the word was meant to convey.)

Really, with Scrum the Team is supposed to have ‘positive’ stress (you can google that is you don’t know the concept). And bad stress is supposed to be eliminated. But life is never quite that simple.

So, as you introduce Scrum, you must actively manage that they understand and execute on the ‘stress’ ideas in the proper way.  Much too often, ‘Scrum’ is used to just beat up on the Team continually.  (Or at least that’s how they hear it.)  In many ways, Scrum was designed to SAVE the Team from the Death March. So this ‘beating up’ is rather ironic.

But also ironic is the notion that the Team with Scrum should have zero stress. That time magically has no importance suddenly. This is of course not true. The full team is faced with the business problem of delivering something useful in a reasonable time.  They may or may not be able to do it in a specific situation (eg, company and product), but that fundamental pressure is unavoidable in our business.

5, People Types

A few Myers-Briggs types will find Scrum ‘uncomfortable’ or hard.

Those types may have been fairly satisfied (even if unproductive) in the ‘regularity’ and ‘control’ of waterfall. But Scrum exposes that our business actually has a fair amount of ‘chaos’.  Makes that much more obvious.  And a small percentage of people will find this too uncomfortable for their Type.

In the long term, this is a good thing.  People get reallocated to work that suits them better. But in the short term, it can be hard.

6. Skill Development Feels Endless

We know from any sport that even for ‘simple’ sports it takes years to develop into a true professional.

Scrum, in a similar way, exposes that development into a professional product development person (whether business or technology side) takes time.

And learning and playing the simple sport of Scrum takes years to master as well. Years. Years of hard practice. And this realization can be discomforting to some.

In truth, this was always true in a way. But waterfall kind of hid this truth to a fair degree. And one could feel ‘advanced’ much sooner. It was an illusion, but it seemed to be true then.

So, while this can seem hard, I am not convinced that it is really hard.

But you have seen already that almost all of what I have called ‘hard’ is mainly inside the heads of people. It is not ‘externally’ hard (mostly), but rather internally hard. Or subjectively hard.

7. Impediment Removal

Getting groups of people to remove impediments often feels very very hard.

And it is. All work in life is hard in some sense. And when we are inexpert at some things, they definitely feel very hard at first.

But with impediments, we tyoically also must get other people to ‘assist’ or go along in some way. And that can be very very hard.

Very useful, but very hard.

***

So, there are a few ‘hard’ things about Scrum.

I would be interested in your thoughts on why Scrum is hard.  I have not used the word ‘culture’ yet, and expect some of you to use it.

Leave a Reply

What is 8 + 2 ?
Please leave these two fields as-is:
Please do this simple sum so I know you are human:)

There are 101 ways to approach anything.
To find the best way, sometimes you need expert help

What People Say

“Kelly revolutionised the way our digital department operated. A true advocate of agile principles, he quickly improved internal communication within our teams and our internal clients by aligning our business and creating a much enhanced sense of transparency in the decisions the business was making. Kelly also introduced a higher sense of empowerment to the development teams...”

PETER SILVA-JANKOWSKI
IPC MEDIA

“Kelly’s a leading program director with the ability to take charge from day one and keep strong momentum at both a program and project level driving prioritisation, resourcing and budgeting agendas. Kelly operates with an easy-going style and possesses a strong facilitation skill set. From my 5 months experience working with Kelly, I would recommend Kelly to program manage large scale, complex, cross company change programs both from a business and IT perspective.”

LUKE SHARKEY /STRATEGY & IMPLEMENTATION LEADER
SUNCORP

“Kelly is an extremely talented and visionary leader. As such he manages to inspire all around him to achieve their best. He is passionate about agile and has a wealth of experience to bring to bear in this area. If you're 'lucky' he might even tell you all about his agile blog. Above all this, Kelly is great fun to work with. He is always relaxed and never gets stressed - and trust me, he had plenty of opportunity here! If you get the chance to work with Kelly, don't pass it up.”

GILES BENTLEY, DEVELOPMENT & OPERATIONS DIRECTOR
TIME INC

“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”

DAN PULHAM, DIGITAL DIRECTOR
TELSTRA

“Kelly and I worked together on a very large project trying to secure a new Insurer client. Kelly had fantastic commercial awareness as well as his technical expertise. Without him I would never had secured this client so I owe a lot to him. He is also a really great guy!”

GINA MILLARD
GLASS'S INFORMATION SERVICES

“Kelly came to the department and has really made a huge impact on how the department communicates, collaborates and generally gets things done. We were already developing in an agile way, but Kelly has brought us even more into alignment with agile and scrum best practices, being eager to share information and willing to work with us to change our processes rather than dictate how things must be done. He is highly knowledgable about agile development (as his active blog proves) but his blog won't show what a friendly and knowledgeable guy he is. I highly recommend Kelly to anyone looking for a CTO or a seminar on agile/scrum practices - you won't be disappointed!”

ANDY JEFFRIES/TECHNICAL LEAD
IPC MEDIA

“Kelly was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”

HANNAH JOYCE
GLASS'S INFORMATION SERVICES

“Kelly was engaged as a Program Director on a complex business and technology transformation program for Suncorp Commercial Insurance. Kelly drew on his key capabilities and depth of experience to bring together disparate parties in a harmonised way, ensuring the initiate and concept phases of the program were understood and well formulated. Excellent outcome in a very short time frame. ”

BRUCE WEIR/EGM
SUNCORP

“I worked with Kelly on many projects at IPC and I was always impressed with his approach to all of them, always ensuring the most commercially viable route was taken. He is great at managing relationships and it was always a pleasure working with him.”

BEATRIZ MONTOYA/CONSUMER MARKETING DIRECTOR
IPC MEDIA

“I worked with Kelly whilst at Thoughtworks and found him to be a most inspiring individual, his common-sense approach coupled with a deep understanding of Agile and business makes him an invaluable asset to any organisation. I can't recommend Kelly enough.”

PETER THATCHER, SENIOR ACCOUNT DIRECTOR
ThoughtWorks

“Kelly was a brilliant CTO and a great support to me in the time we worked together. I owe Kelly a great deal in terms of direction and how to get things done under sometimes difficult circumstances. Thanks Kelly.”

JULIE PEEL
GLASS'S INFORMATION SERVICES