Lean Software Development: An Agile Toolkit: An Agile Too... und über 1,5 Millionen weitere Bücher verfügbar für Amazon Kindle. Erfahren Sie mehr


oder
Loggen Sie sich ein, um 1-Click® einzuschalten.
oder
Mit kostenloser Probeteilnahme bei Amazon Prime. Melden Sie sich während des Bestellvorgangs an.
Jetzt eintauschen
und EUR 7,97 Gutschein erhalten
Eintausch
Alle Angebote
Möchten Sie verkaufen? Hier verkaufen
Der Artikel ist in folgender Variante leider nicht verfügbar
Keine Abbildung vorhanden für
Farbe:
Keine Abbildung vorhanden

 
Beginnen Sie mit dem Lesen von Lean Software Development auf Ihrem Kindle in weniger als einer Minute.

Sie haben keinen Kindle? Hier kaufen oder eine gratis Kindle Lese-App herunterladen.

Lean Software Development: An Agile Toolkit for Software Development Managers [Englisch] [Taschenbuch]

Mary Poppendieck , Tom Poppendieck
5.0 von 5 Sternen  Alle Rezensionen anzeigen (3 Kundenrezensionen)
Preis: EUR 35,95 kostenlose Lieferung. Siehe Details.
  Alle Preisangaben inkl. MwSt.
o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o
Nur noch 6 auf Lager (mehr ist unterwegs).
Verkauf und Versand durch Amazon. Geschenkverpackung verfügbar.
Lieferung bis Samstag, 30. August: Wählen Sie an der Kasse Morning-Express. Siehe Details.

Weitere Ausgaben

Amazon-Preis Neu ab Gebraucht ab
Kindle Edition EUR 16,21  
Taschenbuch EUR 35,95  

Kurzbeschreibung

8. Mai 2003
Lean Software Development: An Agile Toolkit * Adapting agile practices to your development organization* Uncovering and eradicating waste throughout the software development lifecycle * Practical techniques for every development manager, project manager, and technical leader Lean software development: applying agile principles to your organization In Lean Software Development, Mary and Tom Poppendieck identify seven fundamental "lean" principles, adapt them for the world of software development, and show how they can serve as the foundation for agile development approaches that work. Along the way, they introduce 22 "thinking tools" that can help you customize the right agile practices for any environment. Better, cheaper, faster software development. You can have all three-if you adopt the same lean principles that have already revolutionized manufacturing, logistics and product development. * Iterating towards excellence: software development as an exercise in discovery* Managing uncertainty: "decide as late as possible" by building change into the system.* Compressing the value stream: rapid development, feedback, and improvement * Empowering teams and individuals without compromising coordination* Software with integrity: promoting coherence, usability, fitness, maintainability, and adaptability * How to "see the whole"-even when your developers are scattered across multiple locations and contractors Simply put, Lean Software Development helps you refocus development on value, flow, and people-so you can achieve breakthrough quality, savings, speed, and business alignment.

Wird oft zusammen gekauft

Lean Software Development: An Agile Toolkit for Software Development Managers + Implementing Lean Software Development: From Concept to Cash (Addison-Wesley Signature) + Leading Lean Software Development: Results are Not the Point (Addison-Wesley Signature)
Preis für alle drei: EUR 99,85

Die ausgewählten Artikel zusammen kaufen


Produktinformation

  • Taschenbuch: 240 Seiten
  • Verlag: Addison Wesley; Auflage: 1. A. (8. Mai 2003)
  • Sprache: Englisch
  • ISBN-10: 0321150783
  • ISBN-13: 978-0321150783
  • Größe und/oder Gewicht: 23,1 x 17,8 x 1,3 cm
  • Durchschnittliche Kundenbewertung: 5.0 von 5 Sternen  Alle Rezensionen anzeigen (3 Kundenrezensionen)
  • Amazon Bestseller-Rang: Nr. 70.074 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
  • Komplettes Inhaltsverzeichnis ansehen

Mehr über den Autor

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

Produktbeschreibungen

Synopsis

Lean Software Development: An Agile Toolkit Mary Poppendieck Tom Poppendieck Forewords by Jim Highsmithand Ken Schwaber *Adapting agile practices to your development organization *Uncovering and eradicating waste throughout the software development lifecycle *Practical techniques for every development manager, project manager, and technical leaderLean Software Development: An Agile Toolkit Lean software development: applying agile principles to your organization In Lean Software Development, Mary and Tom Poppendieck identify seven fundamental "lean" principles, adapt them for the world of software development, and show how they can serve as the foundation for agile development approaches that work. Along the way, they introduce 22 "thinking tools" that can help you customize the right agile practices for any environment. Better, cheaper, faster software development. You can have all three--if you adopt the same lean principles that have already revolutionized manufacturing, logistics and product development.

