Facebook Twitter Pinterest <Einbetten>
  • Alle Preisangaben inkl. USt
Auf Lager.
Verkauf und Versand durch Amazon. Geschenkverpackung verfügbar.
Gebraucht: Gut | Details
Verkauft von Warehouse Deals
Zustand: Gebraucht: Gut
Kommentar: Kleiner Schnitt oder Kratzer auf der Vorderseite. Kleine Falte oder kleiner Knick auf der Vorderseite. Mittlerer Schnitt oder Kratzer in der Rückseite. Kleine Falte oder kleiner Knick auf der Rückseite. Kleiner Fleck oder geringe Abnutzung auf den Seiten. Kleiner Schnitt oder Kratzer auf den Seiten. Kleine Falte oder kleiner Knick auf den Seiten. Amazon-Kundenservice und Rücknahmegarantie (bis zu 30 Tagen) bei jedem Kauf.
Möchten Sie verkaufen?
Zur Rückseite klappen Zur Vorderseite klappen
Hörprobe Wird gespielt... Angehalten   Sie hören eine Hörprobe des Audible Hörbuch-Downloads.
Mehr erfahren
Dieses Bild anzeigen

Lean Software Development: An Agile Toolkit for Software Development Managers (Englisch) Taschenbuch – 8. Mai 2003

5.0 von 5 Sternen 3 Kundenrezensionen

Alle 3 Formate und Ausgaben anzeigen Andere Formate und Ausgaben ausblenden
Preis
Neu ab Gebraucht ab
Kindle Edition
"Bitte wiederholen"
Taschenbuch
"Bitte wiederholen"
EUR 30,70
EUR 30,70 EUR 26,25
8 neu ab EUR 30,70 7 gebraucht ab EUR 26,25
click to open popover

Hinweise und Aktionen


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)
Gesamtpreis: EUR 113,64
Die ausgewählten Artikel zusammen kaufen

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.

  • Apple
  • Android
  • Windows Phone

Geben Sie Ihre Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.

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


Produktinformation

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.

Alle Produktbeschreibungen

Kundenrezensionen

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

Top-Kundenrezensionen

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
Kommentar 8 Personen fanden diese Informationen hilfreich. War diese Rezension für Sie hilfreich? Ja Nein Feedback senden...
Vielen Dank für Ihr Feedback.
Wir konnten Ihre Stimmabgabe leider nicht speichern. Bitte erneut versuchen
Missbrauch melden
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... ›
Kommentar 9 Personen fanden diese Informationen hilfreich. War diese Rezension für Sie hilfreich? Ja Nein Feedback senden...
Vielen Dank für Ihr Feedback.
Wir konnten Ihre Stimmabgabe leider nicht speichern. Bitte erneut versuchen
Missbrauch melden
Von Ein Kunde am 21. Oktober 2003
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.
Kommentar Eine Person fand diese Informationen hilfreich. War diese Rezension für Sie hilfreich? Ja Nein Feedback senden...
Vielen Dank für Ihr Feedback.
Wir konnten Ihre Stimmabgabe leider nicht speichern. Bitte erneut versuchen
Missbrauch melden

Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)

Amazon.com: 4.5 von 5 Sternen 59 Rezensionen
5.0 von 5 Sternen All project managers and technical leaders should memorize the principles referred in this book 29. Mai 2016
Von Marcos Vinicius - Veröffentlicht auf Amazon.com
Format: Kindle Edition Verifizierter Kauf
The book is must for project managers, technical leaders and everyone that has any intention of influence the software development process or the interaction with the client.
Main benefit for me it that it takes the discussion of project-level practices and explain the importance and the 'why's of those practices in a way that touches the mindset of high-level managers, directors, and even maybe the executive level of organizations.
1 von 1 Kunden fanden die folgende Rezension hilfreich
4.0 von 5 Sternen Recommended Reading 31. Dezember 2009
Von David Wight - Veröffentlicht auf Amazon.com
Format: Taschenbuch Verifizierter Kauf
It was seven years and many software projects ago when I first read this book. At the time, I was trying to get my arms around the rapidly emerging agile movement. I enjoyed reading and learning about the practices for XP, Scrum, Crystal and other methodologies. However, this book helped me see the bigger picture and introduced me to valuable concepts from lean manufacturing such as value stream mapping, set based development and pull systems.

The book also introduced me to a lean, systems-based way of approaching software development. Although I might have been pressed to enumerate all the principles and the tools in the book, I know that over the years I've applied many of them regularly- adapting them to fit the diverse domains and environments in which I worked. Over the years, my copy has became worn and dog-eared. It was marked with a yellow tag on the spine, my way of marking favorite books on my shelf. As such, it was often loaned out to others.

I recently re-read the book and was surprised how relevant it remains in 2009. A few of the specifics in the book are dated, such as its characterization of how CMM, CMMI and PMI relate to agile. However, most of the material, is not only relevant; it's often more applicable today than when it was originally written. The book is well organized, easy to read and filled with "pearls of wisdom". I'll continue to include it right next to Goldratt in my list of recommended reading.
2 von 2 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen The Best Introduction I've Read 31. Mai 2008
Von Amazon Customer - Veröffentlicht auf Amazon.com
Format: Taschenbuch Verifizierter Kauf
It's pretty much all been said by previous reviewers but this one is worth another accolade. As a CIO with over 20 years in software engineering, I've just about read it all, seen it all, tried it all. As a result I'm a big believer in Lean/Agile, and this is the best introduction I've come across. It's a nice, practical mix of principles and practices and touches on all the right themes.

