null
Loading... Please wait...
FREE SHIPPING on All Unbranded Items LEARN MORE
Print This Page

The Mikado Method

List Price: $44.99
SKU:
9781617291210
Quantity:
Minimum Purchase
25 unit(s)
  • Availability: Confirm prior to ordering
  • Branding: minimum 50 pieces (add’l costs below)
  • Check Freight Rates (branded products only)

Branding Options (v), Availability & Lead Times

  • 1-Color Imprint: $2.00 ea.
  • Promo-Page Insert: $2.50 ea. (full-color printed, single-sided page)
  • Belly-Band Wrap: $2.50 ea. (full-color printed)
  • Set-Up Charge: $45 per decoration
FULL DETAILS
  • Availability: Product availability changes daily, so please confirm your quantity is available prior to placing an order.
  • Branded Products: allow 10 business days from proof approval for production. Branding options may be limited or unavailable based on product design or cover artwork.
  • Unbranded Products: allow 3-5 business days for shipping. All Unbranded items receive FREE ground shipping in the US. Inquire for international shipping.
  • RETURNS/CANCELLATIONS: All orders, branded or unbranded, are NON-CANCELLABLE and NON-RETURNABLE once a purchase order has been received.
  • Product Details

    Author:
    Ola Ellnestam, Daniel Brolund
    Format:
    Paperback
    Pages:
    240
    Publisher:
    Manning (March 17, 2014)
    Language:
    English
    ISBN-13:
    9781617291210
    ISBN-10:
    1617291218
    Dimensions:
    7.38" x 9.25" x 0.7"
    File:
    Eloquence-SimonSchuster_06032026_P10163223_onix30_Complete-20260603.xml
    Folder:
    Eloquence
    List Price:
    $44.99
    Case Pack:
    32
    As low as:
    $40.49
    Publisher Identifier:
    P-SS
    Discount Code:
    G
    Weight:
    15.2oz
    Pub Discount:
    37
    Imprint:
    Manning
  • Overview

    Summary

    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.

    About the Technology

    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.

    About the Book

    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.

    Purchase of the print book includes a free eBook in PDF, Kindle, and ePub formats from Manning Publications.

    What's Inside
    • 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

    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 legacy systems.

    Table of Contents
      PART 1 THE BASICS OF THE MIKADO METHOD
    1. Meet the Mikado Method
    2. Hello, Mikado Method!
    3. Goals, graphs, and guidelines
    4. Organizing your work
    5. PART 2 PRINCIPLES AND PATTERNS FOR IMPROVING SOFTWARE
    6. Breaking up a monolith
    7. Emergent design
    8. Common restructuring patterns