Commencez à lire Implementing Lean Software Development: From Concept to Cash sur votre Kindle dans moins d'une minute. Vous n'avez pas encore de Kindle ? Achetez-le ici Ou commencez à lire dès maintenant avec l'une de nos applications de lecture Kindle gratuites.

Envoyer sur votre Kindle ou un autre appareil

 
 
 

Essai gratuit

Découvrez gratuitement un extrait de ce titre

Envoyer sur votre Kindle ou un autre appareil

Implementing Lean Software Development: From Concept to Cash
 
Agrandissez cette image
 

Implementing Lean Software Development: From Concept to Cash [Format Kindle]

Mary Poppendieck , Tom Poppendieck
4.0 étoiles sur 5  Voir tous les commentaires (1 commentaire client)

Prix conseillé : EUR 21,62 De quoi s'agit-il ?
Prix éditeur - format imprimé : EUR 41,57
Prix Kindle : EUR 15,13 TTC & envoi gratuit via réseau sans fil par Amazon Whispernet
Économisez : EUR 26,44 (64%)

App de lecture Kindle gratuite Tout le monde peut lire les livres Kindle, même sans un appareil Kindle, grâce à l'appli Kindle GRATUITE pour les smartphones, les tablettes et les ordinateurs.

Pour obtenir l'appli gratuite, saisissez votre adresse e-mail ou numéro de téléphone mobile.

Formats

Prix Amazon Neuf à partir de Occasion à partir de
Format Kindle EUR 15,13  
Broché EUR 42,84  



Le Pack de Noël: téléchargez gratuitement plus de 175€ de top applis et jeux avec l'App-Shop Amazon. Offre à durée limitée. En savoir plus.

Il est encore temps pour de faire vos cadeaux de Noël avec les chèques-cadeaux Amazon.fr par email ou à imprimer.



Descriptions du produit

Présentation de l'éditeur

"This remarkable book combines practical advice, ready-to-use techniques, anda deep understanding of why this is the right way to develop software. I haveseen software teams transformed by the ideas in this book."

--Mike Cohn, author of Agile Estimating and Planning

"As a lean practitioner myself, I have loved and used their first book for years.When this second book came out, I was delighted that it was even better. If youare interested in how lean principles can be useful for software developmentorganizations, this is the book you are looking for. The Poppendiecks offer abeautiful blend of history, theory, and practice."

--Alan Shalloway, coauthor of Design Patterns Explained

"I've enjoyed reading the book very much. I feel it might even be better than thefirst lean book by Tom and Mary, while that one was already exceptionallygood! Mary especially has a lot of knowledge related to lean techniques inproduct development and manufacturing. It's rare that these techniques areactually translated to software. This is something no other book does well(except their first book)."

--Bas Vodde

"The new book by Mary and Tom Poppendieck provides a well-written andcomprehensive introduction to lean principles and selected practices for softwaremanagers and engineers. It illustrates the application of the values andpractices with well-suited success stories. I enjoyed reading it."

--Roman Pichler

"In Implementing Lean Software Development, the Poppendiecks explore moredeeply the themes they introduced in Lean Software Development. They beginwith a compelling history of lean thinking, then move to key areas such asvalue, waste, and people. Each chapter includes exercises to help you apply keypoints. If you want a better understanding of how lean ideas can work withsoftware, this book is for you."

--Bill Wake, independent consultant

In 2003, Mary and Tom Poppendieck's Lean Software Development introduced breakthrough development techniques that leverage Lean principles to deliver unprecedented agility and value. Now their widely anticipated sequel and companion guide shows exactly how to implement Lean software development, hands-on.

This new book draws on the Poppendiecks' unparalleled experience helping development organizations optimize the entire software value stream. You'll discover the right questions to ask, the key issues to focus on, and techniques proven to work. The authors present case studies from leading-edge software organizations, and offer practical exercises for jumpstarting your own Lean initiatives.

  • Managing to extend, nourish, and leverage agile practices
  • Building true development teams, not just groups
  • Driving quality through rapid feedback and detailed discipline
  • Making decisions Just-in-Time, but no later
  • Delivering fast: How PatientKeeper delivers 45 rock-solid releases per year
  • Making tradeoffs that really satisfy customers