*Iterating towards excellence: software development as an exercise in discovery *Managing uncertainty: "decide as late as possible" by building change into the system.*Compressing the value stream: rapid development, feedback, and improvement *Empowering teams and individuals without compromising coordination *Software with integrity: promoting coherence, usability, fitness, maintainability, and adaptability *How to "see the whole"--even when your developers are scattered across multiple locations and contractors Simply put, Lean Software Development helps you refocus development on value, flow, and people--so you can achieve breakthrough quality, savings, speed, and business alignment.

Buchrückseite

Lean Software Development: An Agile Toolkit

Mary Poppendieck Tom Poppendieck

Forewords by Jim Highsmithand Ken Schwaber

  • Adapting agile practices to your development organization
  • Uncovering and eradicating waste throughout the software development lifecycle
  • Practical techniques for every development manager, project manager, and technical leader
Lean Software Development: An Agile Toolkit

Lean software development: applying agile principles to your organization

In Lean Software Development, Mary and Tom Poppendieck identify seven fundamental "lean" principles, adapt them for the world of software development, and show how they can serve as the foundation for agile development approaches that work. Along the way, they introduce 22 "thinking tools" that can help you customize the right agile practices for any environment.

Better, cheaper, faster software development. You can have all three—if you adopt the same lean principles that have already revolutionized manufacturing, logistics and product development.

  • Iterating towards excellence: software development as an exercise in discovery
  • Managing uncertainty: "decide as late as possible" by building change into the system.
  • Compressing the value stream: rapid development, feedback, and improvement
  • Empowering teams and individuals without compromising coordination
  • Software with integrity: promoting coherence, usability, fitness, maintainability, and adaptability
  • How to "see the whole"—even when your developers are scattered across multiple locations and contractors

Simply put, Lean Software Development helps you refocus development on value, flow, and people—so you can achieve breakthrough quality, savings, speed, and business alignment.


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
Hier reinlesen und suchen:

Kundenrezensionen

