|The Mikado Method
Ola Ellnestam and Daniel Brolund
MEAP Began: May 2013
Softbound print: December 2013 | 245 pages
|Order today and start reading The Mikado Method today through MEAP|
|MEAP + Ebook only - $35.99|
|MEAP + Print book (includes Ebook) when available - $44.99|
|* For more information, please see the MEAP FAQs page.|
|About MEAP Release Date Estimates|
Table of Contents, MEAP Chapters & Resources
|Table of Contents||Resources|
PART I: THE BASICS
1 A quick introduction - FREE
2 Hello, Mikado Method! - AVAILABLE
3 More about the Mikado Method - AVAILABLE
4 Organizing your work - AVAILABLE
PART II: PRACTICAL ADVICE FOR IMPROVING SOFTWARE
5 Breaking up a monolith - AVAILABLE
6 Emergent design with the Mikado Method - AVAILABLE
7 Technical debt - AVAILABLE
8 Common restructuring patterns - AVAILABLE
PART III: CONTROLLING THE SURROUNDINGS OF THE MIKADO METHOD
9 Setting the stage for improvements - AVAILABLE
Technical debt is best understood as the work remaining before job can be considered complete or, put more colorfully, the cost of kicking the can down the road. The Mikado Method is a process for surfacing the dependencies in a codebase, so that you can systematically eliminate technical debt and get things done.
It gets its name from a simple game commonly known as "pick-up sticks." You start with a jumbled pile of sticks. The goal is to remove the Mikado, or Emperor, stick without disturbing the others. Players carefully remove sticks one at a time, leaving the rest of the heap intact, slowly exposing the Mikado. The game is a great metaphor for eliminating technical debt—carefully extracting each intertwined dependency until you're able to successfully resolve the central issue and move on.
The Mikado Method is a book by the creators of this process. It describes a pragmatic, straightforward, and empirical method to plan and perform non-trivial technical improvements on an existing software system. The method has simple rules, but the applicability is vast. As you read, you'll practice a step-by-step system for identifying the scope and nature of your technical debt, mapping the key dependencies, and determining the safest way to approach the "Mikado"-your goal. A natural byproduct of this process is the Mikado Graph, a minimalistic, relevant, just-in-time roadmap and information radiator that reflects deep understanding of how your system works.
- Understand your technical debt
- Surface the dependencies in legacy systems
- Isolate and resolve core concerns while creating minimal disruption
- Create a roadmap for your changes
This book builds on agile processes, such as refactoring, TDD, and rapid feedback. It requires no special hardware or software, and can be practiced by both small and large teams.
About the Authors
Ola Ellnestam and Daniel Brolund are developers, coaches, and team leaders. They developed the Mikado Method in response to years of experience resolving technical debt in complex systems that they didn't build but still had to fix.
About the Early Access Version
This Early Access version of The Mikado Method enables you to receive new chapters as they are being written. You can also interact with the authors to ask questions, provide feedback and errata, and help shape the final manuscript on the Author Online
Want to learn More?
Sign up to read more content when it is released and to receive news about this book.