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...
When cities grow larger, productivity per person increases. When companies grow larger, productivity per person decreases. Cities can last thousands of years and survive plagues and nuclear blasts. Large companies have an average lifespan of fifteen years, and the lifespan is dropping. It is blindingly obvious, except almost nobody noticed until a couple of years ago: Companies have short lifespans. Cities live thousands of years; Cities can survive plagues and nuclear bombs. Companies croak when there is a slight downturn in the economy.; People want to live in large cities, but they want to work in small companies. Why? What is the difference, and does it matter? If we understand why cities are so resilient, can we use that knowledge to build better companies? Companies that are more resilient and better places to work? It turns out we can. Physicist Geoffrey West has studied cities and found a very simple mathematical relationship between city size and productivity: Wh...
Comments