September 27, 2004
The downside to Agile
A client recently emailed (quote included here with his permission):
> It's funny but I think I can only work on Agile/XP projects now. I don't think I can "go back" to the old way. Thanks for the brain washing......
This got me thinking. I feel the same, and have done since soon after I got into XP in 1999. I've heard lots of people say the same over the last few years.
This causes a problem. Once converted to Agile/XP, you'll be dissatisfied if you have to work on a non-Agile project. Currently only a minority of jobs are working on Agile/XP projects, so if you want to be happy in your work your job opportunities become more limited once you've worked on an Agile/XP project.
Fortunately, Agile/XP projects are becoming more common now, so the situation for converts is improving.
Through careful selection of employer, and plenty of good fortune, I haven't had to "go back" to the old way and hope I never do.
Posted by ivan at September 27, 2004 2:37 PM
Copyright (c) 2004-2008 Ivan Moore
Sad but true, I have to adjust to write code on my own nowadays.
It's quite a revelation doing an XP "conversion" and watching the team just light up when it's succesful. It's like an oppresive weight of guilt and responsibility has been lifted from their shoulders.
I have this pattern but I seem also to have what I call the "Return of the King" pattern.
Elrond: I give hope to men.
Aragorn: I keep none for myself.
Even hearing about waterfall projects upsets me now:
There's plenty of agility for the company, but I don't see much agility in XP for the employee. It pretty much limits you to on-site working in rigid hours. The company may well get it's truck number down to zero, but I doubt there'd be a great hurry to reduce notice periods... Apart from letting us get our work done without stress and blame, I don't see developers getting much flexibility out of XP.