> We try to use it to do Extreme Programming in a modern language to ship new product updates in less than a week I always find these kinds of comments interes

> We try to use it to do Extreme Programming in a modern language to ship new product updates in less than a week I always find these kinds of comments interesting (and I realise that you were not suggesting trying to do this is a good idea). XP has sprints. I have never found a way to make sprints less than 2 weeks and actually have them work well. Whenever anyone has wandered onto my team and assured me that they can do 1 week sprints, I've found that they don't actually do everything that is required for XP to be successful (like planning game, prioritisation meetings, understanding the acceptance criteria for a story before you put it in a sprint, etc, etc, etc). For me 1 week XP sprints are the holy grail: something you covet, but which is unattainable and leads you on a bloody journey of despair if you try to get it ;-) My own personal opinion is that XP and continuous deployment don't even work particularly well because you can't do true continuous integration (i.e. trunk based development where you are integrating everybody's changes every 5-20 minutes) and maintain a completely sound development structure. That's one of the reasons for sprints: to allow yourself to break stuff for a while and then ensure that it's all working by the end of the sprint. It's not just XP where I find this. Most of the time, I find that the most popular variant of anything just doesn't work at all: because the "30 minute meal" is full of compromise. It doesn't matter how many times Jamie Oliver says that it's "lovely" and "rustic" -- it's soggy lettuce with completely random salad dressing that you whirred up in your blender. Ha ha... so many nonsequitors. I hope that made some sense... Time for coffee...