Implementing Lean Software Development is indispensable to anyone who wants more effective development processes--managers, project leaders, senior developers, and architects in enterprise IT and software companies alike.

Quatrième de couverture

"This remarkable book combines practical advice, ready-to-use techniques, anda deep understanding of why this is the right way to develop software. I haveseen software teams transformed by the ideas in this book."

--Mike Cohn, author of Agile Estimating and Planning

"As a lean practitioner myself, I have loved and used their first book for years.When this second book came out, I was delighted that it was even better. If youare interested in how lean principles can be useful for software developmentorganizations, this is the book you are looking for. The Poppendiecks offer abeautiful blend of history, theory, and practice."

--Alan Shalloway, coauthor of Design Patterns Explained

"I've enjoyed reading the book very much. I feel it might even be better than thefirst lean book by Tom and Mary, while that one was already exceptionallygood! Mary especially has a lot of knowledge related to lean techniques inproduct development and manufacturing. It's rare that these techniques areactually translated to software. This is something no other book does well(except their first book)."

--Bas Vodde

"The new book by Mary and Tom Poppendieck provides a well-written andcomprehensive introduction to lean principles and selected practices for softwaremanagers and engineers. It illustrates the application of the values andpractices with well-suited success stories. I enjoyed reading it."

--Roman Pichler

"In Implementing Lean Software Development, the Poppendiecks explore moredeeply the themes they introduced in Lean Software Development. They beginwith a compelling history of lean thinking, then move to key areas such asvalue, waste, and people. Each chapter includes exercises to help you apply keypoints. If you want a better understanding of how lean ideas can work withsoftware, this book is for you."

--Bill Wake, independent consultant

In 2003, Mary and Tom Poppendieck's Lean Software Development introduced breakthrough development techniques that leverage Lean principles to deliver unprecedented agility and value. Now their widely anticipated sequel and companion guide shows exactly how to implement Lean software development, hands-on.

This new book draws on the Poppendiecks' unparalleled experience helping development organizations optimize the entire software value stream. You'll discover the right questions to ask, the key issues to focus on, and techniques proven to work. The authors present case studies from leading-edge software organizations, and offer practical exercises for jumpstarting your own Lean initiatives.

  • Managing to extend, nourish, and leverage agile practices
  • Building true development teams, not just groups
  • Driving quality through rapid feedback and detailed discipline
  • Making decisions Just-in-Time, but no later
  • Delivering fast: How PatientKeeper delivers 45 rock-solid releases per year
  • Making tradeoffs that really satisfy customers
Implementing Lean Software Development is indispensable to anyone who wants more effective development processes--managers, project leaders, senior developers, and architects in enterprise IT and software companies alike.


Détails sur le produit

  • Format : Format Kindle
  • Taille du fichier : 4610 KB
  • Nombre de pages de l'édition imprimée : 304 pages
  • Utilisation simultanée de l'appareil : Jusqu'à  appareils simultanés, selon les limites de l'éditeur
  • Editeur : Addison-Wesley Professional; Édition : 1 (1 septembre 2006)
  • Vendu par : Amazon Media EU S.à r.l.
  • Langue : Anglais
  • ASIN: B00HNB3VQE
  • Synthèse vocale : Activée
  • X-Ray :
  • Word Wise: Non activé
  • Moyenne des commentaires client : 4.0 étoiles sur 5  Voir tous les commentaires (1 commentaire client)
  • Classement des meilleures ventes d'Amazon: n°141.204 dans la Boutique Kindle (Voir le Top 100 dans la Boutique Kindle)
  •  Souhaitez-vous faire modifier les images ?


En savoir plus sur l'auteur

Découvrez des livres, informez-vous sur les écrivains, lisez des blogs d'auteurs et bien plus encore.

Commentaires en ligne

