did-you-know? rent-now

Amazon no longer offers textbook rentals. We do!

did-you-know? rent-now

Amazon no longer offers textbook rentals. We do!

We're the #1 textbook rental company. Let us show you why.

9780321437389

Implementing Lean Software Development From Concept to Cash

by ;
  • ISBN13:

    9780321437389

  • ISBN10:

    0321437381

  • Edition: 1st
  • Format: Paperback
  • Copyright: 2006-09-07
  • Publisher: Addison-Wesley Professional

Note: Supplemental materials are not guaranteed with Rental or Used book purchases.

Purchase Benefits

  • Free Shipping Icon Free Shipping On Orders Over $35!
    Your order must be $35 or more to qualify for free economy shipping. Bulk sales, PO's, Marketplace items, eBooks and apparel do not qualify for this offer.
  • eCampus.com Logo Get Rewarded for Ordering Your Textbooks! Enroll Now
  • Complimentary 7-Day eTextbook Access - Read more
    When you rent or buy this book, you will receive complimentary 7-day online access to the eTextbook version from your PC, Mac, tablet, or smartphone. Feature not included on Marketplace Items.
List Price: $49.99 Save up to $19.12
  • Rent Book $30.87
    Add to Cart Free Shipping Icon Free Shipping

    TERM
    PRICE
    DUE

    7-Day eTextbook Access 7-Day eTextbook Access

    USUALLY SHIPS IN 24-48 HOURS
    *This item is part of an exclusive publisher rental program and requires an additional convenience fee. This fee will be reflected in the shopping cart.

Supplemental Materials

What is included with this book?

Summary

"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. bull; bull;Managing to extend, nourish, and leverage agile practices bull;Building true development teams, not just groups bull;Driving quality through rapid feedback and detailed discipline bull;Making decisions Just-in-Time, but no later bull;Delivering fast: How PatientKeeper delivers 45 rock-solid releases per year bull;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.

Author Biography

Mary Poppendieck is a seasoned leader in operations and product development with more than thirty 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 the president of Poppendieck LLC, which specializes in bringing Lean techniques to software development.

Tom Poppendieck is an enterprise analyst, architect, and agile process mentor with more than twenty-five years of experience developing and implementing complex systems. He currently assists organizations in applying Lean principles and tools to software development processes.



Table of Contents

