Rating: 
Summary: Exhaustive look at proven methods
Review: If ever there is a book that should be part of a college-level software engineering curriculum as well as carefully read by software engineering development and project managers this is it. Every major iterative development methodology is covered in complete detail, with an emphasis on Agile methods, and a solid business and technical case is provided for the general approach.Why make a case for? As difficult as it may be to believe, the waterfall method is still prevalent despite the large body of literature on rapid, iterative development SDLCs. Indeed, I have worked in environments that claimed to embrace the RUP as the enterprise methodology in principle, yet in practice projects were planned and managed using the waterfall SDLC. Why the disconnect? Managers were set in their ways and had no true understanding of the mechanics or value of Agile and iterative development methods. This book can change that because each major approach is carefully described using the following format for easy comparison and to clearly show strengths and weaknesses:
Method Overview
Lifecycle
Workproducts, Roles, and Practices
Values
Common Mistakes and Misunderstandings
Sample Projects
Process Mixtures
Adoption Strategies
Fact versus Fantasy
Strengths versus "Other" More importantly, these approaches are placed in the context of the benefits of incremental delivery, with clearly presented evidence of the benefits, which is provided in Chapter 6. Regardless of biases or preferences, any objective reader will come away with a clear sense of the meaning of 'Agile' and the power and value of iterative development. You will also come away with a good frame of reference with which to compare your own organization's approach to development and delivery, and how to improve it.
Rating:
Summary: Thorough and poigniant
Review: The following is a letter I wrote to someone about this book:
Carlton, You should get hold of Craig Larman's book "Iterative and Agile Management". It has some of the best information about the failings of up-front requirements that I have seen. He quotes from dozens of different peer-reviewed research studies that date back to the 70's and 80's showing that the vast majority of software project failure can be traced to up-front requirements and waterfall mentality.
This information is so significant that I can't believe it's not more widely known. These research studies were done by some of the best people in the industry, including people like Fred Brooks, Capers Jones, and Tom Gilb.
There are 50 pages of such information, all very easy to read. Show it to your managers. Show them the report that the U.S. Department of Defense lost nearly half their major software projects in the 70's and 80's because of up-front requirements analysis.
Rating:
Summary: Simple, effective and right on the target
Review: This book is written in the same agile fashion as what its subject is. It is concise, easy to understand, extremly well illustrated with examples and research results demonstrating practical value of the iterative development.
I found its greatest strength to be:
A. It compares all the prominent iterative methods using practical examples as you would do it in real world.
B. Your manager can read it,(As the title suggest) and maybe even beleive it.
Adopting the methods presented in this book may be the best thing ever that happened to your projects.
Rating:
Summary: Excellent Book
Review: This is the best book I have ever read about modern software development methodologies. I never really understood the difference between the UP (Unified Process) and the RUP (Rational Unified Process) before I read this book. Now I understand the differences very well. I also didn't really have a good understanding of the main iterative methodologies: Scrum, XP, UP, and Evo. I had heard and read a little about all of these methodologies, but until I read this book, I didn't realize how little I knew. If you would like to learn more about agile and iterative development and how it compares to the traditional waterfall software development methodology, you need to buy this book. Also, if you are having trouble getting your management team to buy in to agile and iterative software development, buy this book. It will give you all of the ammunition you need to convince them.
Rating:
Summary: Excellent Book
Review: This is the best book I have ever read about modern software development methodologies. I never really understood the difference between the UP (Unified Process) and the RUP (Rational Unified Process) before I read this book. Now I understand the differences very well. I also didn't really have a good understanding of the main iterative methodologies: Scrum, XP, UP, and Evo. I had heard and read a little about all of these methodologies, but until I read this book, I didn't realize how little I knew. If you would like to learn more about agile and iterative development and how it compares to the traditional waterfall software development methodology, you need to buy this book. Also, if you are having trouble getting your management team to buy in to agile and iterative software development, buy this book. It will give you all of the ammunition you need to convince them.
Rating:
Summary: Required reading
Review: This latest book of Craig Larman's has been so well received at my office that I can't get my copy back as it is circulated from manager to manager. Hopefully, they'll get their own copies soon. But seriously, as my work is based around Scrum, XP, & RUP I have found this book compelling. Larman's insightful and objective process analysis make this book required reading for all leads and managers.
Rating:
Summary: Sadly it's true
Review: Waterfall style projects do not work for software development. We need to be responsive to a dynamic marketplace - embrace change, don't fight it. If you've struggled with rigid processes imposed on your software development team, or at the other extreme, if you've never known how some process can help your software team - then this is a great book for you. Craig provides the evidence to support my view that software development is not a repeatable, conveyor belt production line. It is an exploratory endeavour. Sure there are constraints imposed on a software team - budget, resources, time. But they should be the boundaries that your team operates within. You should not try to be specific about the tasks your team will do, just be specific about their boundaries - what they won't do. If you struggle to understand this concept, or struggle to make others understand, point them to Craig's chapter on evidence. It seems the software industry project managers have hoodwinked us into believing every small step in a project can and must be planned out, otherwise the team will fail. My experience, and Craig's research, supports the fact that this is incorrect. Projects can be run in an agile manner and will be successful. I've been able to use this text to address other people's concerns, to support my observations and to help move a very rigid team to be more adaptive. In fact, I find it hard to locate the book now as it is being passed from one PM to the next! Hmmm, about time they bought their own copy...
Rating:
Summary: We went one better than just buy the book...
Review: We had the pleasure of Craig Larman's presence for 2 days here in Melbourne Australia. Craig conducted a seminar on UP/AGILE/SCRUM etc and the EVIDENCE for its use. He also took us through a practical exercise based on his "UML and Patterns" book as well - another great read... Boy - did he switch on some lights as to why you should use AGILE rather than WATERFALL development. I am now the proud owner of both his books (personally signed! as well). The 2 days were fantastic. The books are even better - complementing each other with lots of examples and stating actual scientific facts. I am now busy trying to read "Agile and Iterative Development: A Manager's Guide" on the train and the like. The book will be a great aid in helping you change mindset of management so do yourself a favour - grab a copy for yourself and one for the boss!! You will not be disappointed. Mark Bourne
Rating:
Summary: Adios Waterfall
Review: Yes, indeed, Finally. Abundant proof in one book that the traditional waterfall approach is a terrible way to manage software projects, and is therefore slowly being displaced by agile and iterative approaches. Larman does a devastatingly thorough job of debunking waterfall once and for all. 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.
| 
