OK, So Maybe Software Development Isn’t Engineering After All

This is the indostan six men in learning more toward Beijing people to see elephants (although they all blind), each observation may satisfy his heart - Dihangefulei Sachs (1816-1887) fable we all know that the blind men and the elephant, how to make everyone is so sure that they do not know what this wonderful beast is based on the limited knowledge of a certain part, they almost time to crack down on dissidents, and their findings. I am reminded of this recently when reading, the Queen Mary and Tang Peng and Mubi grams of Lean Software Development (Addison - Wesley, 2003), which strongly suggest that our tunnel vision software development - Specifically, we troubled determination to take it as a project areas - has led us to go astray. The commitment poppendiecks bring the lesson is very rare product development, from production enterprises in trying to understand how to develop software, in order to become a more profitable move. This ultra-thin, 200-page volume is one of those things, you can give your manager, if you are looking for a good argument that a quick process is able to store your. But it is one of those books, you can actually learn? Change is never easy Many of us have tended to the software side of the elephant marked "works" for so long, its tough for us to see the field any other way. Even those of us with degrees in the more traditional fields of engineering professionals, I am afraid, should know better insist on its own "software engineer", that is, despite the fact that software, and similar projects have rarely, you stop think about it, at least in this type of project, that is to say, mechanical engineers or electrical engineer, who can apply for settlement of scientific research institutions and mathematical principles to their work. But take off your blinders works for a few hours and read this book, you may come to appreciate that at least part of our elephant looks like the manufacturing sector. This means that we can further understand the lessons learned from the manufacturing software manufacturing cars, washing machines, as well as other real-world decoration.

Course, the manufacturing industry has experienced many changes over the years, from flint tools workshop olduvai Canyon to the latest automated robot cells. The poppendiecks to focus on a particular thread of modern thinking, in the production and product design: Lean principles, which seek to eliminate waste in the production process. (Note that the principle of distinction, they are universal and practices, applicable principles in a particular environment). Lean principles of resonance, as well as the interest of existing software and, in extreme programming (XP) practices, but a lean software development organizations is not necessarily an embrace wholeheartedly XP. A very good thing that this book is that it argues that the need always to evaluate what works in their own organizations, rather than trying to follow the cookbook recipes may or may not apply.

Principles and tools Lean software development mainly around 11 chapters, each chapter is devoted to an agile principles that the authors identify: eliminate waste sound learning may be decided later as soon as possible to provide authorized team built on the integrity of the whole (There is also a chapter VIII the end of a set and repeated attempts to blindly apply warned things without thinking, they passed).

Skating very close to some of these territories platitudes, it is difficult to imagine any person would agree that the mandate of the team the past few days (or at least to imagine anyone so foolish as to such differences written). The value of this book goes far beyond the two organizations, although. First, the author for a job well done tease how these principles found in the process of building lean product development organizations, can be applied to software development. Second, they divided into a number of sub-chapters, dealing with 22 tools that help focus on the principles, and further.

Not to be fooled by the word "tool" into thinking of the compiler and linker. These tools of a more philosophical or managerial sort. For example, a tool that in the first chapter may later decide to "Options Thinking": A discussion of the options open to you so that you do not have to spend resources, until they really need. As another example, you will find that, "professional knowledge" one of the tools, used to strengthen the ranks - in-depth study on the benefits from the work to actual development expertise, which has hidden in your team , rather than trying to impose top-down approach heavy impact on them.

One for managers Ironically, one of the best things that this book from the perspective of the development work, it is a complete lack of source code. It is not recommended, particularly software development tools, practices (beyond the line of this bottom-up thing, because the source code control), or programming techniques. This makes it particularly suitable for those folks is responsible for the management ladder, may not have much grasp of precisely what the folks on the front line are doing coding, but still have the responsibility to maximize productivity.

This book can be a great accessory sales booth said that the cloud is this: "You see, we have a delivery is almost impossible on the current project schedule. If we want to buried in the procedures and instruments work, we will never make it. But if you can cut through some red tape, for us, so that we could really do our jobs, no waste, and we will try to improve it. There are several ways, we can modify the program to make it more efficient, "Maybe your manager will not have the opportunity, under such circumstances, you will not be worse than you are now. However, if you are lucky, then this book can be a lever to help move things toward a more flexible world, which, the developers have more capacity and software, in the approach to development would be very meaningful.

But remember: an elephant is no wall The idea in this book, can be very appealing, especially for those who have tired of the waterfall method and the process involved in the pre - Design. But even so, you need to exercise a bit ago, must be carefully considered, and wholeheartedly plunge into Lean software development. The support of this book, there are a lot of the evidence came from the manufacturing sector, in particular the story of how the success of the Japanese automotive manufacturers with Lean techniques. However, its fallacious to argue that success depends directly on the Lean technology History of a few do so and can not prove any causal relationship. There are many differences in the average software shops, the Americans and Japanese car manufacturers, and more software developers are the United States may not care to live in Japanese society. Its enticing, but not logical, assuming that the only change, we want to see are those who will bring success.

Finally, please remember that even if the software is not building projects, not car manufacturing. We can draw lessons from these areas (as well as from the construction, accounting, or even restaurant management), but in the end we need to continue with the testing and development of our own repertoire working practices. The poppendiecks are very good about stresses the need to develop the practice of the work in this respect your own organization. Just sure, you do not skip this part of the book is very useful in your search for new ideas.

Would like to read more of Mikes work? Larkware visit his Web site is updated daily, in http://www.larkware.com.