The Art of Agile Development und über 1,5 Millionen weitere Bücher verfügbar für Amazon Kindle. Erfahren Sie mehr
EUR 24,95
  • Alle Preisangaben inkl. MwSt.
Nur noch 1 auf Lager (mehr ist unterwegs).
Verkauf und Versand durch Amazon.
Geschenkverpackung verfügbar.
Menge:1
Ihren Artikel jetzt
eintauschen und
EUR 8,90 Gutschein erhalten.
Möchten Sie verkaufen?
Zur Rückseite klappen Zur Vorderseite klappen
Anhören Wird wiedergegeben... Angehalten   Sie hören eine Probe der Audible-Audioausgabe.
Weitere Informationen
Alle 2 Bilder anzeigen

The Art of Agile Development (Englisch) Taschenbuch – November 2007


Alle 6 Formate und Ausgaben anzeigen Andere Formate und Ausgaben ausblenden
Amazon-Preis Neu ab Gebraucht ab
Kindle Edition
"Bitte wiederholen"
Taschenbuch
"Bitte wiederholen"
EUR 24,95
EUR 22,53 EUR 15,99
56 neu ab EUR 22,53 8 gebraucht ab EUR 15,99

Hinweise und Aktionen

  • Studienbücher: Ob neu oder gebraucht, alle wichtigen Bücher für Ihr Studium finden Sie im großen Studium Special. Natürlich portofrei.


Wird oft zusammen gekauft

The Art of Agile Development + Agile Retrospectives: Making Good Teams Great (Pragmatic Programmers) + Agile Estimating and Planning (Robert C. Martin)
Preis für alle drei: EUR 79,85

Die ausgewählten Artikel zusammen kaufen
Jeder kann Kindle Bücher lesen — selbst ohne ein Kindle-Gerät — mit der KOSTENFREIEN Kindle App für Smartphones, Tablets und Computer.


Produktinformation

  • Taschenbuch: 438 Seiten
  • Verlag: O'Reilly & Associates; Auflage: 1 (November 2007)
  • Sprache: Englisch
  • ISBN-10: 0596527675
  • ISBN-13: 978-0596527679
  • Größe und/oder Gewicht: 17,8 x 2,3 x 23,3 cm
  • Durchschnittliche Kundenbewertung: 4.3 von 5 Sternen  Alle Rezensionen anzeigen (3 Kundenrezensionen)
  • Amazon Bestseller-Rang: Nr. 109.485 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)

Mehr über den Autor

Entdecken Sie Bücher, lesen Sie über Autoren und mehr

Produktbeschreibungen

Synopsis

"The Art of Agile Development" contains practical, down-to-earth guidance for anyone involved in or considering the agile method - and Extreme Programming in particular - to build reliable software. Agile development methods have become increasingly popular because too many software projects have failed to meet expected release dates, deliver the required features, or to match projected costs. This book provides no-nonsense advice on agile planning, development, delivery, and management taken from the authors' many years of experience. While plenty of books address the what and why of agile development, very few offer developers, managers, stakeholders and users the information they can apply directly. "The Art of Agile Development" provides a gestalt view of the agile development process that serves as a comprehensive introduction for non-technical readers, along with hands-on technical practices for programmers and developers. The book also tackles the people aspect of Extreme Programming. Other books focus solely on the process; this book deals with the need for face-to-face interaction, which is the most difficult aspect of working in an agile development.

You'll find clear answers to questions such as: How can we adopt agile development? Do we really need to pair program? What metrics should we report? What if I can't get my customer to participate? How much documentation should we write? When do we design and architect? As a non-developer, how should I work with my agile team? Where is my product roadmap? How does QA fit in? Whether you are currently part of an agile team, working with an agile team, or interested in agile development you will reach for this book again and again. Author James Shore's companion web site, Successful Software, contains dozens of considered essays discussing agile development and Extreme Programming, with multiple new essays posted each month.

Über den Autor und weitere Mitwirkende

James Shore, signatory number ten to the Agile Manifesto, has been coaching agile teams large and small before they were called agile. He brings both breadth and depth to his discussion of agile development. In 2005, the Agile Alliance recognized James with their most significant award, the Gordon Pask Award for Contributions to Agile Practice. James is an internationally recognized speaker who consults for companies interested in agile development. He writes about agile development on his top-ranked blog, jamesshore.com.Shane Warden promotes free and open source software for O'Reilly's Open Technology Exchange. In practice, this means editing and researching. He is a co-author of The Art of Agile DevelopmentHe has contributed to several projects including Perl 5, Perl 6, Pugs, and, these days, Parrot. Someday, he'd like to claim some responsibility for improving the quality of all software.

Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?


