• Tous les prix incluent la TVA.
En stock.
Expédié et vendu par Amazon. Emballage cadeau disponible.
Lean Software Development... a été ajouté à votre Panier
+ EUR 2,99 (livraison en France métropolitaine)
D'occasion: Très bon | Détails
Vendu par Nearfine
État: D'occasion: Très bon
Commentaire: Petites traces d'usage. Livraison prévue sous 20 jours.
Vous l'avez déjà ?
Repliez vers l'arrière Repliez vers l'avant
Ecoutez Lecture en cours... Interrompu   Vous écoutez un extrait de l'édition audio Audible
En savoir plus
Voir cette image

Lean Software Development: An Agile Toolkit (Anglais) Broché – 8 mai 2003

5.0 étoiles sur 5 1 commentaire client

Voir les 3 formats et éditions Masquer les autres formats et éditions
Prix Amazon
Neuf à partir de Occasion à partir de
Format Kindle
"Veuillez réessayer"
Broché
"Veuillez réessayer"
EUR 48,41
EUR 41,22 EUR 24,19
Note: Cet article est éligible à la livraison en points de collecte. Détails
Récupérer votre colis où vous voulez quand vous voulez.
  • Choisissez parmi 17 000 points de collecte en France
  • Les membres du programme Amazon Prime bénéficient de livraison gratuites illimitées
Comment commander vers un point de collecte ?
  1. Trouvez votre point de collecte et ajoutez-le à votre carnet d’adresses
  2. Sélectionnez cette adresse lors de votre commande
Plus d’informations

rentrée scolaire 2017 rentrée scolaire 2017

click to open popover

Offres spéciales et liens associés


Produits fréquemment achetés ensemble

  • Lean Software Development: An Agile Toolkit
  • +
  • Implementing Lean Software Development: From Concept to Cash
Prix total: EUR 91,43
Acheter les articles sélectionnés ensemble

Description du produit

Présentation de l'éditeur

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.

Quatrième de couverture

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.

Aucun appareil Kindle n'est requis. Téléchargez l'une des applis Kindle gratuites et commencez à lire les livres Kindle sur votre smartphone, tablette ou ordinateur.

  • Apple
  • Android
  • Windows Phone
  • Android

Pour obtenir l'appli gratuite, saisissez votre numéro de téléphone mobile.



Détails sur le produit


Quels sont les autres articles que les clients achètent après avoir regardé cet article?

Commentaires en ligne

5.0 étoiles sur 5
5 étoiles
1
4 étoiles
0
3 étoiles
0
2 étoiles
0
1 étoile
0
Voir le commentaire client
Partagez votre opinion avec les autres clients

Meilleurs commentaires des clients

L'évaluation d'un enfant le 11 septembre 2010
Format: Broché
Les fondements de la mouvance "Lean" de l'agilité.
Exposé très clair par les poppendieck.
Très intéressants.
Pas trop théorique.
Vraiment très bien
Remarque sur ce commentaire Avez-vous trouvé ce commentaire utile ? Oui Non Commentaire en cours d'envoi...
Merci pour votre commentaire.
Désolé, nous n'avons pas réussi à enregistrer votre vote. Veuillez réessayer
Signaler un abus

Commentaires client les plus utiles sur Amazon.com (beta) (Peut contenir des commentaires issus du programme Early Reviewer Rewards)

Amazon.com: 4.6 étoiles sur 5 60 commentaires
9 internautes sur 9 ont trouvé ce commentaire utile 
5.0 étoiles sur 5 Still Coming Back to this Title 3 Years Later 14 février 2006
Par Jean Tabaka - Publié sur Amazon.com
Format: Broché Achat vérifié
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".
5.0 étoiles sur 5 All project managers and technical leaders should memorize the principles referred in this book 29 mai 2016
Par Marcos Vinicius - Publié sur Amazon.com
Format: Format Kindle Achat vérifié
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 internautes sur 1 ont trouvé ce commentaire utile 
4.0 étoiles sur 5 Recommended Reading 31 décembre 2009
Par David Wight - Publié sur Amazon.com
Format: Broché Achat vérifié
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 internautes sur 2 ont trouvé ce commentaire utile 
5.0 étoiles sur 5 The Best Introduction I've Read 31 mai 2008
Par Amazon Customer - Publié sur Amazon.com
Format: Broché Achat vérifié
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!
4.0 étoiles sur 5 Comes complete with instructions and a warranty 19 juillet 2008
Par Erik Gfesser - Publié sur Amazon.com
Format: Broché Achat vérifié
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.
Ces commentaires ont-ils été utiles ? Dites-le-nous