Rejecting CDD

One of the 12 agile principles is:

“Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.”

Indefinitely. Wow, that’s a long time!* How will we ever know if we’ve delivered on this principle? Well, we won’t. We’ll only know when we fail to deliver – when team members burn out. When it’s too late.

So, take a look a yourself and your team. How important is that first coffee in the morning? Or the second? Agilista, meet barista.

The first step in treating any addiction is to admit that it exists. You might not need that caffeine. Remember the manifesto – agile processes promote sustainable pace.

Practice what you preach and consider saying “No” to Caffeine Driven Development.

Coffee – Stupid

* With thanks to Douglas Adams: “Space is big. Really big. You just won’t believe how vastly, hugely, mindbogglingly big it is. I mean, you may think it’s a long way down the road to the chemist’s, but that’s just peanuts to space, listen…”






2 responses to “Rejecting CDD”

  1. Neil Menzies Avatar
    Neil Menzies

    But… XP principles mean you take the things that are good and do them to extremes… and coffee is good!

    So the real answer should be to drink extreme amounts of coffee.

    So we’ve got BDD, CDD and DDD is there an ADD to start the list?

    1. Seb Rose Avatar

      I’m not sure which XP principle encourages you to take things to extremes: Maybe it shouldn’t have been called Extreme Programming at all, but it seems a bit pointless to complain now.

      As for ADD, I can think of a few candidates for ‘A’ right now, but I wouldn’t want to publish them on a professional blog 😉

Leave a Reply

Your email address will not be published. Required fields are marked *