Originally posted by william gates:
I think agile works best with smaller teams and with teams that seem to stick around for quite some time.
But many projects I've worked on in the past became nightmares because these large systems built over the years never were documented well, if at all. And when one piece is added to another piece over 10+ years, it suddenly becomes, "where is everything and what does everything do and when there is nobody left who worked on this system it becomes one big nightmare.
It's nice if you or somebody you know built it, but the fact is, IT is about maintaining systems.
I've worked on many projects for different companies where one person was the only one who knew the ins and outs of a system. There used to be more, but they all left and/or were laid off. And this person was a year or two away from retirement. Once the guy was gone, nobody from that company had a clue aboout that system or what it really does, how it works and so on. And it was a mission critical system. There are many large and small companies out there that do this.
But the reality of IT is most people rarely stay at one place for the duration of a system.
And then IT looks like a joke to the business when it takes 6 months for new people to figure out whats going on when the fact is it could have taken a lot less with proper documents.
Yeah many people never read documentation or specs, but that's their fault.
I think agile development is great, but in the long run, if people don't document anything well, IT will look like a joke to those hiring, firing, and putting out the money.