![Agile Management for Software Engineering: Applying the Theory of Constraints for Business Results by [Anderson David J.]](https://m.media-amazon.com/images/I/51HGbxinJSL._SX260_.jpg)
Abraham Lincoln once asked something like, "If you call a tail a leg, how many legs does a dog have?" The answer is four. "Just because you call a tail a leg doesn't make it so." Just because you want to call some development practice "Agile" doesn't make it so. In this book, David Anderson makes a case for calling Theory of Constraints the underlying definition of Agile software development practices. The principle tie is that a key measure in the Theory of Constraints is called Throughput; the amount of value delivered to the customer. Agile methods pride themselves as delivering value to the customer quickly. Based on the Theory of Constraints definition, the Feature Driven Development (FDD) method, Anderson's personal expertise, turns out to be the most Agile of all.
In making the case for the Theory of Constraints based approach, Anderson has given us a lot of formulas and metrics for looking at software projects. This is the most thorough treatment of the subject I have seen yet. I wasn't fully satisfied with the metrics as I felt the book didn't deal with the biggest problem in metrics, the problem of characterizing the measure. To do good metrics, you have to be very clear on what you are measuring, the characterization problem. Without that, all the formulas, graphs, and trends are pretty much useless. Most of the book dealt with the problem by saying, "If you could measure `X', then..." I got really tired of all the Ifs in the book.
In fact, I am not sure I should like this book or not. I found myself half of the time saying to myself, "Hmm, that is a interesting idea," and the other half saying, "I don't think so." Perhaps it was all the Ifs, perhaps it was the repetition. I am glad to say at the end of the book Anderson does appear to have the intelligence to note that one size does not fit all and does a nice job of suggesting where the best choices in software development approaches might be.
So, who should read this book? Well, if you like Donald Reinertsen's and Eliyahu Goldratt's work and live in the software world, this book is for you. If you have to teach Agile seminars to software professionals (like me), then this should be on your reading list as well. If you are general software project manager or developer who is looking to improve the way you do software development, then I would probably pass on this book. Not that the ideas are all wrong but you probably will get lost along the way. If...
- Format: Kindle Edition
- File Size: 4684 KB
- Print Length: 352 pages
- Simultaneous Device Usage: Up to 5 simultaneous devices, per publisher limits
- Publisher: Pearson; 1 edition (17 September 2003)
- Sold by: Amazon Australia Services, Inc.
- Language: English
- ASIN: B003CW67YG
- Text-to-Speech:
Enabled
- Word Wise: Not Enabled
- Customer Reviews: 7 customer ratings
-
Amazon Bestsellers Rank:
#1,142,597 Paid in Kindle Store (See Top 100 Paid in Kindle Store)
- #343 in Software Project Management
- #312 in Agile Management
- #609 in Software Design & Engineering Textbooks