Foreword by Jeff Sutherland xvii
Foreword by Kent Beck xx
Preface xxiii
Chapter 1: History 1(18)
Interchangeable Parts
1(1)
Interchangeable People
2(1)
The Toyodas
3(1)
The Toyota Production System
4(3)
Taiichi Ohno
5(1)
Just-in-Time How
5(1)
Autonomation (Jidoka)
5(1)
Shigeo Shingo
6(5)
Nonstock Production
6(1)
Zero Inspection
6(1)
Just-in-Time
7(4)
Lean
11(6)
Lean Manufacturing/Lean Operations
11(1)
Lean Supply Chain
12(1)
Lean Product Development
13(4)
Lean Software Development
17(1)
Try This
17(2)
Chapter 2: Principles 19(24)
Principles and Practices
19(4)
Software Development
20(3)
Software
20(1)
Development
21(2)
The Seven Principles of Lean Software Development
23(19)
Principle 1: Eliminate Waste
23(2)
Myth: Early Specification Reduces Waste
24(1)
Principle 2: Build Quality In
25(4)
Myth: The Job of Testing Is to Find Defects
28(1)
Principle 3: Create Knowledge
29(3)
Myth: Predictions Create Predictability
31(1)
Principle 4: Defer Commitment
32(2)
Myth: Planning Is Commitment
33(1)
Principle 5: Deliver Fast
34(2)
Myth: Haste Makes Waste
35(1)
Principle 6: Respect People
36(2)
Myth: There Is One Best Way
37(1)
Principle 7: Optimize the Whole
38(5)
Myth: Optimize By Decomposition
40(2)
Try This
42(1)
Chapter 3: Value 43(24)
Lean Solutions
43(6)
Google
43(3)
From Concept to Cash
46(3)
Concept
46(1)
Feasibility
46(2)
Pilot
48(1)
Cash
49(1)
Delighted Customers
49(3)
Deep Customer Understanding
50(1)
Focus on the Job
51(1)
The Customer-Focused Organization
52(8)
Leadership
52(5)
The Chief Engineer
53(2)
Leadership Team
55(1)
Shared Leadership
56(1)
Who's Responsible?
56(1)
Complete Teams
57(3)
Design for Operations
58(2)
Custom Development
60(5)
From Projects to Products
60(2)
IT—Business Collaboration
62(5)
Accountability
64(1)
Try This
65(2)
Chapter 4: Waste 67(28)
Write Less Code
67(6)
Zara
67(2)
Complexity
69(4)
Justify Every Feature
70(1)
Minimum Useful Feature Sets
71(1)
Don't Automate Complexity
72(1)
The Seven Wastes
73(10)
Partially Done Work
74(1)
Extra Features
75(1)
Relearning
76(1)
Handoffs
77(1)
Task Switching
78(2)
Delays
80(1)
Defects
81(2)
Mapping the Value Stream
83(9)
Preparation
83(2)
Choose a Value Stream
83(1)
Choose When to Start and Stop the Timeline
84(1)
Identify the Value Stream Owner
84(1)
Keep It Simple
85(1)
Examples
85(7)
Example 1
86(1)
Example 2
86(2)
Example 3
88(1)
Example 4
89(2)
Diagnosis
91(1)
Future Value Stream Maps
92(1)
Try This
92(3)
Chapter 5: Speed 95(22)
Deliver Fast
95(5)
Patient Keeper
95(3)
Time: The Universal Currency
98(2)
Queuing Theory
100(14)
Little's Law
100(1)
Variation and Utilization
101(2)
Reducing Cycle Time
103(14)
Even Out the Arrival of Work
103(2)
Minimize the Number of Things in Process
105(2)
Minimize the Size of Things in Process
107(1)
Establish a Regular Cadence
108(2)
Limit Work to Capacity
110(2)
Use Pull Scheduling
112(2)
Summary
114(1)
Try This
114(3)
Chapter 6: People 117(32)
A System of Management
117(9)
The Boeing 777
117(3)
W. Edwards Deming
120(4)
Why Good Programs Fail
124(2)
Teams
126(10)
What Makes a Team?
126(6)
Leadership
132(1)
Responsibility-Based Planning and Control
133(3)
The Visual Workspace
136(5)
Self-Directing Work
137(4)
Kanban
138(1)
Andon
139(1)
Dashboard
140(1)
Incentives
141(6)
Performance Evaluations
141(2)
Ranking
142(1)
Compensation
143(6)
Guideline No. 1: Make Sure the Promotion System Is Unassailable
143(1)
Guideline No. 2: De-emphasize Annual Raises
144(1)
Guideline No. 3: Reward Based on Span of Influence, Not Span of Control
144(1)
Guideline No. 4: Find Better Motivators Than Money
145(2)
Try This
147(2)
Chapter 7: Knowledge 149(28)
Creating Knowledge
149(10)
Rally
149(3)
What, Exactly, Is Your Problem?
152(2)
A Scientific Way of Thinking
154(1)
Keeping Track of What You Know
155(4)
The A3 report
157(2)
The Internet Age
159(1)
Just-in-Time Commitment
159(9)
Set-Based Design
160(4)
Example 1: Medical Device Interface Design
162(1)
Example 2: Red-Eye Reduction
162(1)
Example 3: Pluggable Interfaces
163(1)
Why Isn't This Waste?
164(1)
Refactoring
164(4)
Legacy Systems
166(2)
Problem Solving
168(7)
A Disciplined Approach
169(4)
1. Define the Problem
169(1)
2. Analyze the Situation
169(2)
3. Create a Hypothesis
171(1)
4. Perform Experiments
171(1)
5. Verify Results
172(1)
6. Follow Up/Standardize
172(1)
Kaizen Events
173(4)
Large Group Improvement Events
173(2)
Try This
175(2)
Chapter 8: Quality 177(30)
Feedback
177(13)
The Polaris Program
177(2)
Release Planning
179(3)
Architecture
182(1)
Iterations
183(7)
Preparation
185(1)
Planning
186(1)
Implementation
186(2)
Assessment
188(1)
Variation: User Interface
189(1)
Discipline
190(14)
The Five S's
190(3)
Standards
193(3)
Code Reviews
194(1)
Pairing
195(1)
Mistake-Proofing
196(2)
Automation
197(1)
Test-Driven Development
198(3)
Unit Tests (Also Called Programmer Tests)
200(1)
Story Tests (Also Called Acceptance Tests)
200(1)
Usability and Exploratory Testing
201(1)
Property Testing
201(1)
Configuration Management
201(1)
Continuous Integration
202(1)
Nested Synchronization
203(1)
Try This
204(3)
Chapter 9: Partners 207(16)
Synergy
207(10)
Emergency!
207(2)
Open Source
209(1)
Global Networks
210(4)
Outsourcing
214(3)
Infrastructure
214(1)
Transactions
215(1)
Development
216(1)
Contracts
217(4)
The TS Agreement
217(1)
The PS 2000 Contract
218(1)
Relational Contracts
219(2)
Try This
221(2)
Chapter 10: Journey 223(24)
Where Do You Want to Go?
223(6)
A Computer on Wheels
224(1)
A Long-Term Perspective
225(2)
Centered on People
227(2)
What Have We Learned?
229(5)
Six Sigma
229(1)
Process Leaders—Natural Work Team Leaders
229(1)
Tools—Results
229(1)
Theory of Constraints
230(4)
Critical Chain
232(1)
Accommodations
233(1)
Hypothesis
234(8)
Training
234(2)
Thinking
236(1)
Measurement
237(6)
Cycle Time
238(2)
Financial Return
240(1)
Customer Satisfaction
241(1)
Roadmap
242(1)
Try This
243(4)
Optimize the Whole
243(1)
Respect People
243(1)
Deliver Fast
244(1)
Defer Commitment
244(1)
Create Knowledge
245(1)
Build Quality In
245(1)
Eliminate Waste
246(1)
Bibliography 247(10)
Index 257

