- Taschenbuch: 304 Seiten
- Verlag: Addison-Wesley Longman, Amsterdam (1. Oktober 2001)
- Sprache: Englisch
- ISBN-10: 0201699699
- ISBN-13: 978-0201699692
- Größe und/oder Gewicht: 18,8 x 1,7 x 23,5 cm
- Durchschnittliche Kundenbewertung: 4 Kundenrezensionen
- Amazon Bestseller-Rang: Nr. 272.788 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
- Komplettes Inhaltsverzeichnis ansehen
Agile Software Development: Software Through People (Englisch) Taschenbuch – 1. Oktober 2001
Dieses Buch gibt es in einer neuen Auflage:
Kunden, die diesen Artikel gekauft haben, kauften auch
Es wird kein Kindle Gerät benötigt. Laden Sie eine der kostenlosen Kindle Apps herunter und beginnen Sie, Kindle-Bücher auf Ihrem Smartphone, Tablet und Computer zu lesen.
Geben Sie Ihre Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.
Wenn Sie dieses Produkt verkaufen, möchten Sie über Seller Support Updates vorschlagen?
Lightweight methodologies are exploding in popularity because their flexibility is ideal for today's fast-changing development environments. In Agile Software Development, legendary software expert Alistair Cockburn reviews the advantages and disadvantages of lightweight methods, synthesizing the field's key lessons into a simplified approach that allows developers to focus on building quality software rapidly, cost-effectively, and without burnout. Ideal for managers seeking to transcend yesterday's failed approaches, the agile movement views software development as a cooperative game. As players move throughout the game, they use markers and props to inform, remind, and inspire themselves and each other. The goal of the game: to deliver a working software system -- and to use the lessons of each project to build a new, smarter "game" for the next project. For every IT executive and manager, software developer, team leader, team member, and client concerned with building robust, cost-effective software.
"Coming of age for software developers means understanding that software is a cooperative effort, not something individuals do in isolation. This is a book that teams of software developers can thrive upon, full of sensible advice for a cooperative development approach."
--Tom DeMarco, The Atlantic Systems Guild
Software development paradigms are shifting. The development group's "team" ability, and the effects of the individual developer, become more important as organizations recognize that the traditional approach of increasing process pressure and overworking team members is not meeting getting the job done. The pioneers of Agile methodologies question the preconceived processes within which development teams work. Rather than adding to the burden of the individual developer, Agile asks "how can we change the process so that the team is more productive, while also improving quality?" The answer is in learning to play the "game."
Written for developers and project managers, Agile Software Development compares software development to a game. Team members play the game knowing that the ultimate goal is to win--always remembering what they have learned along the way, and always keeping in mind that they will never play the same way twice. Players must keep an open mind to different methodologies, and focus on the goal of developing quality software in a short cycle time.
Based on a decade's work and research, and interviews with software project teams, this book presents sound advice for bringing difficult projects to successful conclusion with a minimum of stress. It includes advice on:
- The principals behind agile methodologies
- Which methodologies fit different projects--including appendixes to select the appropriate methodology on a project
- New vocabulary for describing methodologies
- Just-in-time methodology tuning
- Managing the incompleteness of communication
- Continuous methodology reinvention
- The manifesto for agile software development
Today's software developers need to recognize that they have a number of methodologies to choose from. With this book as a guide, they can break free of nonproductive habits, move beyond old routines, and clear a new path to success.
0201699699B09142001 Alle Produktbeschreibungen
Prima, selten so ein gutes Buch gelesen!
Cockburn schafft mit diesem Buch etwas, das nicht vielen Fachbüchern gelingt. Selten wurde Fachwissen so klar und deutlich , aber zugleich so unterhaltsam vermittelt. Mit diesem Buch lernt man nicht nur für den Beruf, sondern auch für's Leben.
Gegenüber diesem Werk fallen selbst andere Branchenklassiker wie "The Mythical Man Month" und "Extreme Programming Explained" deutlich zurück. Ein klares must read!
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta) (Kann Kundenrezensionen aus dem "Early Reviewer Rewards"-Programm beinhalten)
The book is an eye opener for the software development profession. He discusses very much things which sometimes have come up (by people like Jerry Weinberg) but never really made it in the mainstream. This is what this book has done, bring them out. These are things like different skill levels of people, cost of not being colocated, different processes for different size groups, impact of skills on the size of the group etc.
The book is sometimes abstract though. It doesn't always takes concrete solutions. If that's what you expect then you might be dissapointed.
Now 5 years after publication, this is still relevant and still in the top 10 list of Agile books. A must read!
The impetus for this approach came from the realization that more was not better. A common statement from successful project teams was: "...what we want to express doesn't get captured in ... models...(it's) what we say to each other while drawing on the board." From this Cockburn found "...successful teams were still delivering software without using our latest energy-saving ideas... a well-functioning team of adequate people will complete a project almost regardless of the process or technology..."
Cockburn gives his recommended standard methodology structure of 13 inter-related elements as well as a discussion of Agile Techniques and his own Crystal Methodology. Cockburn stresses the human equation as well as using tools that are appropriate to the circumstances - i.e., the particular project and available resources.
Tucked away in the Appendices are more gems. Appendix A covers The Agile Alliance group and it's Agile Software Development Manifesto - a 12-point summary of key principles. Appendix B has brief summaries of three interesting works along with Cockburn's commentaries: Peter Naur's 1985 article, Programming as Theory Building, Pelle Ehn's now out of print, Work-Oriented Development of Software Artifacts, and 17th- century samurai Miyamoto Musashi's The Book of Five Rings.
The book contains a wealth of information for the experienced designer or programmer; it is not a book for beginners. Cockburn ends his commentary of Ehn "...I evidently wasn't ready to read very many of his words in 1993...(I) wonder how many other concepts he mentions, but which I haven't yet noticed. I hope you take the time to reread this article in another year or two."
I would suggest that Agile Software Development be reread every year or two also.