Agile and Iterative Development: A Manager's Guide (The Agile...

Features

• Cover Type: Paperback with 368 pages
• Published by: Addison-Wesley Professional August 21, 2003
• Written in: English
• ISBN 10 Number: 0131111558
• ISBN 13 Number: 978-0131111554
• Book Dimensions: 8.9 x 7 x 0.9 inches
• Weighs: 1.5 pounds

Reader Reviews
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. Comment | | (Report this)