Only Software matters

Experiences in software development

  • Enter your email address to follow this blog and receive notifications of new posts by email.

    Join 640 other followers

  • MVB

  • JavaCodeGeeks

    Java Code Geeks

  • My recent tweets

    • RT @voxxed_thess: ▶️8 Days remaining for Voxxed Days Thessaloniki! In sponsoring Voxxed Days Thessaloniki, these great companies decided… 3 days ago
    • RT @softwaregarden: Save the dates. This November lots of tech events will happen in Thessaloniki - Saturday, 17th, Global Day of @coderet2 weeks ago
    • RT @voxxed_thess: We'd like to convey our gratitude to @Stoiximan , our Platinum Sponsor for this year's Voxxed Days Thessaloniki! Stoixima… 4 weeks ago
    • RT @voxxed_thess: 🤔 𝐀 𝐜𝐥𝐞𝐯𝐞𝐫 𝐩𝐞𝐫𝐬𝐨𝐧 𝐬𝐨𝐥𝐯𝐞𝐬 𝐚 𝐩𝐫𝐨𝐛𝐥𝐞𝐦. 𝐀 𝐰𝐢𝐬𝐞 𝐩𝐞𝐫𝐬𝐨𝐧 𝐚𝐯𝐨𝐢𝐝𝐬 𝐢𝐭! 😎 46 Days Remaining for Voxxed Days Thessaloniki! #vdthess11 month ago
    • RT @softwaregarden: We need more #WomenInTech that's why @voxxed_thess is the only conference in Greece that offers discounted tickets for… 1 month ago

Archive for the ‘technical debt’ Category

Mikado Method – Learn how to eliminate your techical debt

Posted by Patroklos Papapetrou on May 13, 2013


Save 50% on The Mikado Method and these other selected books. Just enter miklaunch50 in the Promotional Code box when you check out. Expires Tuesday, May 23. Only at

The Mikado Method is a process for surfacing the dependencies in a codebase so that you can systematically eliminate technical debt. It gets its name from a simple game commonly known as “pick-up sticks,” in which you try to remove the Mikado stick without disturbing the others. The game is a great metaphor for eliminating technical debt by carefully extracting each intertwined dependency until you’re able to successfully resolve the central issue and move on.

The Mikado Method, a book by the creators of this process, presents 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 refac, TDD, and rapid feedback. It requires no special hardware or software and can be practiced by both small and large teams.

You can also choose…


Posted in quality, software, technical debt | 1 Comment »

%d bloggers like this: