Rating: 
Summary: A Management Book that Developers Should Read Too
Review: This book is essential reading for IT managers, but senior developers should read it too. While some things in this book will make engineers say "I know that, but just didn't know how to say it", other things are real eye openers. Engineers will find some of the management theory to be dry reading, but it is relevant.If you ask engineers who have used both traditional (i.e. waterfall) methods and agile methods they will tell you that agile methods are superior, but if you ask them why and how agile methods deliver better results almost none of them will be able to tell you. They know it from experience and intuition, but they do not understand the why and how. Of course, since engineers don't know how and why agile methods work they are at a disadvantage when it comes to convincing management to try them. That's where David Anderson's book comes in. It explains how and why agile methods work in terms that engineers can identify with and that managers understand: increased profit, meaningful accounting, and the ability to repeat successes. Being able to convince your manager to try agile methods is only one benefit. As a team lead or architect if you don't understand what makes agile methods work you may very well end up doing things that defeat their advantages. This book explains why certain things help software development and why others impede it. Why and how should software development teams should identify and exploit constraints? What is Throughput Accounting and why should it be used for software development instead of Cost Acounting? How is software development different from other kinds of engineering and manufacturing businesses? How can the self organizing behavior intrinsic to successful software development efforts be improved? Anderson's book is invaluable to the manager and valuable to the software engineer.
Rating:
Summary: hard work, but worth it.
Review: This is the hardest - and possibly best - Agile software book I have read so far. It's hard because it digs deeper into the cause and effect at play within agile environments and because it deals with the "bigger" financial aspects of lean. It's a well written, comprensive text.
| 