In diesem Buch (Mehr dazu)
Ausgewählte Seiten ansehen
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis | Rückseite
Hier reinlesen und suchen:

Kundenrezensionen

4.3 von 5 Sternen
5 Sterne
2
4 Sterne
0
3 Sterne
1
2 Sterne
0
1 Sterne
0
Alle 3 Kundenrezensionen anzeigen
Sagen Sie Ihre Meinung zu diesem Artikel

Die hilfreichsten Kundenrezensionen

3 von 3 Kunden fanden die folgende Rezension hilfreich Von Dr. Gernot Starke am 25. April 2009
Format: Taschenbuch Verifizierter Kauf
Hätte der Titel "The Art of XP Projects" gelautet - so hätte ich 5 Sterne vergeben. Lob den Autoren zu einer guten XP-Einführung mit vielen Praxistipps.

Aber: Ich hatte eben "agile development" erwartet - und nicht den hier praktizierten Fokus auf XP... das steht ziemlich kleingedruckt in der Einleitung (die ich jedoch erst nach dem Kauf lesen konnte).
Kommentar War diese Rezension für Sie hilfreich? Ja Nein Feedback senden...
Vielen Dank für Ihr Feedback. Wenn diese Rezension unangemessen ist, informieren Sie uns bitte darüber.
Wir konnten Ihre Stimmabgabe leider nicht speichern. Bitte erneut versuchen
1 von 1 Kunden fanden die folgende Rezension hilfreich Von Amazon Customer am 10. Februar 2009
Format: Taschenbuch
Ich habe dieses Buch im Oktober in einem Buchladen gesehen und mich spontan zum Kauf entschlossen.
Das Buch ist quasi eine Anleitung zur Einführung eines Agilen Software-Entwicklungsprozess. Es werden alle notwendigen Techniken zur Agilen Entwicklung ausführlich beschrieben und die Voraussetzungen für eine Umsetzung genannt.
Ich war von den Beschreibungen und den Versprechen des Buches so angetan, dass ich in meinem Softwareentwicklungsteam (das Team besteht aus insgesamt 5 Entwicklern) die neue Vorgehensweise vorgeschlagen und mit Zustimmung der Kollegen gemeinsam eingeführt habe. Seitdem sind wir als Team fleißig am Pair-Programming, machen täglich Stand-Up-Meetings, haben in unserem Büro ein Whiteboard mit Story-Karten, verwenden die Abschätzungsmethodiken mit Story-Points und berechnen unsere (konstante) Velocity und sind allesamt mit mehr Freude bei der Arbeit und haben das Gefühl, wirklich effektiver und nachvollziehbarer zu Arbeiten.
Insgesamt ein sehr empfehlenswertes Buch, dass für mich in der Praxis beweißt, dass es wirklich funktioniert!
Kommentar War diese Rezension für Sie hilfreich? Ja Nein Feedback senden...
Vielen Dank für Ihr Feedback. Wenn diese Rezension unangemessen ist, informieren Sie uns bitte darüber.
Wir konnten Ihre Stimmabgabe leider nicht speichern. Bitte erneut versuchen
Format: Taschenbuch
This book helped me in the past getting in touch with Agile Software development. For new adopters of Agile and/or eXtreme Programming this book is a very good guide. Shane Warden and James Shore focus mainly on XP, but the practices they describe are useful in any context - no matter whichi methodology you might be using. They give clear and practical motivations for their described practices and conclude in the end with an overview over the principles behind the presented practices. In addition the book is very readable.

It covers the main topics of Kent Becks or Ron Jeffries introductions to eXtreme Programming, while going beyond it. The five-fold areas of interest include Collaboration, Thinking, Developing, Releasing and Planning. After starting with this book you get motivated to get more to know about Agile practices. The book gives even more useful hints to bibliography to read next.

This was my first book about Agile that I really loved to read. It helped me overcoming the daily problems I was facing and gave me tools that I needed to try out the next day directly at work. Must buy.
Kommentar War diese Rezension für Sie hilfreich? Ja Nein Feedback senden...
Vielen Dank für Ihr Feedback. Wenn diese Rezension unangemessen ist, informieren Sie uns bitte darüber.
Wir konnten Ihre Stimmabgabe leider nicht speichern. Bitte erneut versuchen

Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)

Amazon.com: 49 Rezensionen
36 von 37 Kunden fanden die folgende Rezension hilfreich
Very Practical, Wide Audience, Lots of Material 24. November 2007
Von Malbery - Veröffentlicht auf Amazon.com
Format: Taschenbuch
The Art of Agile Development is one of my best purchases in a long time. I've read a lot of Extreme Programming and Agile Software Development books and this one really nails it. Many are too theoretical, vague, or just plain developer-centric. This book however is of real practical value to everyone in the team: customers/business analysts, testers, and developers alike.

