5 of 6 people found the following review helpful
5.0 out of 5 stars
A must read for all people involven in software development., 28 April 2005
The book addresses many areas of why the culture that exists in IT and firms that deal with IT is not working and why many IT projects go wrong. He points out that this is not due to lack of design, but because design is not done in the proper way. He talks about the roles of everyone (managers, programmers, designers, users, etc.) during the design and what things are been done wrong. He goes into depth why programmers are the least suitable people to do the design and how they can not "think as users". The good thing about this book is that it also gives many advices and ways on how to do things the right way. Thus, he does not only identify the problem areas, but he goes on and suggest solutions and ways to improve.
This book is a very good reading for everyone who is involved in the ANY part in the software development phase. I strongly recommend that people take some time to read it, or just browse through some areas of it. The book is split in two major parts:
The first part (Chapters 1-8) shows why there is more of a cultural problem than a technical problem on the way that software is developed. It is a good background reading to understand the rest of the book.
The second half (Chapters 9-14) suggest ways to improve the bad culture and create software that is actually helping and not embarrassing the users. This is the part is the main core of the book and needs reading. It can be understood more deeply once the first part has been read, but this part can be read on its own as well.