A previous reviewer laments the authors' distaste for CMMI and PMI. For instance:

"Between PMI and CMM certification programs, a heavy emphasis on process definition and detailed, front-end planning seemed to dominate everyone's perception of best practices...spending a lot of time and getting the requirements right upfront was the way to do things `right the first time'...CMM, in its eagerness to standardize process, leaves out the heart of discovery and innovation..." Spot on.

As a PMP with CMMI experience, I couldn't agree more with the Poppendiecks' observations and concerns. They go on to say, "This is not to say that CMM and PMI are bad, but only that for anyone who has lived through the lean revolution, they tend to give the wrong flavor to a software development program." That "wrong flavor" is called "waterfall."

Of course there are Level 5 Agile shops out there, and the author's recognize that "CMM is not supposed to dictate approach, but only assess..." But here's the problem: "CMM programs...may standardize on less than ideal practices...they may be better implemented separate from--and after--process improvements."

This book is a must read for software development managers and other business execs pursuing the promise of an Agile company (vs. IT shop). I'll definitely be passing out a few copies!
7 von 7 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen Still Coming Back to this Title 3 Years Later 14. Februar 2006
Von Jean Tabaka - Veröffentlicht auf Amazon.com
Format: Taschenbuch Verifizierter Kauf
I bought Mary and Tom's book when it first came out in 2003 and knew immediately that it would have a lasting impact on my vocabulary around agile software development. Their view of applying lean thinking and lean development to software development gave the entire group of agile methodologies (Scrum, XP, Crystal Clear, etc.) something truly solid upon which to hang their collective hats. For my part, it gave me the theoretical background I lacked while also giving clear practical advice about how to apply the theory. Eliminate waste, amplify learning, delay commitment, delivery fast, empower the team, build integrity in, and see the whole. These are the 7 principles of Lean that are then applied directly into software development practices.

It is now several years later and I keep coming back to this title, not just for my own reference, but also for my clients. In my work as an Agile Mentor, this book is one of my all time top references. I recommend this book to developers, managers, executives, stakeholders, testers, customers, everyone! "Lean Software Development" gets this mighty nod from me because it provides straightforward language around productivity, revenue, and quality that helps all of these various roles understand the value of agile software development practices. When development teams eliminate waste daily, they eliminate waste from the overall product release. And when multiple teams eliminate waste from product releases, they are eliminating organizational waste. And with organizatinal waste tracked and eliminated, the entire organization enjoys higher quality and productivity. This progression of benefit occurs with all of the seven principles and the Poppendiecks give you the path to apply these bottom up or top down.

If you have but one book to choose in order to understand agile software development, start with "Lean Software Development". If your boss has only one book to choose in order to understand why YOU are interested in agile software development, have her start with "Lean Software Development".
4.0 von 5 Sternen Comes complete with instructions and a warranty 19. Juli 2008
Von Erik Gfesser - Veröffentlicht auf Amazon.com
Format: Taschenbuch Verifizierter Kauf
Shortly after leading my first Six Sigma process improvement project, which involved my constructing of software to automate client business processes, I came across this book by the Poppendiecks. At the time, the integration of Lean and Six Sigma seemed to be picking up steam, and rather than reading a general text on Lean, getting a better understanding of how to apply Lean to software development seemed to make sense. In reading through this book, although Lean and Six Sigma (now often called Lean Six Sigma) share some commonalities, it became quickly apparent that Lean shares much in common with practices set into motion by the agile software development movement. The introduction to this text lists seven Lean principles as applied to software development: eliminating waste, amplifying learning, deciding as late as possible, delivering as fast as possible, empowering the team, building integrity in, and seeing the whole. In addition, it is also indicated that the Lean principles, respectively, do not mean throwing away all documentation, continuously changing one's mind, procrastinating, rushing and delivering sloppy work, abandoning leadership, performing big upfront design, or ignoring the details. It is interesting that the authors wait until the last chapter to disclose what the authors deem as instructions and a warranty card. The authors caution the reader that "one team's prescription is another team's poison", one should "not arbitrarily adopt practices that work in other organizations", and "the right amount of features analysis and traceability depends on the nature of the system and the probability of change" just as "the right amount of user interaction design depends on the users of the system, their background, and how they might use the system". These cautionary notes present a reminder of what the Lean principles applied to software development are all about. The authors also briefly discuss such areas as "special work environments" like the government, where skeptics to agile methods are common. I would like to see the Poppendiecks (or someone else) write an entire book on special work environments. En route to the closing chapter, the authors present 22 tools to help customize the right agile practices for any particular environment. Much of the material will probably already be familiar to agile practitioners, but a substantial amount of the discussion is on Lean. Most of the diagrams presented are well done, although some are a bit amateurish and do not aid the associated discussions. Small case studies that are provided throughout the text are beneficial (although sometimes minimally so) in helping the reader understand the problem space as well as apply the tools. The first few chapters are well suited for an introduction to Lean, and the book in general is recommended for those interested in exploring how Lean might be incorporated into software development.
Waren diese Rezensionen hilfreich? Wir wollen von Ihnen hören.