Agile and Iterative Development: A Manager's Guide (Agile Software Development Series) (英語) ペーパーバック – 2003/8/15
Kindle 端末は必要ありません。無料 Kindle アプリのいずれかをダウンロードすると、スマートフォン、タブレットPCで Kindle 本をお読みいただけます。
Using statistical research and case studies, the author presents the most convincing case ever made for iterative development. He offers a concise summary of the key ideas that drive all agile and iterative processes, with the details of four noteworthy iterative methods: Scrum, XP, RUP, and Evo.
CRAIG LARMAN is known throughout the international software community as an expert and passionate advocate for object-oriented technologies and development, and iterative and agile development methods. He serves as Chief Scientist at Valtech, a global consulting and skills transfer company, where he has led the adoption of iterative and agile methods. Larman also authored Applying UML and Patterns, the world's best-selling text on object-oriented analysis and design, and iterative development.
The kindle version should get 3 stars. There are lots of small textual diagrams and graphs that were poorly imported into the kindle and they come across as thin grey type. I have perfect vision and I first found myself holding the kindle next to my face to read the text, but I've eventually just given up on reading the small graphs.
Two things about the book that keep it out of my 'recommended book list' are:
1. I thought it could have used a bit more editing/revision prior to release as their are some minor errors, but on the whole this is a very good book.
2. Removal or Revision of Chapter 4. This chapter is an attempt to bring all of the agile/iterative methods together into a 'story' but it just doesn't work that well for me. What might have helped is to move this chapter toward the end of the book after all the methods have been discussed.
Overall...this is a good book and one worth reading if you are interested in learning more about Iterative & Agile development topics. The book really made me think about the 'tried and true' PMI methods for managing projects and how those methodologies aren't really a good fit in the world of software development.
After reading the book (and a few other Agile books) I've begun to think about ways to move Agile methods from software/product development to other areas such as IT Management, Service Management and other areas of business.
The first chapters of the book are probably the best description of what iterative development is ever written. Craig's writing style is clear and easy to understand. After this, the book dives in the more than interesting background on iterative development and especially waterfall development after which the author gives an excellent summary of the current evidence about agile and iterative development.
This is where you could stop reading the book. The rest of the chapters are summaries of other methods which are ok, but I'd recommend to read the original work on each of these methods instead. The chapter on Unified Process is somewhat weird and IMHO misplaced.
In summary, the book is not perfect however it's by far the best available . It's the only book which so clearly describes the basics of iterative development. Craig's writing style is clear and easy to understand. This book is a modern classic and highly recommended for anyone who is involved in Software Development.
The book cogently and painstakingly explains how several of waterfall's practices have been conclusively linked to project failures, and how, on the other hand, the practices of Agile and iterative methods like Scrum and XP reduce project risk. Larman summarizes research findings encompassing thousands of projects, and quotes the supporting opinions of standards bodies and industry thought-leaders. The net effect is compelling, to say the least.
If you are an Agile skeptic, this book may rattle your conviction. If you are fence-sitter, it may convince you. And if you already have Agile fire in the belly, then certainly this book will stoke that fire. After reading it, I am left wondering how intelligent, experienced software development management can justify the continued use of a process that has wasted so much money and caused so much pain.