The book builds around 37 agile development practices in five categories: Thinking, Collaborating, Releasing, Planning, and Developing. Respective examples of practices are: Energized Work, Ubiquitous Language, No Bugs, Vision, and Incremental Design & Architecture. It's obvious that the authors are experienced practitioners as the text is littered with symptoms of common problems and remedial advice. Each practice has a clear explanation, answers to common questions, results you should expect to see, and when to and when not to adopt the practice given your current environment.

As a developer I'm finding this book invaluable. It's helped me think and communicate far more succinctly and effectively - even for material I was intimately familiar with. It's also a book that's accessible to everyone in and outside the team. In short, this is a great book.
27 von 29 Kunden fanden die folgende Rezension hilfreich
Agile and XP Grow Up 16. Dezember 2007
Von Rob Myers - Veröffentlicht auf Amazon.com
Format: Taschenbuch
This book is very well-timed. Now that agile development practices are "crossing the chasm" towards professionally accepted standards, this book reminds us that "agile" is neither a narrow, prescriptive set of standardized practices, nor a free-for-all smorgasbord of every possible practice.

This book will give teams and their management the information necessary to make informed decisions about the make-up of a software product team, and how it operates. The Art of Agile Development is intelligent, thoughtful, professional, and realistic. It is based on years of varied experiences, and it reveals a well-tested set of recommendations.

Part I

The book starts out with high-altitude answers to "Why?" and "How?" and a satisfying definition of "success." This is followed by a story of a hypothetical XP team. The story is full of dialog revealing the day-to-day functioning of a well-running team as a new hire joins the team. That dialog may seem contrived, but it's likely more of a composite of things heard on various teams. Yes, agile teams do enjoy their work, and people who enjoy their work talk about it as portrayed. I think this portrayal brings forth an important decision for the reader: Do you suspect that your development teams could truly run more smoothly, or are you merely looking for a way to dismiss this weird new "agile movement" and get on with your agonizing career? (Either way, keep reading!)

Part II

The second section of the book is a detailed exploration of the development practices recommended by the authors. There are a number of practices recognizable from XP, with some additional thoughtful practices, some realistic alterations, and some notable replacements. As I said, this is neither a full buffet, nor is it a restrictive diet. This is a menu prepared by two experienced chefs. They talk about contraindications and alternatives for each practice, but they also warn of the pitfalls of removing key ingredients.

Each chapter, or practice, comes with embedded boxes highlighting important points, and "allies," which are the names of other related (and supporting) practices and their page numbers. These allies appear in little grey boxes in the margins. They give you the ability to use the book as a reference, but they also paint an important picture of how the practices fit together.

I have to give special credit to the authors for the chapter they call simply "Trust." Under "alternatives" they state rather clearly that there are none. No replacement for trust! It seems so obvious, and yet teams struggle every day because they don't have it. The authors, thankfully, provide suggestions for establishing lasting trust.

Another noteworthy chapter is "No Bugs." If you're standing in the bookstore trying to decide whether or not to buy the book, turn to this chapter. These practices bring numerous others into focus. Again, if you're thinking "pipe dream," keep reading. If you follow this menu conscientiously and rigorously, you will arrive at the sweet dessert of extremely high-quality code.

Part III

Have you ever had a delicious meal at a friend's house, obtained the recipe, tried it for yourself, and thought "Oh, that didn't turn out well!" What can you do?

It takes experience (and that means real time in the kitchen) before you can comfortably tweak a chef's recipe. You can also go back to your experienced friend and ask for advice or clarification. This book provides the same opportunity. Read Parts I and II, go try it for a while, then come back to Part III.

This section describes the underlying values and principles behind the agile practices, and will help your new process and your team's existing culture work together towards greater and greater success. If a lot of the chapter titles in this section sound like Lean product-development principles, well, I think that's intentional.

It is perhaps difficult to pinpoint what is truly "agile." This book represents true agility without claiming to fully define it, and I hope it helps others on real software projects navigate a successful jump across the chasm.

This is mature, no-nonsense agility, in book form!
14 von 14 Kunden fanden die folgende Rezension hilfreich
Terrific work on Agile for newcomers and pros alike 2. Februar 2008
Von James Holmes - Veröffentlicht auf Amazon.com
Format: Taschenbuch
I've been working through this book for the last five or six weeks and have been loving it. Usually I do a deep skim read of most books -- the kind of reading you do in college where you need to get the gist of a book and some of the pearls -- but this one's grabbed me into an intense period of reading, reflecting, and re-reading parts.

