This is the true story of a software creation team who wanted to double its productivity. See how a PDCA-like approach led to implement Dojo and Mob programming practices, what worked and what could be improved. Agile teams who want to increase their skills and efficiency through a standardized way of sharing knowledge amongst team members will learn a lot here. More about Lean in IT on www.lean-it-summit.com

1. P ris, France
16 & 17 October, 2014
Copyright © Institut Lean France 2014
Lean IT Summit ®
®
“Training Within Software”
using Dojo and
Mob Programming
Bernard Notarianni

2. Bernard Notarianni
Agile Coach / XP http://umolelo.com
Software creation
Web/Mobile
Microsoft .Net
Erlang
Agile Coaching
Managers, product owners, devs
XP practices trainer
Team dynamics facilitation

3. Story
Those people found what works for them
We are sharing with those who want to try
We do not try to convince anybody

4. Story
Those people found what works for them
We are sharing with those who want to try
We do not try to convince anybody
Explaining what happened
using Lean point of view
Lean

5. The team
4 functional experts
•Within 10 to 20 years of experience
•Distributed in France, Belgium, Italy and Spain
5 developers colocated in Paris
•1 expert .Net /MVC – technical lead
•1 senior dev on .Net/MVC
•3 internal developers
1 agile coach (XP / Craftmanship)

6. R1
One year project
Iter 1
Iter 2
Iter 3
Iter 4
Iter 5
Iter 6
Iter 7
Iter 8
Release 1 = 8 one-week iterations
R2
R3
R4
R5
R6
R7
R8
R9
R10
R11
About 4000 to 8000 Man.Days

7. Iter 1
Iter 2
Iter 3
Iter 4
Iter 5
Iter 6
Iter 7
Iter 8
Short cycles
Lean

8. Continuous improvment
with daily reflection
Lean
Photo Alper Çuğun - CC BY 2.0

9. Gemba* ?
Lean
*Gemba = the « real place » where the work is done and the product is created.

10. Gemba = the code!
Lean

11. Bad quality of code
We dont know the technology
Training with cycle of Dojo
Cycle 1
Observation
Hypothesis
Experiment
Result

12. Training program
1.CRUD Asp.Net MVC & Code Fluent Entities
2.Partial View, Child Action with Asp.Net MVC
3.TDD
4.Unit Test & Mock
5.FitNesse
6.Working methodology
7.MVC ++ (Ajax etc.)
8.TFS + Azure
9.Code Fluent Entities ++
10.Dependency injection with Unity
11.Watin
Tech
Tech
Method
Tech
Tech
Method
Tech
Method
Tech
Tech
Tech
Topics are fully customised to the context of the team
Lean

13. Deep thinking about our current knowledge
Lean

14. Courtesy of BetClic
Learn from others’ mistakes
Lean
Share comments and advice from the expert
Lean
Repetition to anchor the knowledge
Lean

15. Photo Zach Dischner - CC BY 2.0

16. Bad quality of code
We dont know the technology
Training with cycle of Dojo
Cycle 1
Code compliant with .net/MVC standards
Observation
Hypothesis
Experiment
Result

17. Iter 1
Iter 2
Iter 3
Iter 4
Iter 5
Iter 6
Iter 7
Iter 8

19. The voice of the client
Lean

20. Photo Alper Çuğun - CC BY 2.0

21. Bad quality of code
We dont know the technology
Training with cycle of Dojo
Cycle 1
Code compliant with .net/MVC standards
Observation
Hypothesis
Experiment
Result
Low velocity
UI complexity is slowing us down
Cycle 2

23. From 8th light blog, Robert Martin (Uncle Bob)

24. Test

25. Test
Short
time frame
Lean
Creating knowledge
for improvement
Lean
Scientific experiment
Lean

26. Bad quality of code
We dont know the technology
Training with cycle of Dojo
Cycle 1
Code compliant with .net/MVC standards
Observation
Hypothesis
Experiment
Result
Low velocity
UI complexity is slowing us down
Implement all but UI in one day
Cycle 2

27. Black Friday

28. I was wrong

29. Bad quality of code
We dont know the technology
Training with cycle of Dojo
Cycle 1
Code compliant with .net/MVC standards
Observation
Hypothesis
Experiment
Result
Low velocity
UI complexity is slowing us down
Implement all but UI in one day
Cycle 2
FAIL: everything is slowing us down.
Deep focused
observation
Lean
Gemba=code
Lean

30. Photo Alper Çuğun - CC BY 2.0

31. Bad quality of code
We dont know the technology
Training with cycle of Dojo
Cycle 1
Code compliant with .net/MVC standards
Observation
Hypothesis
Experiment
Result
Low velocity
UI complexity is slowing us down
Implement all but UI in one day
Cycle 2
FAIL: everything is slowing us down.
Low velocity
We don’t understand the code from team mates
Mob Programming complex refactoring
Cycle 3

33. Experiment
Refactoring of customer table
Impact all over the application
4 developers in a meeting room. No experts.

34. Photo Zach Dischner - CC BY 2.0

35. Bad quality of code
We dont know the technology
Training with cycle of Dojo
Cycle 1
Code compliant with .net/MVC standards
Observation
Hypothesis
Experiment
Result
Low velocity
UI complexity is slowing us down
Implement all but UI in one day
Cycle 2
FAIL: everything is slowing us down.
Low velocity
We don’t understand the code from team mates
Mob Programming complex refactoring
Cycle 3
Faster creation of quality code

36. Bad quality of code
We dont know the technology
Training with cycle of Dojo
Cycle 1
Code compliant with .net/MVC standards
Observation
Hypothesis
Experiment
Result
Low velocity
UI complexity is slowing us down
Implement all but UI in one day
Cycle 2
FAIL: everything is slowing us down.
Low velocity
We don’t understand the code from team mates
Mob Programming complex refactoring
Cycle 3
Faster creation of quality code
Time wasted understanding specs
Specs are not detailed enough with users’ input
Mob Specs
Cycle 4
Less time wasted during mob prog.

37. Func. spec
Mob Spec
Fitnesse
creation
Spikes
Bug Fix
Solo dev
Mob
Démo
Pair
Pair
Day 1
Day 2
Day 3
Day 4
Day 5

38. Productivity?

41. Func. spec
Mob Spec
Fitnesse
creation
Spikes
Bug Fix
Solo dev
Mob
Démo
Pair
Pair
Day 1
Day 2
Day 3
Day 4
Day 5
Time wasted
on bug fixing
Lean
All value
created here
Lean
Bottleneck?

42. R1
Area for more improvement
R2
R3
R4
R5
R6
R7
R8
R9
R10
R11
x2
x4
x1.3

43. Conclusion
Gemba = code
Continuous improvement using one week iterations
Bottleneck = sharing knowledge within team
Solution = learn as a team (Dojo, Mob Programming…)

44. We do need to learn everywhere

45. Design process as a learning acquisition activity

46. Questions?
« I want to try! »