Agile Adoption Story – Common Mistakes (part 6)

And finally, to finish the agile adoption story, even though the team is after all able to find their way to communicate, share knowhow, learn from each other, and cooperate, there is another obstacle. Surprisingly it’s not outside the company but in the business unit internally.

Company doesn’t need to change

The company doesn’t need any change. It used to be working good for many years, and if we had observed any problems, they were indeed located in the ICT, so why should we change the business unit? Isn’t Scrum called software development methodology?

Oh, yes, Scrum is business driven, but here are the requirements, so take them as they are and if you need to make any User Stories out of them, sure, feel free to do it. But we are not really interested in your internal processes so don’t bother us. However, we expect you to finish all this work on time.

So the teams are desperate again. Unless they got Product Owner, who is willing to become part of their team, and share the risk and success with them, they can’t proceed with real Scrum. They can’t take all responsibility and gain success in return.

Unfortunately, some get frustrated from the lack of business support and still complaining “Agile is not for us”. We are different, we have too complex product, we are too big/small to implement agile. Our customers are like this and that, and you know, agile is great, just for a different company.


The Great ScrumMaster: #ScrumMasterWay bookLearn more about transforming organisations, leadership and culture with the Agile & Enterprise Coaching.Check our Scrum and Agile training sessions on Sochova.com.Grab a copy of The Great ScrumMaster: #ScrumMasterWay book.


2 thoughts on “Agile Adoption Story – Common Mistakes (part 6)”

  1. So I’m surprised to not see “team does not adopt engineering practices and rots under a pile of technical debt”. Isn’t that a common mistake too?

Comments are closed.