eXtreme Programming Is Not Agile!

In the course of my blogging, I’ve often come across comments or other bloggers talking about XP (eXtreme Programming) as though it *is* agile.

Truth is, XP is Agile, but Agile is not XP…

Although I like a lot of the concepts in eXtreme Programming, whether or not you use XP practices does not define whether or not you are doing agile development.

It’s quite feasible that you’re not doing Test Driven Development. That you’re not doing Automated Unit Testing. That you’re not doing Pair Programming. And that you’re absolutely doing agile development.

Agile development is a set of values and principles. And eXtreme Programming is just one of the agile methodologies that supports these principles.

People using Scrum are doing agile. People using DSDM are doing agile. People using ‘home-made’ forms of iterative, incremental, collaborative development are doing agile. To a greater or lesser extent, I admit, and with a different emphasis. But they are certainly ‘doing agile’.

eXtreme Programming, whilst one of the more popular forms of agile development, is only one form of agile development. And as it’s name suggests, it is probably the most extreme. ‘Milder’ forms of agile can be equally beneficial, and should not be dismissed as ‘not agile’.


Photo by grisei

7 Responses to “eXtreme Programming Is Not Agile!”

  1. Hans-Eric Grönlund says:

    Wow, you almost got me upset there for a while, but after reading the article I have to agree with you. The title fooled me big time though. :-)

  2. Matt M says:

    I think the problem is your title is logically incorrect. It can be more clearly stated as, XP is an Agile method. XP is Agile. XP provides sufficient conditions to meet the definition of Agile.

    Your point-
    Agile methods are not limited to XP. Hence, Agile is not XP. The conditions of XP are not necessary conditions of an Agile method.

    In the short form XP provides sufficient, but not necessary, conditions for an Agile method.

    I think the more interesting point is why people are so disappointed with Agile methods that don’t feature aspects of XP. There is so much wisdom in Mr. Beck’s book that is extremely powerful in improving software projects, that it was a prime mover in driving Agile adoption. Other methods, such as Scrum, that don’t address these practices should often be supplemented with things like continuous integration, 10 minute builds, etc. or they will be missing out on a lot of opportunity for awesome performance.

    So, I think the real heart of the issue is not that practices which aren’t XP aren’t agile, and no one with any sense would say that, but rather that projects using other processes would often be well served to adopt as much of XP as they can.

  3. Kelly Waters says:

    I know the title is logically incorrect btw; I was just being provocative :-)

    Many thanks for your comments though Matt. You speak sense…


  4. ash says:

    I agree completely. In fact I have written a couple of posts about Kanban. The case study that is the subject of the posts seemed to some to be very non-agile in the sort of confused sense mentioned in your post. But from another perspective it seemed very agile. Have a read of this if you’re interested. http://witi-work.blogspot.com/2008/04/agile-and-orthodoxy.html

  5. Godzhesas says:

    Title is very provocative, when i saw it i was about to jump straight to the comments :) i love XP because we use it in our company, we use SCRUM by the way too, though i agree that it is just one of the many Agile processes.

  6. awahid says:

    The title should be "XP is Agile, but Agile is not XP".
    I think everybody would agree on this statement There are various other methodologies which are agile but not XP eg:
    1) Scrum
    2) Feature-Driven Development (FDD)
    3) Crystal methodologies
    4) Dynamic Systems Development Method (DSDM) and Atern
    5) Adaptive Software Development (ASD)
    6) Lean

    XP is one of the methodology in Agile software development.

  7. Jill says:

    It’s not “provocative”. It’s false, and the second sentence states exactly the opposite of the title. This is the very definition of linkbait. The title is a lie designed to draw in readers.

    You might as well use a title like “The President Has Been Shot!”, and then in your introductory paragraph say “The president, of course, has not been shot. But now that I have your attention…”

    You are what is wrong with the internet today. (Quick quiz: is that statement true, false, or “provocative”?)

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


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