Agile Software Development Ecosystems

by Jim Highsmith

Book Overview

Presents the key practices of Agile development approaches, offers overviews of specific techniques, and shows how to choose the approach that best suits your organization. This book deals with:... This description may be from another edition of this product.

• Format: Paperback
• Language: English
• ISBN: 0201760436
• ISBN13: 9780201760439
• Release Date: January 2002
• Publisher: Addison-Wesley Professional
• Length: 448 Pages
• Weight: 2.05 lbs.
• Dimensions: 1.0" x 7.5" x 9.3"

Customer Reviews

Great Intro to Agile

Jim Highsmith does an excellent job of introducing you to the agile software philosophy. This book includes the basic motivation for agility in the software arena, the foundational philosophies of agile, a review of the top 7 agile approaches being used today (XP, Scrum, DSDM, FDD, ASD, LD, and Crystal), interviews with the leading proponents, and a comparison of Agile versus a more rigorous process-oriented approach.If you are new to Agile approaches or just looking to fine-tune your current software methodology, this book is an excellent start.

Brings it all together better than any other book so far

This book basically brings together the major players and their methods, and explores the differences and similarities between them.Every new paradigm needs a clear, concise, yet thorough synthesis of the ideas surrounding it, and the personalities driving it. For the agile paradigm, this is it. This book is highly underrated in my opinion. If you want to understand agile software development, there's only one book you need to read. That is a major accomplishment. Kudos to Jim Highsmith.(originally posted on WikiWiki)

An Excelent starter

A very good starter for Agile practices.I have been involved in software projects in different roles( programmer, Architect, manager, integrator etc) for 20 years. I felt that MS project never reflected the work hat was actually done, and that if I wanted things to progress, most of the practices I was asked to do were of little help (Heavy documentation, requirements tractability, lots of very detailed design before coding and other fun stuff).This book gives a good definition for the things that really matter.Methodology helps your project only if you adjust it to your people, goal and organization. By giving a broad perspective of agile methodologies, this book enables you to select what should work for you.And - on top of it - I really enjoyed reading it

good overview, good description of what agile means

I found Jim Highsmith's Agile Software Development Ecosystems to be an easier read than his first book Adaptive Software Development. This one is an overview of the Agile methods and people behind them -- Scrum, Dynamic Systems Development Method, Crystal Clear, Feature Driven Development, Lean Development, Extreme Programming, Adaptive Software Development, Kent Beck, Alistair Cockburn, Ken Schwaber, Martin Fowler, Ward Cunningham, himself, Bob Charette -- and descriptions of some projects each method was used on.None of the method descriptions are in-depth enough to actually do them, but they provide enough information to point you into a direction for further investigation. There is some discussion about Agile principles and values, and Agile methods versus non-Agile methods and Company Culture and Market Style, and some discussion on "how to make your own agile methodology" (or how to adapt one to your company's requirements).I recommend it.

Excellent

This book is about "The Agile Movement", if there is such a word.This books attempts to convey the rationale and "night thoughts" of veterans who have been the route of traditional methodologies and UML and the hard lessons learned.It is an interesting and eye-opening book along the line of "The Mythical Man Month" that every software architects, program managers and students of software engineering should read. It does holds its concerns well. An analogy from the art world would be fit here:It is an "Impressionist" software practices resurgent in responding to traditional "Renaissance" software practices in responding to market forces and expectation and to "get the job done", avoiding over-engineered and over modelled process.Whether Agile movement will be the last say in software process in the next decade is hard to say.One big problem with software is that there are lack of accountability that other engineering discipline have and does not seem to fit the shoe as well other disciplines.(civil,electrical,etc). No one got drag to court if a software fails miserably. Compare that to a bridge or house collapsing.So the ultimate question is "What is Software Engineering and does it makes sense?".I think by reading this book will provoke you into thinking.