4 Sterne
0
3 Sterne
0
2 Sterne
0
1 Sterne
0
5.0 von 5 Sternen
5.0 von 5 Sternen
Die hilfreichsten Kundenrezensionen
8 von 8 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen Denkwerkzeuge für die Just-in-Time Softwareentwicklung 14. November 2003
Format:Taschenbuch
Ein empfehlenswertes Buch in der Flut von Agilitätsbüchern ist Lean Software Development. Mit Idee übertragen die Poppendiecks die Leanproduction-Prinzipien auf die Softwareentwicklung und erklären damit, warum Extreme Programming und Konsorten funktioniert.
Oder besser: gleich die Originale lesen und eigene Schlüsse ziehen:
- Taiichi Ohno: Toyota Production System
- Donald Reinertsen: Managing the Design Factory
- James Womack, Daniel Jones, Daniel Roos: The Machine that changed the World
War diese Rezension für Sie hilfreich?
9 von 10 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen Einfach verständliche Theorie für ebensolche Praxis 7. September 2004
Format:Taschenbuch
Mary und Tom Poppendieck haben es geschafft, agile Vorgehensweisen auf ein einfach verständliches Podest von theoretischen Grundlagen zu heben.
Sie gehen von Prinzipien des "Lean Manufacturing" aus, übersetzen die Prinzipien in die Domäne der Anwendungsentwicklung. Sie weisen explizit darauf hin, dass ein einfaches Übernehmen der Praktiken aus anderen Domänen nur fehlschlagen kann, und geben sich deshalb viel Mühe, die richtigen Analogien für Praktiken aus dem Lean Manufacturing in der Anwendungsentwicklung zu finden.
Wenn das jetzt sehr kompliziert klingt, so ist es das Buch dafür überhaupt nicht.
In sieben Kapiteln werden die "Lean Principles" vorgestellt:
1. Eliminate Waste (whatever gets in the way of rapidly satisfying a customer need is waste)
2. Amplify learning (Development is an exercise in discovery, while production is an exercise in reducing variation)
3. Decide as late as possible (Delaying decisions is valuable because better decisions can be made when they are based on fact, not speculation)
4. Deliver as fast as possible (Design, implement, feedback, improve. The shorter these cycles are, the more can be learned.)
5. Empower the team (lean practices use pull techniques to schedule work and contain local signaling mechanisms so workers can let each other know what needs to be done.)
6. Build integrity in (Integrity comes from wise leadership, relevant expertise, effective communication, and healthy discipline.)
7. See the whole (When individuals or organizations are measured on their specialized contribution rather than overall performance, suboptimization is likely to result.
Lesen Sie weiter... ›
War diese Rezension für Sie hilfreich?
1 von 2 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen A must read! 21. Oktober 2003
Von Ein Kunde
Format:Taschenbuch
This book tries to bring lean production principles to the software development
field. And what can I say, it is an eye opener. It gives you the theoretic
background and principles how to succeed in software development. It doesn't offer
a method or a process, but the foundation and tools you need to understand how
SW development should be (and unfortunately it most of the time isn't that way).
So in my eyes it's a much more timeless and important book, as it doesn't try to
give us a new methodology but the fundations we needed and haven't had. After reading
this book you understand why waterfall and all the heavy weight stuff simply can't
work and never will. No matter how hard we try.
War diese Rezension für Sie hilfreich?
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
Amazon.com: 4.6 von 5 Sternen  53 Rezensionen
67 von 70 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen Excellent book that teaches how to think agilely 1. Juni 2003
Von Michael Cohn - Veröffentlicht auf Amazon.com
Format:Taschenbuch
Books written during the first phase of agile software development have been about very specific practices we should employ. There are some excellent books on the Extreme Programming, Feature-Driven Development and Scrum agile processes. These books teach us "do a, b, and c if you want to do Extreme Programming" or "do x, y and z if you want to do Scrum."
In the last year we've seen books by Highsmith (Agile Software Development Ecosystems) and Cockburn (Agile Software Development) that represent the second wave of agile software development-that of learning to think agilely rather than following a prescribed set of agile rules. Mary and Tom Poppendieck's book is the latest and best book for teaching how to think agilely.
The book contains 22 "thinking tools." The thinking tools are drawn from the world of lean manufacturing where they have helped improve product delivery speed, quality and cost. Each tool is presented as a guideline. Each thinking tool is described with enough detail that you can put it into practice; but, more importantly, the reasons supporting each are made explicit. So, instead of simply reading that it is good to "deliver as fast as possible" we learn how rapid delivery is supported by pull systems (where work is pulled into the current step from the prior step), how queuing theory helps us identify bottlenecks, and how to calculate the cost of delay (to see which bottlenecks are worth removing).
This book is the perfect blend of highly actionable instructions and descriptions of why those actions work. I highly recommend this book to anyone who wishes to improve his or her software development process. The authors' ideas are applicable both to projects using agile approaches today and to more traditional, plan-driven projects.
34 von 34 Kunden fanden die folgende Rezension hilfreich
4.0 von 5 Sternen A good, practical book 17. Mai 2006
Von Mark Meuer - Veröffentlicht auf Amazon.com
Format:Taschenbuch
Our reading group at work recently read "Lean Software Development." There are several things I really like about this book:

1. Its thinking is clearer than most. The Poppendiecks make sharp distinctions between principles, tools, and practices. (More on this will follow.)

2. It presents an Agile approach without demanding that one follow all tenets of Extreme Programming (such as pair programming).

3. It recognizes that in the past it has been a mistake to think of software development as being roughly analogous to manufacturing. Creating custom software is not very much like assembling cars within a factory.. Software development is much closer to product development, much more like the work that goes into designing the car in the first place. Principles (not necessarily techniques!) that work well in product design can have a much more straightforward application in software design.

4. They specifically address the needs of safety-critical software, talking about how to apply these principles in environments that are heavily regulated or where a software failure may endanger lives.

The book does suffer at times from and affliction common to this genre: over-enthusiasm. There can be a sense that all we need to do is follow what they say and all will be well. But, for the most part, the authors provide reasonable, realistic guidance for those looking to improve the way they go about creating software.

Now that we have the overview, let's look at the meat of the book: Agile principles. There are seven Agile principles which should govern a group's software development process:

1. Eliminate Waste

2. Amplify Learning

3. Decide as Late as Possible

4. Deliver as Fast as Possible

5. Empower the Team

6. Build Integrity In

7. See the Whole

A chapter is devoted to each principle. In each, the principle is described, examples are given from both product and software development, and a number of "tools" are suggested as ways to apply the principle in software development.

The principles are valid within any development effort, software or otherwise. For example, a good process will always seek reasonable ways to eliminate waste. In product development and manufacturing, waste may include scrap material that does not end up in a product. In software, the definition of "waste" will include things like partially done work, extra processes, extra features, waiting,

etc.

It is very important to keep the distinction between principles, tools, and techniques in mind. Principles must be reasonably applied to a given environment. The authors put it quite well: (pp. 179-180)

* Eliminate waste does not mean throw away all documentation.

* Amplify learning does not mean keep on changing your mind.

* Decide as late as possible does not mean procrastinate.

* Deliver as fast as possible does not mean rush and do sloppy work.

* Empower the team does not mean abandon leadership

* Build integrity in does not mean big, upfront design.

* See the whole does not mean ignore the details.

"One team's prescription is another team's poison. Do not arbitrarily adopt practices that work in other organizations; use the thinking tools in this book to translate lean principles into agile practices that match your environment."

I strongly recommend this book.
58 von 69 Kunden fanden die folgende Rezension hilfreich
2.0 von 5 Sternen Great Principles based on Bad Assumptions 8. Mai 2007
Von R. Lampereur - Veröffentlicht auf Amazon.com
Format:Taschenbuch
I am a senior software systems engineer working for an aerospace company. I recently read the Poppendicks' book and have mixed feelings about it. Overall they present some great lean development principles and tools that appear to be useful in boosting productivity in my software engineering organization. On the other hand, their understanding of CMM/CMMI is so off-base that it is hard for me to take them seriously as authors.

They misrepresented CMM several times in the book, so they either do not understand what CMM is and how it works, or they are intentionally misrepresenting it to "scare" people into using their lean software tools. The reality is that agile software development principles and tools fit perfectly into the CMM/CMMI models and the Poppendicks would have a much stronger book if they realized that. Rather than bashing CMM to make their tools seem more useful, they might do better if they realized that CMM/CMMI and lean software development can work perfectly together.

My advice to people interested in buying the book is to only read the book if you can take what the Poppendicks say with a grain of salt. Read about the lean principles/tools and think of how you could apply them in your software development environment. In the spirit of implementing the primary principle of lean development (i.e. eliminate waste), I would ignore the anecdotes they include in the book. They appear to be intentionally sensational while offering little value.
21 von 23 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen Learning from Lean Manufacturing 4. Juli 2003
Von Steve Berczuk - Veröffentlicht auf Amazon.com
Format:Taschenbuch
This is an excellent discussion of how the principles of Lean Manufacturing apply to Software Development. The authors explain why the usual metaphor of software as manufacturing is not quite right, and why the metaphor of Lean Manufacturing is something we can learn from. The book is clearly written and the authors provide examples and anecdotes to help you to understand their points. This was a fairly quick read, and I am likely to refer to it often.
10 von 10 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen Not just for Agile Development 22. Juni 2004
Von Mike Tarrani - Veröffentlicht auf Amazon.com
Format:Taschenbuch
Although this book is from the Agile-series, the approach and advice extends to any methodology from the heavy (and still used) waterfall SDLC, to XP and agile methods.
Key steps in this book will show you how to streamline your development methodology in accordance with lean thinking:
- Eliminate waste by cutting the fat out of processes, reducing rework, viewing your SDLC as a value stream.
- Amplify learning, with an emphasis on iterative planning, feedback loops and team communications.
- Decide as late as possible, which is enabled by concurrent activities, depth-first versus breadth-first problem solving, and other effective tools and techniques.
- Deliver as fast as possible, based on analogies between manufacturing pull systems and scheduling, and how to accomplish the same in development.
- Empower the team, which is a fundamental element of lean thinking. The tools and techniques presented in this section of the book are a mixture of common sense, leadership and management.
- Build integrity in. If ever there were a direct connection between the lean thinking approach to manufacturing and software development, it is here. Tools and techniques given include model-driven development, refactoring and testing techniques.
- See the whole, which emphasizes system thinking, metrics, optimization, and the supporting tools and techniques.
Any or all of the above can be effectively applied to any SDLC or methodology and produce results. Lean thinking was developed by Toyota as a manufacturing paradigm, which has been extended through that company and is applied to business processes outside of the manufacturing domain. That this team of authors has applied it to software development is not as unnatural as it may seem at first glance given how vastly different software is to create versus cars, for example. But, the paradigm has been proven outside of manufacturing before this book was written, and the basic philosophy and principles can be applied - which this book evidences.
If you want to look at development from an entirely unique perspective purge the words agile, XP and any other methodology from your mind while reading this book. I can almost guarantee that you'll find something in every chapter that you can put to immediate use in your own organization. As an aside, a book on software testing that is consistent with lean thinking in many ways, and closely aligned to the content of this book is "Software Testing Fundamentals: Methods and Metrics" ISBN 047143020X.
Waren diese Rezensionen hilfreich?   Wir wollen von Ihnen hören.
Kundenrezensionen suchen
Nur in den Rezensionen zu diesem Produkt suchen

Kunden diskutieren

Das Forum zu diesem Produkt
Diskussion Antworten Jüngster Beitrag
Noch keine Diskussionen

Fragen stellen, Meinungen austauschen, Einblicke gewinnen
Neue Diskussion starten
Thema:
Erster Beitrag:
Eingabe des Log-ins
 

Kundendiskussionen durchsuchen
Alle Amazon-Diskussionen durchsuchen
   


Ähnliche Artikel finden


Ihr Kommentar