Warden and Shore have written a fantastic work here. The book covers all aspects of Agile from planning to delivery, and each aspect is broken down into sensible sections. It reads like a series of great articles on very granular components of Agile such as Refactoring, 10-Minute Build, or Stand Up Meetings, but it's so well-written that all the articles mesh together perfectly leaving a smooth path through the book.

Each article (and that's my description, not theirs) lays out a specific practice or component of Agile, walks you through the benefits of it, details how that practice fits in the larger picture, shows you how to implement that practice, and discusses how to identify when you might need to implement or rework the practice. Each article is extremely well done and approaches its topic from a very pragmatic view. There are also cross-references to other practices elsewhere in the book that can help you solve related issues. Additionally, there are great references to other books, articles, and web posts.

Overall the book's just terrific. It's easy to read, it's pragmatic and practical, and it's thought-provoking. Art of Agile Development can be used by newcomers interested in moving into Agile practices, but it's also absolutely applicable to Agile pros looking to improve their own system. It certainly got me fired up with a number of ideas on how to improve our process even more. Perhaps that's the best endorsement of this book.
4 von 4 Kunden fanden die folgende Rezension hilfreich
Great book for beginners 19. Mai 2009
Von George Romaniuk - Veröffentlicht auf Amazon.com
Format: Taschenbuch
My encounter with agile took place in 2004 when my company wanted to formalize the entire product development process. We took this opportunity to learn more about agile and apply it our software development.

I read few short articles and a book about agile but there was not enough practical information to convince us that we will be safe embracing agile methodology.

I learned about this book quite recently from practitioners of agile, read the book and also participated in a very interesting discussion club.

The title of this book is in my opinion little misleading - I was expecting to read about some esoteric topics related to agile software development but to my great surprise I found almost a "Manual" or a "Handbook" of agile software development.

The art is being taught in a very well defined environment, little too idealized in my opinion but with clear boundaries and good instructions what to do in case your situation is outside of this environment. I read the book from page one in natural page order and noticed that the book was getting more interesting as I was progressing.

There is a great body of down to earth instructions for beginners, not only related to pure software development but also relevant to setting up the team in your company's environment.

The book also offers good discussion of product requirements, the role and approach to testing and to some extent - making decisions regarding software architecture.

The book has a phenomenal bibliography and inspired many thoughts about the nature of software development and similarities between software development and industrial mass production environment

I am sure that the book is not going to end the writing career of the authors and a follow-up will be available soon, discussing issues like rewards and compensation in companies practicing agile methodology.
35 von 47 Kunden fanden die folgende Rezension hilfreich
Reading Is Painful, Repetetive and Choppy 2. November 2009
Von D. Frost - Veröffentlicht auf Amazon.com
Format: Taschenbuch Verifizierter Kauf
I just can't stand reading this book. Being an SCM manager I am familiar with the good ideas and the problems of agile development. I am also familiar with the managers who like to use catch phrases to motivate and fix every issue with development.

This book is great training if you want to just spit out a bunch of buzzwords in agile programming but not really understand them. The first 200 pages of the book are literally a maelstrom of agile "buzzwords" broken up into recommendations of XP (extreme programming).

One thing that is repeated for every single XP practice is the following "THIS_PRACTICE is a prerequisite for agile (or XP) but if you can not THIS_PRACTICE you can still be effective... and here are alternatives... contraindications.." Ok, first off, if you have an idea or set of practices to improve programming, stick to you guns. With all the alternatives and wishy washy commitment in the writing of this book, I would conclude that the idea of XP is not that good in the first place.

The structure of the book is painfully chopped up into small pieces and the exact same concepts, practices and advice are repeated over, and over, and over!!!! Its maddening. Each chapter is also padded with all of the "if you can't do this..." sub-chapters which like most of the book just repeats the same conceits. There are many good points in the book but its simply not interesting to read. It reads more like a huge power point presentation. Touching on hundreds of ideas and highlighting them. The treatement of each individual practice is simply too shallow to be thought provoking or entertaining in any way. I know programming practice is not sexy but it can certainly be engaging.

The best parts of this book are short anecdotes about the anthers experience and nods to other, much better reading material like "The Mythical Man-Month". I admit I could not suffer the entire book but I did read some of the later chapters and the writing style is just as fractured and annoying as 10 or so chapters I did read. The authors do appear to have a good understanding of agile practice but they are not that familiar with writing a well structured book.

My advice would be to look at other books on the subject of programming and managing software projects. This will give you a good background. This book is just a primer on XP and a poorly written one at that.
Waren diese Rezensionen hilfreich? Wir wollen von Ihnen hören.