© Scott S. Nelson
© Scott S. Nelson
I’m on a roll with the LinkedIn rants today 🙂
Do software development efforts fail because: 1) the technical staff is not skilled enough for the work, 2) management has unrealistic expectations, 3) lack of reasonable resources to perform the effort. I would be interested to know your thoughts.
Someone once said that failure can only occur when time and resources are limiting factors. In the case of software, all of the above are true, though the most consistent cause I see is that the process of doing the following in order:
1) Set a completion date
2) Define the requirements
3) Design the software
4) Develop the software
5) Change the requirements
6) Wonder what went wrong
Agile is a good step in preventing failure from the above process except that even shops that use Agile often face that the end date is set before work begins and that unrealistic expectations are set at the same time.
Another ongoing issue is that management’s reaction to bad news about meeting functionality or a date is to throw more people on the project and demand more frequent meetings which pull the people most capable of solving the issue away from solving the issue. This trains developers to not communicate issues until the last minute, which accelerates this vicious cycle.
As Dennis Miller used to say “But that’s just my opinion. I could be wrong”
I have to point to this just for the title: Never Eat Anything Bigger Than Your Head. Just wish I could remember where I first heard that phrase…
Anyway, it is a good post about sizing stories in Agile.
As the author notes, on boarding is costly in Agile. He presents a nice template to reduce that cost at http://www.the-arm.com/2009/05/project-standards/