Supplemental Materials

What is included with this book?

The New copy of this book will include any supplemental materials advertised. Please check the title of the book to determine if it should include any access cards, study guides, lab manuals, CDs, etc.

The Used, Rental and eBook copies of this book are not guaranteed to include any supplemental materials. Typically, only the book itself is included. This is true even if the title states it includes any access cards, study guides, lab manuals, CDs, etc.

Excerpts

The Sequel Lean was an idea borrowed from the 1990s when we wrote the bookLean Software Development: An Agile Toolkitin 2003. We had observed that breakthrough ideas from manufacturing and logistics often take a decade or two before they are adapted to provide suitable guidance for development efforts. So we decided it was not too late to use well-proven lean concepts from the 1980s and 1990s to help us explain why agile methods are a very effective approach to software development. The strategy worked. The bookLean Software Developmentpresents a set of thinking tools based on lean thinking that leaders continue to find useful for understanding agile software development. The book has been purchased by many a developer who gave it to his or her manager to read, and many managers have distributed multiple copies of the book to colleagues in support of a transition to lean/agile software development. Meanwhile, something unexpected happened tolean. In the last couple of years lean initiatives have experienced a resurgence in popularity. The word lean was originally popularized in the early 1990s to characterize the Japanese approach to automobile manufacturing. In recent years, Honda and Toyota have been doing increasingly well in the North American auto market, while Detroit automakers are restructuring. For example, Toyota's profits rose from more than $8 billion in the fiscal year ending March 31, 2003, to more than $10 billion in 2004, $11 billion in 2005, and $12 billion in 2006. Many companies have taken a second look at lean to try to understand what's behind such steady and sustained success. Lean initiatives seldom start in the software development or product development area of a company, but over time, successful lean initiatives make their way from manufacturing or logistics to development departments. However, lean practices from manufacturing and other operational areas do not adapt easily to a development environment, so lean initiatives have a tendency to stall when they reach software development. While the underlying lean principles remain valid, it is usually inappropriate to apply operational practices and measurements to a development environment. When lean initiatives stall in software development areas, many companies have discovered that the bookLean Software Developmentgives them a good foundation for thinking about how to modify their approach and adapt lean ideas to a development organization. The benefits of lean and agile software development have become widely known and appreciated in the last few years, and many organizations are changing the way they develop software. We have traveled around the world visiting organizations as they implement these new approaches, and we have learned a lot from our interaction with people working hard to change the way they develop software. As our knowledge has grown, so has the demand for more information on implementing lean software development. We realized that a new book would allow us to share what we've learned with many more people than we can contact personally. Therefore we have summarized our experiences in this book,Implementing Lean Software Development: From Concept to Cash. This book is not a cookbook for implementing lean software development. Like our last book, it is a set of thinking tools about how to go about adapting lean principles to your world. We start this book where the last book left off and go deeper into the issues and problems that people encounter when trying to implement lean and agile software development. You might consider this book a sequel toLean Software Development. Instead of repeating what is in that book, we take a different perspective. We assume the reader is convinced that lean software development is a good idea, and focus on the essential elements of a successful implementation. We look at key aspects of implementation and discuss wh

Rewards Program