5, 10 or 20 seats+ for your team - learn more
The Mikado Method is a book written 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.
The game "pick-up sticks" is a good metaphor for the Mikado Method. You eliminate "technical debt" -- the legacy problems embedded in nearly every software system -- by following a set of easy-to-implement rules. You carefully extract each intertwined dependency until you expose the central issue, without collapsing the project.
The Mikado Method presents a pragmatic process to plan and perform nontrivial technical improvements on an existing software system. The book helps you practice a step-by-step system for identifying the scope and nature of your technical debt, mapping the key dependencies, and determining a safe way to approach the "Mikado" -- your goal. A natural by-product of this process is the Mikado Graph, a roadmap that reflects deep understanding of how your system works.
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.
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 legacy systems.
Enables you to deal with unavoidable complexities in manageable pieces.
If you deal with legacy code and your technical debt is increasing, read this book.
An engaging and authoritative source of information and best practices that you need to succeed.
A great guide to safer refactoring.
geekle is based on a wordle clone.