The major software methodology wars since the mid 1950’s. Someone was wrong on the Internet, so here we go… In a recent HBR article, It’s Time to End the Battle Between Waterfall and Agile , the author sets up a false premise: There is a war between Waterfall methodology and Agile. The war must end. And finally, you can combine the approaches to get the best of both worlds. This sounds good, but the article is based on a misunderstanding of both Waterfall and Agile. Also, there is no war between Waterfall methodology and Agile. There can’t be, because Waterfall methodology does not exist! Waterfall is a name for large projects that failed in the 1960’s. Waterfall was never a methodology, but a failure to apply the methodologies that existed back then. As I will show towards the end of this article, at least one of the “successful” Waterfall projects mentioned in the HBR article was neither successful, nor a Waterfall project. I got invaluable help from Alistair Cockburn. He fact che...
It is performance evaluation time in many companies. This can be stressful, both to the people being evaluated, and the people doing the evaluation. In companies adopting agile software development methods, the tension can be extraordinary. Individual performance evaluations run counter to agile philosophy, which emphasizes team performance over individual performance. However, managers and corporate leaders need to take a few steps back, and consider the impact performance evaluations have on the organization as a whole. Especially now, in the midst of a recession, it is important to look at a companies current policies to see if they can be improved, or if they are actually holding the company back. So, how can a manager evaluate policy? Performance evaluation policies can serve as an excellent example. I'll confine myself to discussing the so-called ‘rank and yank’ methods. These are performance reviews were employees are ranked using a forced ranking system. It usually looks so...
About a week ago I posted an article on the IHM Business School blog about an important, but very taboo subject. At more than 15,000 unique page views the first few days, it is probably the most read article I have ever written. With more than 130 comments on the IHM Blog, it is certainly the most discussed. I was amazed, not only that the article arose such interest, but of the very thoughtful responses, and how many people that have had similar experiences. Leif Claesson, one of the commenters, even took the trouble to translate the article into English. Because of the interest in the original article, I am publishing Leif's translation here. Here is a link to the original article on the IHM Business School blog . --- This was a very difficult article to write. If you prefer reading easy pieces regarding easy subjects, you should skip this one. Robin Williams recent suicide, received a lot of coverage. The speculations with regards to why one of the world’s most gif...
Comments