Essays Practitioners Course Managers Workshop Concept 2 Cash Lean Toolkit Our Bookshelf

Home
People
Company
Photos

 

Order The Book

Table of Contents

Preface
Sample Chapter 1

Sample Chapter 2

Interview

 

cover
Order The Book
Table of Contents
Introduction

 Sample Chapter

Book Review 2005

Book Review 2007


Video: The Role of Leadership in Software Development
 

Video: Competing
on the basis of time

 

Conference Photos

 

 

 

Lean Software Development
Deliver Value Quickly, Efficiently, Reliably - Every Time

New Essays

 

Classes

   

Train-Wreck Management

More Essays
 

Public Classes:  Practitioners Course
Oslo, June 19-20    Information
Copenhagen, June 23-24    Information

Denver, October 28-29   Information Coming Soon

   

  Principles

Coming Events

Eliminate Waste
The three biggest wastes in software development are:
bullet
Extra Features
We need a process which allows us to develop just those 20% of the features that give 80% of the value.
bullet
Churn
If you have requirements churn, you are specifying too early.  If you have test and fix cycles, you are testing too late.
bullet
Crossing Boundaries
Organizational boundaries typically increase cost by over 25%, creating buffers that slow down response time and interfere with communication.
 
Create Knowledge
Planning is useful. Learning is essential.
bullet
Use the Scientific Method
Teach teams to: establish hypotheses, conduct many rapid experiments, create concise documentation, and implement the best alternative.  
bullet
Standards Exist to be Challenged and Improved
Embody the current best known practice in standards that everyone follows, while actively encouraging everyone to challenge and change the standards.
bullet
Predictable Performance is Driven by Feedback
A predictable organization does not guess about the future and call it a plan; it develops the capacity to rapidly respond to the future as it unfolds.
 
Build Quality In
If you routinely find defects in your verification process, your process is defective.
bullet
Mistake-Proof Code with Test-Driven Development
Write executable specifications instead of requirements.
bullet
Stop Building Legacy Code
Legacy code is code that lacks automated unit and acceptance tests.
bullet
The Big Bang is Obsolete
Use continuous integration and nested synchronization.
 
Defer Commitment
Abolish the idea that it is a good idea to start development with a complete specification.
bullet
Break Dependencies
System architecture should support the addition of any feature at any time.
bullet
Maintain Options
Think of code as an experiment – make it change-tolerant.
bullet
Schedule Irreversible Decisions at the Last Responsible Moment
Learn as much as possible before making irreversible decisions.
 
Deliver Fast
Lists and queues are buffers between organizations that simply slow things down.
bullet
Rapid Delivery, High Quality, and Low Cost are Fully Compatible
Companies that compete on the basis of speed have a big cost advantage, deliver superior quality, and are more attuned to their customers' needs.
bullet
Queuing Theory Applies to Development, not Just Servers
Focusing on utilization creates a traffic jams that actually reduces utilization. Drive down cycle time with small batches and fewer things-in-process.
bullet
Limit Work to Capacity
Establish a reliable, repeatable velocity with iterative development. Aggressively limit the size of lists and queues to your capacity to deliver.
 
Respect People
Engaged, thinking people provide the most sustainable competitive advantage.
bullet
Teams Thrive on Pride, Commitment, Trust, and Applause
What makes a team? Members are mutually committed to achieve a common goal.
bullet
Provide Effective Leadership
Effective teams have effective leaders who bring out the best in the team.
bullet
Respect Partners
Allegiance to the joint venture must never create a conflict of interest.
 
Improve the System
Brilliant products emerge from a unique combination of opportunity and technology.
bullet
Focus on the Entire Value Stream
– from concept to cash.
– from customer request to deployed software.
bullet
Deliver a Complete Product
Develop a complete product, not just software.  Complete products are built by complete teams.
bullet
Measure UP
Measure process capability with cycle time. Measure team performance with delivered business value. Measure customer satisfaction with a net promoter score.


Limerick, Ireland, 10-14 June 2008.
Tutorial: 
Mapping the Value Stream
Workshop:  Stop Thrashing


Oslo, June 17-18
 
Danish IT University
Copenhagen, June 24 - Evening Talk
Agile Software Community of India
Workshop:  Lean Software Development - Mapping the Value Stream
Mumbai - Saturday, 28th June
Bangalore - Monday, 30th June
Delhi - Sunday, 6th July
 
Lean Product Development Summit
Shanghai, China - July 14-16, 2008

Toronto, August 4-8, 2008
Expanding Agile Horizons: The Five Dimensions of Systems
Appraisals and Compensation: The Elephant in the Room
Open Source Meets Agile - with Christian Reis
Robust Performance of Complex Systems - with Michael Nygard

Dublin, September 3-5, 2008.

Oslo, September 17-18


Lean & Agile Software Development

Stockholm, September 23-24

Agile Network
Linköping , September 24
Deep Lean
Stockholm, September 25-26

Buenos Aires, Argentina 20 al 24 de octubre 2008

Orlando, FL, November 10-13

Another View

 

Past Events

 

Join the Lean Development Discussion Group

Top M

 

Copyright © 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007 Poppendieck.LLC
Screen Beans Art © A Bit Better Corporation
Last modified: March 17, 2008