Lean Software Development: An Agile Toolkit. By Mary Poppendieck, Tom Poppendieck. Publisher: Addison Wesley. Pub Date: May 08, Lean Software. Development. An Agile Toolkit. Mary Poppendieck. Tom Poppendieck. Boston • San Francisco • New York • Toronto • Montreal. London • Munich. Lean Software Development: An Agile Toolkit In Lean Software Development, Mary and Tom Poppendieck identify seven fundamental “lean” principles, adapt.

Author: Kigalabar Shaktibei
Country: Bahamas
Language: English (Spanish)
Genre: Medical
Published (Last): 1 September 2008
Pages: 195
PDF File Size: 6.81 Mb
ePub File Size: 18.34 Mb
ISBN: 436-7-70640-352-6
Downloads: 27601
Price: Free* [*Free Regsitration Required]
Uploader: Dijar

I found that the principles were presented clearly and in a way that made a lot of sense. Jim Highsmith Foreword by. They provide great examples on why its important to empower the team to make the decisions rather than a top down approach. You can have all three– if you adopt the same lean principles that have already revolutionized manufacturing, logistics and product development.

Good book about lean in software development. When you have tough problems, increase feedback. Dec 31, Joni Kettunen rated it it was amazing Recommends it for: Return to Book Page. poopendieck

Lean Software Development: An Agile Toolkit [Book]

Decide as late as possible 4. Purpose A meaningful purpose inspires and energizes workers. Self- Determination – let the team make their own improvements, measure their own outcomes and treat people like volunteers Motivation – hard to summarise briefly, so many ideas in here about motivation and how to achieve it Leadership – master developers, project managers – given all the team decisions exactly what is the project manager left to do?

Focus on principles as these can be reused in a different environments – practices mostly cann Good book about lean in software development. Mar 23, Wojtek Erbetowski rated it it was amazing. There is no help in applying the principles outside of the confines of a small single customer product This is a somewhat poorly written and badly edited book intended to provide the basic grounding in so called “agile” processes for software development.


An important book considering how prevalent the outdated and inefficient model of mass production and associated management styles are in the software industry. Optional Scope Try This 8. Create a steady, even flow of work, pulled from a deep understanding of value. While it doesn’t come natural for many engineers, the authors strongly recommend the need of retrospectives and feedback which are important to course correct early and often.

There is a short mention about system thinking and the rest of the chapter is basically about agile contracts. I was half expecting a bit of Agile evangelism in the book but I didn’t poppendiekc much of that at all. There is no help in applying the principles outside of the confines of a small developmentt customer product focused team. Agjle great read on how to combine agile and lean. However, all lean principles explained in the book are still valid. The conversation should not be considered complete until it is expressed as a customer test.

The best feature of this book is that it relates core lean values to the software development process. You’ll discover the right questions to ask, the key issues to focus on, and techniques proven to work. What company doesn’t want energized workers, delighted customers, genuine efficiency, and breakthrough innovation? Quotes from Lean Software Dev To see what your friends thought of this book, please sign up. Now Poppedieck know about lean and like it very much.

Mar 10, Marko rated it liked it. This book has a higher level overview of implementing agile.

Think forward to the next generation. Open Preview See a Problem?

Apr 03, Brian Bohanon rated it it was amazing. Appreciate the Entire Value Stream I was not really aware at all of all the ground breaking work done in Toyota and how it can be applied in lots of different industries and settings. The tools presented are: The authors recommend delivering software as fast as possible.

  DTU 26.1 PDF

There is no such thing as a best practice. They don’t build Gantt charts, they create poppenfieck release plan with milestones, ensure design is change tolerant, ensure testing and integration are done during development not after and engage with outside team members such as service and support.

This is a must read and must have in your revelopment library. Find and fix defects the moment they occur. The whole book is based on an assumed model for a software project that is only narrowly applicable to real development.

Lean Software Development: An Agile Toolkit

I’m curious to try value stream mapping an A pithy but important book that takes the principles of Lean Agile Software Development and dives deeper into their overarching philosophy. Please include your surface mailing address and which DVDs you would like to purchase in your E-mail.

Truly excellent book on how software development can be applied properly, based on the experience at the Toyota. At the end o I found this book very interesting since the first few pages I read. They are about understanding the principles behind any particular buzz word, going back and working up from how to apply that principle to your environment. Chapter 8 Instructions and Warranty.

Expertise – particularly the importance of maintaining matrix structures that ensure there are communities of excellence. Deliver as fast as possible 5.