5 étoiles
0
3 étoiles
0
2 étoiles
0
1 étoiles
0
4.0 étoiles sur 5
4.0 étoiles sur 5
Commentaires client les plus utiles
4.0 étoiles sur 5 Riche mais complexe 20 octobre 2012
Par Kogaratsu
Format:Broché|Achat vérifié
La suite logique du premier tome. Très intéressant, mais pas si facile que ça à mettre en pratique. Ces 2 livres restent la référence sur le Lean Software Dev, et restent des "must read"
Avez-vous trouvé ce commentaire utile ?
Commentaires client les plus utiles sur Amazon.com (beta)
Amazon.com: 4.6 étoiles sur 5  23 commentaires
76 internautes sur 86 ont trouvé ce commentaire utile 
3.0 étoiles sur 5 Find a leaner book 4 avril 2007
Par James - Publié sur Amazon.com
Format:Broché|Achat vérifié
While the book contains many interesting ideas, it is very tedious reading; an in-depth article could have adequately covered the same material. The book is often fairly repetitious with the same story used to make the same point in multiple places. While the title might lead one to expect a fairly "applied" book ("Implementing" and "concept to cash", the actual purpose is to sell you on the concept of lean software development.

The authors like to bring in real-world examples to help bolster their arguments but frequently get the facts or their interpretation wrong. While the authors need not be experts in areas outside their expertise, one would expect that they would fact-check the basis of some fairly definitive statements; here are some examples: "... 16 is the standard number of missiles in a submarine to this day" (wrong since 1979 when first 24 missile Trident sub was launched); "... in 1985 the value of the yen started its steep fall" (actually the value of the yen rose). Nitpicking?---perhaps, but I find them wrong on areas that I know a little bit about, it makes me wonder how well they are doing when citing knowledge that is unfamiliar to me.

The authors belittle an "efficient expert" (the subject of "Cheaper by the Dozen") for believing there is only one way to efficiently do things. They later turn around and advocate that all developers be subjected to inspections---not inspections of their software but inspections of their desks to insure that they are tidy. They opine that a developer with a messy desk will probably be responsible for messy software; do they feel that a little maid-service will massively reduce software defects? (Why is it that morning people and neat-freaks always so self-righteous?). Sounds pretty "one-way" to me.

The bottom line is that you could probably find a good article in print somewhere that would provide you with most of the content here saving both time and money (sounds like the "lean" way to do things). Still you will get some value for your time and money if you do invest in this book.
17 internautes sur 17 ont trouvé ce commentaire utile 
4.0 étoiles sur 5 Another terrific book on Lean/Agile 16 octobre 2006
Par James Holmes - Publié sur Amazon.com
Format:Broché
This book is a great follow-on to the Poppendieck's "Lean Software Development" book. That book gave readers "an Agile Toolkit" for understanding what lean and agile are all about. This book is similar to its predecessor both in tone and content with practical examples of what works and what doesn't. Much of the book is still framed by lessons learned from Toyota's manufacturing system and Mary Poppendieck's experience at 3M.

That said, the book isn't just a rehash of the earlier, seminal work. This book seems to have a solid core of how to get the most out of development teams with two sections specific to people and partners. There are also terrific sections on knowledge-sharing, speed, and how to get the highest quality while delivering in a rapid and lean fashion. Some things aren't covered at all, such as the fundamentals of value stream or Pareto charts, but those areas are by far the minority.

One other reviewer remarked about the lack of anything specific to Extreme Programming, but I think that's missing the point a bit: this book isn't about a specific implementation of agile/lean/whatever, it's about the general approach to the principles of lean development. The book guides readers to explore what's not working in their own environment and alter bits and pieces to improve production. An example of this is the closing section to each chapter where a "Try This" section guides readers to examine how their own environment is working or not working.

Folks who have done plenty of reading on agile/lean concepts may not find anything earth-shattering in this book, but it's a terrific read for anyone regardess of their exposure to and involvement in agile. Well-steeped readers will find lots of head-nodding stories and a few provoking exercises and topics. Newcomers will have their eyes opened by a wealth of riches.
19 internautes sur 23 ont trouvé ce commentaire utile 
5.0 étoiles sur 5 An amazing collection of practical advice you can use tomorrow 19 septembre 2006
Par Michael Cohn - Publié sur Amazon.com
Format:Broché
I've long considered Mary and Tom Poppendieck to be among the primary theoreticians in the agile software development movement. Their first book, Lean Software Development, provided insights into the theory behind agile software development. That first book has been widely praised for helping those of us doing agile software development know why what we were doing worked.

With their new book, Implementing Lean Software Development: From Concept to Cash, the Poppendiecks move their ideas a giant leap forward. In this book they move very much from theory straight into what teams should do tomorrow to create better products. The book is full of practical, agile- or lean-minded, do-this-tomorrow advice on topics such as how to solve problems, how to structure compensation and recognition programs, how to get started on a lean initiative, how to write contracts for agile projects, and many more. The practicality of the book is reinforced by the "Try This" exercises that conclude each chapter.

The book starts out with a wonderful description of their seven principles of lean software development. For each principle they single out and dispel a common myth associated with the principle. Their description of the principle "build quality in," for example, includes a highly effective argument against the myth that the job of testing is to find defects.

The book then moves on to chapters on value, waste, people, knowledge, quality, and partners before concluding with a chapter on the journey ahead for companies embracing the theory and the practical advice given in this wonderful book.
12 internautes sur 14 ont trouvé ce commentaire utile 
5.0 étoiles sur 5 Relating software development to manufacturing... 25 septembre 2006
Par Thomas Duff - Publié sur Amazon.com
Format:Broché
I don't think I've ever tried to fit software development into the model of lean manufacturing techniques. But surprisingly, it has a number of parallels, and they are outlined well in the book Implementing Lean Software Development - From Concept to Cash by Mary and Tom Poppendieck.

Contents: History; Principles; Values; Waste; Speed; People; Knowledge; Quality; Partners; Journey; Bibliography; Index

The authors take the Deming-type principles of manufacturing and show how they relate to agile software development, using many of the same concepts and terms that have been handed down to us from the Japanese methodologies that revolutionized manufacturing. For instance, Shingo's seven wastes of manufacturing get translated into the seven wastes of software development: In-Process Inventory (Partially Done Work), Over-Production (Extra Features), Extra Processing (Relearning), Transportation (Handoffs), Motion (Task Switching), Waiting (Delays), and Defects (Defects). To take one of them specifically... Over-production is the making of product that isn't immediately needed. It builds up, costs money to store and maintain, and may never be used if the requirements change before the product is used. Likewise, extra features in software, ones not needed to get the customer's job done, should be avoided at all costs. It's code that needs to be maintained, it can break software that *is* essential, and the requirements for the feature may change dramatically by the time it is actually requested. Granted, these are guidelines and not hard-and-fast rules, but they make a lot of sense in terms of making the software development process more efficient and productive.

Both authors have a manufacturing background in their software development past, so the content is liberally sprinkled with real-life examples of these guidelines as they have played out in companies. It's amazing how we accept things in software development that we would never stand for in a well-run manufacturing set-up (such as running your "machines" over 100% capacity for long periods of time... sound familiar?)

If you're having a hard time getting your organization to give "agile" methodologies a try, you might want to reframe the discussion around "lean" software development. You could break out of the language misconceptions and discover new insights. This book can help you make that leap...
4 internautes sur 4 ont trouvé ce commentaire utile 
5.0 étoiles sur 5 Inspiring and Fat Free 13 avril 2009
Par Malcolm Gorman - Publié sur Amazon.com
Format:Broché
Some of this is so counter-intuitive. But once I began reading, I could see waste in software development where before I had seen good process. Just the concept of unfinished software as Inventory has caused me to rethink my previous willingness (even eagerness) to accommodate context switches between different projects. If the project being switched from has not issued a new iteration of the software, then there is wasted functionality that might have been providing value to users if it had been finished, just sitting on a "shelf" gathering dust. And the further cost of getting back up to speed on that project to transform partly finished work into deliverable software.

I would like to recommend also these other two lean books Lean Thinking : Banish Waste and Create Wealth in Your Corporation, Revised and Updated and The Machine That Changed the World: The Story of Lean Production-- Toyota's Secret Weapon in the Global Car Wars That Is Now Revolutionizing World Industry which go into the research and rational behind the concepts in this book. It will sort out your doubts.

I found myself reading this book during coffee breaks. It's a great read.
Ces commentaires ont-ils été utiles ?   Dites-le-nous
Rechercher des commentaires
Rechercher uniquement parmi les commentaires portant sur ce produit

Discussions entre clients

Le forum concernant ce produit
Discussion Réponses Message le plus récent
Pas de discussions pour l'instant

Posez des questions, partagez votre opinion, gagnez en compréhension
Démarrer une nouvelle discussion
Thème:
Première publication:
Aller s'identifier
 

Rechercher parmi les discussions des clients
Rechercher dans toutes les discussions Amazon
   


Rechercher des articles similaires par rubrique