Eliminate Waste
The three biggest wastes in software development are:
 |
Building the Wrong Thing
“There is nothing so useless as doing
efficiently that which should not be done at all.” ~Peter
Drucker
|
|
|
Failure to Learn
Many of our policies –
for
example: governance by variance from plan, frequent handovers, and
separating decision-making from work
–
interfere
with the learning that is the essence of development.
|
|
|
Thrashing
Practices that interfere with the
smooth flow of value –
for example: task
switching, design loopbacks, technical debt, even backlogs
–
cause organizations to deliver increasing less value while
using increasingly more resources.
|
Build Quality In
If you routinely find defects in your verification
process, your process is defective.
|
|
Final Verification Should Not Find Defects!
Every software development process ever invented had as its
primary purpose to find and fix defects as early in the
development process as possible.
|
|
|
Mistake-Proof your Process with Test-First Development
Tests –
including, unit
tests, end-to-end tests, and integration tests –
must be available to establish confidence in the
correctness of the system at any time during
development, at every level of the system.
|
|
|
Break Dependencies
System architecture should support the addition of
any feature at any time.
|
Learn Before Commitment
Planning is useful. Learning is essential.
|
|
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.
|
|
|
Maintain Options
Think of code as an experiment – make it
change-tolerant.
|
|
|
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.
|
|
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.
|
|
|
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. Aggressively limit the size of lists
and queues.
|
|
|
Managing Workflow is a lot easier than Managing Schedules
The best way to establish reliable, predictable deliveries
is to establish reliable, repeatable
workflows with iterations or a kanban system.
|
Improve
Relentlessly
There
is no such thing as "best practice".
|
|
Use the Scientific Method
Teach teams to: establish hypotheses, conduct many
rapid experiments, create concise documentation, and implement the
best alternative.
|
|
|
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.
|
|
|
Learn How to See Problems and
Solve Problems
dedicate the time
and develop the capacity of the people in your organization
to constantly improve their processes.
|
Respect People
Engaged, thinking people provide the most sustainable
competitive advantage.
|
|
Teams Thrive on Pride, Commitment, Trust, and Applause
What makes a team? Members are mutually committed to
achieve a common goal.
|
|
|
Provide Effective Leadership
Effective teams have effective leaders who bring out the
best in the team.
|
|
|
Respect Partners
Allegiance to the joint venture must never create a
conflict of interest.
|
Appreciate the
System
Brilliant products emerge from a unique combination of
opportunity and technology.
|
|
Focus on the
Entire Value Stream
– from concept to
cash.
– from customer request to deployed software.
|
|
|
Deliver a Complete Product
Develop a complete product, not just software. Complete products are built by complete teams.
|
|
|
Measure UP
Measure process capability with cycle time. Measure team performance with
delivered business value. Measure customer
satisfaction with a net promoter
score.
|
|
|
|
Available NOW!
A DVD of Pictures from
XP 2010 or Agile
2010
Ordering Information and Sample Pictures:
XP 2010
Agile 2010 |
 |
| |
|
|
Events |
|
Swiss
Lean/Agile/Scrum
Zürich
Conference: Sep 7
Workshop: Sep 8-9 |
 |
 |
Leader's Workshop:
Leading Lean Software Development
Stockholm, September 16-17 |
|
Lean & Kanban
2010
Antwerp
Sep 23-24 |
 |
|
 |
Ignite Nordic
2010
Stockholm
September 29-30 |
|
JAOO 2010
Aarhus
Tutorial:
October 3
Conference: October 4-6 |
 |
|
 |
Agile Eastern Europe
Kiev
Lean Masters Class: October 6-7
Conference: October 8-9 |
|
Conference:
Beijing, October 14
Workshop:
Beijing, October 13
Shanghai, October 15 |
 |
 |
Agile Development Practices
Orlando
November 14-19 |
|
Melbourne:
Nov 30-Dec 1: Leaders Workshop
December 2-3: Conference
Brisbane:
Dec 6-7: Leaders Workshop
December 8-9: Conference
|
 |
|
Past Events |
|
