Agile & Religion – 1

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

I heard recently someone comment: "Well, watch out for those guys who get too religious about Agile. We don't want that around here."

This general topic gets talked about in the Agile community a lot. And, I think, often ineffectively.

But I think it is a difficult topic. It is hard to explain the issues around this well.

So, I will try to do several posts with specific examples and situations.

The first thing to say is that lean-agile-scrum is mainly about results. Results for the individual, the team, and the customers. Results such as: better products, higher quality, more fun, better work.

It is not about doing Scrum just for the sake of doing it. As though purity of Scrum, alone, were a high value.

It is important to say that virtually all the people who are experienced with lean-agile-scrum are concerned that they see too many people doing it "weakly". Schwaber talks about 'flaccid Scrum'. The XP guys talk about how Scrummers don't have strong engineering practices. Others talk about ScrumBut (or ScrumButt). And there are other phrases.

What is important is that they have a sense that playing Scrum 'weakly' means that the people are getting FAR less of the value than they deserve.

In summary for now: lean-agile-scrum is not about religion or belief or faith. It is about reality and testing and real results. That seems to me to be pretty far from 'religion' as most people use that word (when they use it as a put-down).

The next thing to say is: when a Scrum advocate talks about doing Scrum better, we should talk more about WHY 'better Scrum' means a better life or better results. More on this in the next post.

3 Responses to “Agile & Religion – 1”

  1. DTinsley says:

    I feel that in an effort to start Agile slowly at organizations we are giving people a watered down version of Agile. The disciplined practices never develop fully. I have been in situations where a few team members wanted to start using scrum but the organization as a whole didn’t know what scrum was. They are not wanting and they are not asking for it. The agile advocates can seem like zealots to those without knowledge or experience with agile. I have struggled with this type of situation a couple of times. They only answer I could find is to work on making my self as agile as I can within the current working environment but accept that the organization is not asking or wanting Agile. Finish the project and look for a agile environment to work in. Watered down agile makes no one happy. Management can’t see the fruit produced because things never get past baby steps and the developer never get the benefits of working on a scrum project. I am glad you posted this article. It has helped me make a decision. Trying to plant seeds of Agile in hard rocky ground is not the best use of resources.

  2. Alex B says:

    I think is quite a challenge to adopt agile in large companies with multiple development streams as agility involves collaboration and change, and the biggest challenge I see is not adopting and practicing scrum at team level but being agile at a larger scale; teams and development synchronization, development and infrastructure synchronization most of the time struggle to function.

  3. Alex B says:

    … and further on I believe religion is a word that should not enter in technology as in the situation it traditionally got used lead us through inquisition and mass brainwash :)

Leave a Reply

What is 3 + 7 ?
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...”


“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.”


“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.”


“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.”


“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!”


“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!”


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


“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. ”


“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.”


“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.”


“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.”