Lean Software Development shows software professionals how to achieve breakthrough quality, savings, speed, and business value by adapting the seven "lean" principles that have already revolutionized manufacturing and R&D. Drawing on 25+ years' experience leading enterprise projects, the authors show how to use these principles to create agile processes that work - because they're optimized for your environment.
Lean Software Development: An Agile Toolkit
and over one million other books are available for Amazon Kindle.
Learn more
FREE Two-Day Shipping for students on millions of items. Learn more |
| |||||||||||||||
 Sell Back Your Copy for $8.50
Whether you bought it on Amazon or somewhere else, you can sell it back through our Book Trade-In Program at the current price of $8.50.
Used Price$16.48
Trade-in Price$8.50
Price after
Trade-in$7.98 |
Book Description
Special Offers and Product Promotions
- Buy $50 in qualifying physical textbooks, get $2 in Amazon MP3 Credit. Here's how (restrictions apply)
Frequently Bought Together
Editorial Reviews
From the Back Cover
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: 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.
About the Author
MARY POPPENDIECK, Managing Director of the Agile Alliance (a leading non profit organization promoting agile software development), is a seasoned leader in both operations and new product development with more than 25 years of IT experience. She has led teams implementing solutions ranging from enterprise supply chain management to digital media, and built one of 3M's first Just-in-Time lean production systems. Mary is currently the President of Poppendieck LLC, a consulting firm specializing in bringing lean production techniques to software development.
TOM POPPENDIECK was creating systems to support concurrent development of commercial airliner navigation devices as early as 1985. Even then, the aerospace industry recognized that sequential development of product design, manufacturing process design and product support was costly and non-competitive. His subsequent experience in software product development, COTS implementation, and most recently as a coach, mentor, and enterprise architect support the same conclusion for software development. He currently assists organizations that need to improve their software development capabilities apply the lean principles and tools described in this book.
Product Details
Would you like to update product info or give feedback on images?
|
More About the Author
Discover books, learn about writers, read author blogs, and more.
Customer Reviews
Most Helpful Customer Reviews
62 of 65 people found the following review helpful
Format:Paperback
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.
30 of 30 people found the following review helpful
Format:Paperback
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.
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.
21 of 23 people found the following review helpful
Format:Paperback
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.
Most Recent Customer Reviews
Content that stands the test of time
"Lean Software Development: An Agile Toolkit" is not only an excellent introduction to lean principles, it also offers a great deal of wisdom about successful software leadership. Read more
Published on December 31, 2009 by Paul Brownell
Lean Software Development, an Agile Toolkit
Lean Software Development, an Agile Toolkit is the third book that I have read on agile development. Read more
Published on December 31, 2009 by Jay Paulson
A good read for anybody in business
Being new to Agile, I am a Project Manager with waterfall experience. I enjoyed the book Lean Software Development An Agile Toolkit by Mary & Tom Poppendieck. Read more
Published on December 31, 2009 by JHarmon
A slender introduction to lean
"Lean Software Development: An Agile Toolkit," by Mary and Tom
Poppendieck, is a good introduction to lean concepts and how they can
be applied to software development. Read more
Poppendieck, is a good introduction to lean concepts and how they can
be applied to software development. Read more
Published on December 30, 2009 by B. Rogers
Recommended Reading
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. Read more
Published on December 30, 2009 by David Wight
A Good Foundations Book
Lean Software Development - An Agile Toolkit is a good foundation book which guides you through the thought process to gain an understanding of the Lean Principles. Read more
Published on December 30, 2009 by Mark Ridlehuber
Tools for Systemic Thinking and Optimization
Not since I read Peter Senge's book "The Fifth Discipline" have I read a book that deals with the importance of systemic thinking as well. Read more
Published on December 27, 2009 by Scott Killen
Your first - First Book on Agile Development
This book is a great first read for you if you are ready to learn about "NEW" tools for developing a product that your customers are expecting in the expected time frame and with a... Read more
Published on December 11, 2008 by James C. Kazakavage
Excellent read
This is a great introduction to Lean software development principles. It makes a logical connection from lean product development and manufacturing systems to software development... Read more
Published on November 29, 2008 by Gary W. Fong
Comes complete with instructions and a warranty
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... Read more
Published on July 19, 2008 by Erik Gfesser
What Other Items Do Customers Buy After Viewing This Item?
Tags Customers Associate with This Product(What's this?)Click on a tag to find related items, discussions, and people.
|
Customer Discussions
|
This product's forum
Active discussions in related forums
Search Customer Discussions
|
Related forums
|
Listmania!
|
|
So You'd Like to...
|
|
Look for Similar Items by Category
- Books > Computers & Technology > Programming > Software Design, Testing & Engineering > Software Development
- Books > Computers & Technology > Software
- Books > New & Used Textbooks > Computer Science > Programming Languages
- Books > New & Used Textbooks > Computer Science > Software Design & Engineering
