Chapter 1. Meet the Mikado Method
Figure 1.1. A Mikado Graph with a goal and two prerequisites
Figure 1.2. Being able to change the shape of things is a highly desirable skill
Figure 1.3. A process chart describing the Mikado Method
Figure 1.4. A user story
Figure 1.5. Start with the goal, replacing “Mikado Goal” with your task or story.
Figure 1.6. Note the immediate solution, or prerequisite.
Figure 1.7. Repeat the steps for each prerequisite to build knowledge about the dependencies.
Figure 1.8. Check off the solutions as they are completed.
Chapter 2. Hello, Mikado Method!
Figure 2.1. The Mikado Method process
Figure 2.2. Drawing the Mikado Goal will help us focus on the task at hand.
Figure 2.3. A clearly written goal makes it easy to know when it’s accomplished.
Figure 2.4. Trying things can provide more feedback than hours of analysis.
Figure 2.5. The compiler, tests, or running the system will help us find the errors quickly.
Figure 2.6. Don’t think too hard about the consequences; just pick a solution that will pull the system in a good direction.
Figure 2.7. We add the solutions to the graph as we come up with them.
Figure 2.8. Prerequisite added
Figure 2.9. The most important, and yet unintuitive, step of the process: fix the broken system by reverting
Figure 2.10. Zoom out and look at the graph. What’s the next sensible prerequisite, or leaf, to work on?
Figure 2.11. Checking in cohesive changes will make coworkers much happier.