The document describes the Mikado Method for incrementally refactoring large codebases. It involves recursively fixing pre-requisites to changes by reverting broken code, documenting the dependency graph, and ensuring each change delivers a working version. This method allows refactoring to proceed gradually while maintaining a deployable main branch, improving communication, and keeping developers focused on necessary changes.

1. Mikado
Method

3. A tool for large-scale refactorings

4. REFACTOR ?

5. PRODUCT OWNER

6. DEVELOPERS

7. GARDENING

8. APP

9. REFACTOR

11. Refactoring the old way is like
removing an old stump…
you will also leave some roots…

12. REFACTOR WITH BRANCHES

14. Refactoring using branches is like
grafting fruit trees…
you never know that what you can get.

15. MIKADO METHOD

17. Refactoring using the Mikado Method
is like pruning ornamental trees…
• You can work in an incremental process.
• You can always change the shape.
• You always see what you get.

18. REFACTORING
THE OLD WAY

19. RIGOROUS ANALYSIS

20. GUESS

21. PROBLEMS

22. APP
My change

23. APP
My change

24. APP
My change

25. APP
My change

26. APP
My change

27. APP
My change

29. REVERT

30. REFACTORING
USING BRANCHES

31. WHEN THE BRANCH IS CREATED

32. MERGING BRANCHES

33. AFTER MERGING BRANCHES

34. PROBLEMS

35. REFACTORING
MIKADO METHOD

37. Do you know
how to play
mikado game?

38. INCREMENTAL

39. LIGHTWEIGHT

40. VISIBILITY

41. STABILITY

42. CONTINUOS DEPLOYMENT

43. COMMUNICATION

44. LEARNING

45. WORK DONE

46. COLLABORATION

47. WORKLOAD

48. EASY

49. HOW IT WORKS ?

50. COMPILED
&
INTERPRETED

51. STEP 1
Naive implementation

52. STEP 1.1
Is something new failing ?
YES - STEP 2
NO - STEP 8

53. STEP 2
What is failing?

54. STEP 3
Document the
pre-requisites
to fix that is failing

55. STEP 4
Document the graph

56. STEP 5
Revert your changes.

57. STEP 5.1
There are more pre-requisites
in this level?
YES - STEP 6
NO - STEP 7

58. STEP 6
Get the next pre-requisite
GOTO STEP 1
repeat the process

59. STEP 7
Down one level
GOTO STEP 5.1

60. STEP 8
Pre-requisite has been
FIXED

61. STEP 9
Document the graph

62. APP
A change
STEP 1

63. APP
A change
STEP 2

64. STEP 3-4
APP
Pre-req
Pre-req
A change
Pre-req

65. STEP 5
APP
Pre-req
Pre-req
A change
Pre-req

66. STEP 5
APP
Pre-req
Pre-req
A change
Pre-req

67. STEP 6-1
APP
Pre-req
Pre-req
A change
Pre-req

68. STEP 2
APP
Pre-req
Pre-req
A change
Pre-req

69. Pre-req
STEP 3-4
APP
Pre-req
Pre-req
Pre-req
A change
Pre-req

70. Pre-req
STEP 5
APP
Pre-req
Pre-req
Pre-req
A change
Pre-req

71. Pre-req
STEP 1
APP
Pre-req
Pre-req
Pre-req
A change
Pre-req

72. Pre-req
STEP 1
APP
Pre-req
Pre-req
Pre-req
A change
Pre-req

73. Pre-req
STEP 1
APP
Pre-req
Pre-req
Pre-req
A change
Pre-req

74. Pre-req
STEP 1
APP
Pre-req
Pre-req
Pre-req
A change
Pre-req

75. Pre-req
STEP 1
APP
Pre-req
Pre-req
Pre-req
A change
Pre-req

76. Pre-req
STEP 1
APP
Pre-req
Pre-req
Pre-req
A change
Pre-req

78. WRITE DOWN YOUR GOAL
SEEK THINGS TO TRY
BACK OUT BROKEN CODE
FIX THE PRE-REQUISITES
RECURSIVELY

80. ALWAYS DELIVERABLE FROM THE MAIN BRANCH
No more broken environments
No more merging issues

81. GOAL FOCUS
Do only the necessary

82. VISUALIZATION OF GRAPH
Best documentation
Improve communication
Improve cooperation

83. HAPPY TEAM