This document discusses the importance of inspecting and adapting work processes through continuous improvement. It outlines several key points: 1) Effective software development requires transparently identifying issues and being ready to change based on lessons learned. 2) The Agile Manifesto and Principles emphasize responding to change over rigid plans and regularly reflecting to improve. 3) Inspecting and adapting helps make teams more effective by addressing weaknesses and building on strengths. 4) Retrospectives should engage the whole team, identify successes and opportunities, and generate actionable commitments for improvement.

1. INSPECT AND ADAPT
By Le Trong Hiep
1

2. AGENDA
Introduction
Pitfalls
when
inspecting
Effective
adapting
Games Q&A
2

3. To succeed, it requires
Continuous
Improvement
Ready For
Changes
Transparent
Issues
Developing software is as hard as being in
relationship.
Developing Software Is Not Easy
3

4. Agile Manifesto
Responding to change over Following a plan (4/4)
Agile Principles
At regular intervals, the team reflects on how to become more
effective, then tunes and adjusts its behavior accordingly. (12/12)
4
INSPECT AND ADAPT

5. INSPECT AND ADAPT
5
Lean Development
Amplifying Learning to create new knowledge
Kaizen Development
Change for the best

6. OBJECTIVES OF INSPECT AND
ADAPT
Make bad
teams
good
Make
good
teams
great.
Keep great
teams
great.
6
Continuous
Improvement
Ready For Changes
Transparent
Issues

7. INSPECT AND ADAPT – HOW TO?
Engage the whole team.
Have inputs from everyone.
Find out what was successful.
Find out what could be improved.
Generate actionable commitments.
7

8. PITFALLS WHEN INSPECT AND ADAPT
8

9. PITFALLS WHEN INSPECT AND ADAPT
Do it internally.
Invite clients, experts, guests.
9

10. PITFALLS WHEN INSPECT AND ADAPT
Make it a Q&A section.
Apply Retrospective Games to let
the team actively involve to the
discussion.
10

11. PITFALLS WHEN INSPECT AND ADAPT
Focus on individual performance.
Look at the team performance and
interaction between members.
11

12. PITFALLS WHEN INSPECT AND ADAPT
Anchoring bias because of 1-2
dominating members.
Finding methods to remove
anchoring bias and empower
everyone to join.
12

13. PITFALLS WHEN INSPECT AND ADAPT
Overlook good things in the
iteration.
Publicly compliment and praise the
team.
13

14. PITFALLS WHEN INSPECT AND ADAPT
Make general commitments. Ex: the
team will test more careful.
Make actionable commitments. Ex:
write failing tests before fixing bugs.
14

15. GAMES
 Fishbowl
 Mad Bad Sad Glad
 Starfish
 Problem Tree
 Five Ys
 Four Ls
 Speedboat
 Etc...
15

16. SPEEDBOAT RETROSPECTIVE
Engine.
• The internal
strength.
Anchor
• The internal
impediments.
Wind
• The external
help.
Rock
• The external
impediments.
16
The plot: the team
is a boat.
Heading toward
the same goal.
While reaching
the goals, it has:

17. THE BIG PICTURE
17

18. HOW TO RUN IT
Pick a goal.
Hand to each member a set of stickers.
Ask team members to write down their ideas in
each section. (in absolute silent)
After 5-10 minutes, ask them to put stickers.
Behold the magic and take a picture.
18

19. FINAL RESULT
19

20. WHY IT WORKS
Think as one team.
Remove bias of anchoring.
Less time and more ideas.
Effortless facilitation.
Visually understanding.
20

21. Q&A
21