Improving the world with software
Better software. Better questions.
Essays on software development, teams and the craft of building things that last.
Essays from December 2008
7 essays from December 2008
-
(Don’t) be evil!
It seems that Google has lost the “don’t” from their slogan. Incredible, it takes only a mild recession for Google to lose all of their ethics! Google has asked the Internet providers for preferential treatment! Shame on you Google. PS: I’ve backed up the blog! 😉
-
Estimation is needed but useless. Do it and throw away the numbers!
I’ve discussed this idea a few times with some friends, but I’ll concede that the ultimate argument for stopping to estimate altogether is still to come… In the meanwhile here is more food for thought. Rob Bowley argues why estimations are bad in software development. My favorite part of his presentation: [In a study discussed …
-
The Law of Disproportional Consequences
Why this title? I wanted to describe this idea that in software it is far harder to develop the right things. Yet the impact of developing the right product is disproportionally higher than incremental improvements in the way you develop an existing product. If you look at the history of software companies this is quite …
-
The reason why top managers should questioned and challenged by us, the Lego edition
For many people that have read about the Toyota Production System (TPS) the image of Toyota has been improved and their willingness to buy a Toyota car has been positively affected (heck, I _want_ to buy a Toyota, I just can’t justify buying a car). But how about reasons not to buy a product from …
-
The Toyota Way in the clothing industry, examples to pay attention
If you have been following this blog, it is no news for you that I’m a big fan of what is known as Toyota Production System and it’s ideas as described by Jeffrey Liker in the famous “Toyota Way“. What you don’t know is that I’m a big fan of many other companies that exhibit …
-
The “it’s not my bug” anti-pattern
Talking to a friend we were discussing the organization of feature teams in a local company. They were previously organized in component teams, which led to a lot of inefficiencies and disconnected work. This happened because one team would only work on one component, and when one feature required work in many components, that feature …
-
Nokia goes agile. Will the rest follow?
Ari Jaaksi from maemo.org is blogging about Scrum in Nokia’s Linux/Open source projects.Also, Juha-Markus Aalto (of Object development fame) presented what I would call the “Nokia Agile Requirements Model” (and what Dean Leffingwell calls “Lean, Scalable Requirements Model“) at the Object days in Tampere. See the slides here(PDF alert). With all of this I can …
Nothing matches that yet.
Keep the conversation going
The essays work best in company. Join the community to keep the questions coming.