Don’t worry: I am not going to jump on the “agile is dead and a failure” bandwagon. I do not want you to stop working with Scrum. I just want you to stop starting with it.
A lot of companies realize something’s got to change in order to survive. Especially software development departments feel the need to be more flexible and innovative in order to keep up with a rapidly changing world. We’ve been promised that an agile framework like Scrum will do just that.
Often the larger agile transitions are primarily focused on the Scrum aspect. Development teams are doing everything by the Scrum guide, but things don’t seem to go as the book described it. Many times it is an isolated implementation that is started on, limited to the development department.
Crap in, crap out
All the while the input – or requirements – stays just as it has been the past decades: not prioritized, a lot of demands for per-customer customization, and lacking a clear vision. Yet this is where you should start: sort out the input. After that the implementation on a team level will be much easier and more meaningful.
There needs to be a concise and clear business case, which results in a vision of the product. The impact that the product needs to have must be clear. ROI needs to be validated with stakeholders. Only after these the roadmaps, epics, features and story maps can be made. And when they are done they need to be revalidated. Make no mistake about the amounts of time this will take: it will be substantial. But all that is logical, since this is the hardest part.
Even if gathering the input is the only action taken you will still have gained a lot. With a better quality of input the product stands a much higher chance to be better. Whether by Scrum or Waterfall. Yes, Waterfall.
There is a theory that Scrum will have a butterfly effect on organizations; that when a single team starts the rest of the company will see the benefits and follow. Everyone will become agile and focus on business value. Well yes, sometimes that’s the case. In most cases however, starting with Scrum on a development team level is not going to bring you more than frustrated isolated development teams, because the agile promise isn’t coming true. Agile was supposed to be more fun, software would be better and customers would be delighted.
Source: Screenshot from https://www.youtube.com/watch?v=nHFgCW1lCmM
The rest of the organization is as frustrated as ever, because the development teams can’t be bothered to deliver on time: “deadlines are a thing of the past, and just not agile”. The gap between business and IT that we were supposed to bridge with agile is now even bigger than it was.
Fulfill the promise
So in order to fulfill this agile promise – which is not necessarily dead, as some may say – we need to stop starting with Scrum.
Impact mapping and continuous validation
There is always a reason for making software. Let’s rephrase that: there should always be a reason, at least from a business perspective. How else could our products have any impact? Whether we want to make an app that that seamlessly connects riders...
- Open Source
- Agile methods
25.11.2015 | 3 Minuten Lesezeit
Continuous Validation: Meet Gareth. He is seriously unpleasant.
Hello world, please meet Gareth. He can be seriously unpleasant. Trust me, we know. But he is becoming more and more indispensable. He will tell you clearly, without emotions, when your ideas are rubbish. He will certainly not hold back and he will give...
15.9.2015 | 3 Minuten Lesezeit
After continuous integration there is continuous validation
It’s a funny thing to say that delivering business value is the most important thing when developing software. It doesn’t matter that a framework like Scrum is far from efficient, because we focus on value. We deliver business value. Working software...
- Software development
23.8.2015 | 3 Minuten Lesezeit
How assumptions are not the mother of all f-ups
The thing about trends is that they will come and they will go. So after the agile trend continuous delivery and devops are in line. I think in a way it is very nice to see that development craftsmanship practices are becoming more and more accepted....
13.7.2015 | 5 Minuten Lesezeit
DevOps, building on quicksand?
The management decides they want DevOps and Continuous Delivery. It is faster, cheaper and there are less people needed for the same work. So now DevOps and CD are set as goal for the whole company to reach in the near future. So basically engineering...
24.7.2014 | 4 Minuten Lesezeit
DevOps and Product Ownership
[This article was co-written by Miel Donkers and Niels Talens.] You could see DevOps as expanding the mindset, toolset and processes which started with Agile. Where Agile focuses on creating maximum business value as soon as possible, DevOps can help...
17.7.2014 | 7 Minuten Lesezeit
It’s all about the input
Garbage in, garbage out This is a pretty basic principle. But what do you expect? What are the odds that if you give poor descriptions of your vision and needs that the results will be as expected? 50/50? Maybe less? Within the agile community there...
7.3.2013 | 6 Minuten Lesezeit
A man went to the doctor…
“Hello Doctor, I have epicondylitis lateralis and I think we can fix that with Shockwave. Shockwave is a brand new treatment that is faster, cheaper and better than all the other methods. Everyone I know does it. Don’t bother looking that up for I’...
9.11.2012 | 2 Minuten Lesezeit
Velocity is not for you
A while ago someone told me they let their product owners participate in estimations. And I don’t mean watch how the team estimates but really estimating stories. I’ve heard about non-programming scrum master, projectmanagers, salespeople and architects...
- Agile methods
- Software development
7.10.2012 | 2 Minuten Lesezeit
RST Testing Training – James vs. Michael
I was thinking to get James Bach to the Netherlands because he has an interesting view on testing. I read a couple of the books he wrote, watched a presentation from him on video . I thought he has a lot to tell. Beginning of this year a new colleague...
22.6.2012 | 4 Minuten Lesezeit
Lean specifications, what’s that?
A lot of teams are changing to Agile. Usually they start bottom up with a development focus on getting agile. The testing is often late in the change process and testers are not that keen on this new process. This is quite logical testers don’t change...
6.9.2011 | 2 Minuten Lesezeit
Lean bells ringing at the hospital
Last week I was working at my house together with my father and we removed a wall to create a bigger room for the upcoming baby. While the last stone was removed he damaged his thumb quite badly. We needed to go to the hospital. As soon as we arrived...
18.6.2011 | 4 Minuten Lesezeit
Dein Job bei codecentric?
Agile Developer & Consultant (w/d/m)
An allen Standorten
Gemeinsam bessere Projekte umsetzen.
Wir helfen Deinem Unternehmen.
Du stehst vor einer großen IT-Herausforderung? Wir sorgen für eine maßgeschneiderte Unterstützung. Informiere dich jetzt.
Hilf uns, noch besser zu werden.
Wir sind immer auf der Suche nach neuen Talenten. Auch für dich ist die passende Stelle dabei.
Do you still have questions? Just send me a message.