The document discusses lean software development principles for achieving continuous delivery, including eliminating waste, amplifying learning, deciding late, delivering fast, empowering teams, building integrity, and seeing the whole process. It provides examples of how following these principles can reduce wait times, unnecessary processes, and bugs by making decisions quickly with the whole team and delivering changes more rapidly based on feedback. The overall message is that lean principles can help teams optimize their processes for continuous delivery.

1. LEANING YOUR WAY INTO
CONTINUOUS DELIVERY
Lance Kind

2. About Lance Kind
XP since 1999
Agile consultant since 2006
Lived in China 5 yrs
Based in Seattle

3. Lean Software Dev. Principles
1. Eliminate Waste: Unnecessary code, functionality, process, …
2. Amplify Learning
3. Decide as late as possible (last responsible moment)
4. Delivery as fast as possible
5. Empower the whole team
6. Build integrity in
7. See the whole
We’ll cover waste, point 1, at the end.

4. Lean Principle 2. Amplify Learning

5. PM/SM Senior Dev Dev 2 Dev 3 QA 1
QA 2 PO
Talk Time
30%
5%
5%
5%5%
30%
20%

6. PM/SM Senior Dev Dev 2 Dev 3 QA 1
QA 2 PO
Talk Time
13%
17%
17%
17%
17%
17%
4%

7. Amplify learning everywhere
• requirements
• development
• operations
• QA
• product ownership
•market reaction

8. 3. DECIDE AS LATE AS
POSSIBLE

10. How late?
• For iterative development, need
estimates by end of planning meeting.
• To make meeting bearable, need to
prepare for planning meeting
• scenarios for each proposed work
item
• team has some knowledge of the
work
• work items are vetted for blocking
issues before meeting
• Decide details during Sprint

11. 4. DELIVERY AS FAST AS
POSSIBLE
Change this to a Feature size problem,
then get market feedback quickly rather than slow, hold ups create wait states and those wait states are going to generate complex processes. !
Bug tracking systems

12. If you don’t deliver your bugs fast, then you’ll need branches, change management tracking, bug tracking system which is a queue for bugs.
What’s the oldest bug in your bug tracking system? Why are you tracking it? Is it just wasting your time?

13. Developer, PO, and Tester are looking at a problem they’ve discovered. Within minutes the PO will decide if it’s a bug. If it is a bug, they’ll discuss if it can be fixed in the Sprint. If they can’t she’ll put it on the product backlog to be prioritized against other features. If it isn’t a bug, they’ll spread that
understanding by conversation and move on. !
This type of decision making only needs a few minutes if you have the right people working together on a daily basis. !
Deliver Bug fixes as quick as possible. The ones you don’t care about, throw the report in the garbage as it will come up again if it’s important.

14. It takes 12 steps in separate groups of bullets to tell you how to use this system. There is effort involved.

15. 5. EMPOWER THE WHOLE
TEAM
Negative meeting culture,
show release planning for whole team,
round-robin is slow, boring, sucks group energy. and filled with wait states. Break this habit.
!
Standup poker planning.
Grooming or release planning that allows individuals to make decisions in a natural flow.

19. 6. BUILD INTEGRITY IN
BDD -get the requirements right
— automation to keep them right !
TDD - keep the design defect free
— adapt the design to keep new features cheap ! Visualize with a build monitor and BDD test report, living traceability matrix.

21. BDD report that’s real time.

22. 7. SEE THE WHOLE

24. Establish Today’s Max Speed
(easy requirement)
requirement
development
need
discovered
feature
developed UAT/QA
go live
DB
or
feeder
Biz Service
Hello World Objects UI
Discover the quickest way to deliver hello world from end to end.

25. Use Lean Principles to Discover
Improvements
• Many forms of waste are due:
• Deciding too early and creating process to “not forget”
and monitor commitments over a long time.
• Delivering too slow so need cross-organizational
mechanisms to “not forget”
• Disempower the team because costs of mistakes feel too
high, and discovering mistakes is too hard.
• Integrity is low so we have a lot of manpower to check,
double check, and triple check every step.

26. • Make visible the WHOLE
• End to end to deliver product
• Go faster by identifying:
1. waste
2. how to decide later
3. how to amplify learning
4. empower
5. build integrity in
• Eliminate Waste: Unnecessary code,
functionality, process, …
• Amplify Learning
• Decide as late as possible (last
responsible moment)
• Delivery as fast as possible
• Empower the whole team
• Build integrity in
• See the whole

27. Did You Discover Anything?

28. Further more
• twitter.com/LancerKind
• news about test automation,
agile, and other things
• AgileNoir.biz
• Learn about Agile & have fun
• LancerKind@Gmail.com
• VOIP: +01 206 866 5983
• Free download of SCRUM NOIR
Bad Boys of Scrum this week on
Amazon.