Software Engineering Institute | Carnegie Mellon University
Software Engineering Institute | Carnegie Mellon University

Digital Library

Javascript is currently disabled for your browser. For an optimal search experience, please enable javascript.

Advanced Search

Basic Search

Content Type


Publication Date


Improving Architectural Refactoring Using Kanban and the Mikado Method

  • April 2015
  • By Paul Boos (Santeon Group)
  • This presentation covers the Mikado Method and how it works, explores the issues and the Kanban backlog, and overviews why Kanban a good fit for maintenance.
  • Publisher: Software Engineering Institute
  • This presentation was created for a conference series or symposium and does not necessarily reflect the positions and views of the Software Engineering Institute.
  • Abstract

    Have you ever found yourself making a change to a system only to have dozens of bugs or other issues pop up? Then you make some more changes trying to solve those and, yikes, more are found! You're on the software spelunking trip from hell with the cavern walls collapsing...

    Embrace the Zen of the Mikado Method. This powerful approach allows you to discover, visualize, and safely make all the changes you need without losing your mind by giving you input into dependencies that can drive your work priorities. Since it contains a visualization technique, it can help your teams understand legacy code and its impacts and then communicate these to stakeholders. Combine this with a Kanban board to help you visualize your progress, and now you can easily see how well you are making progress.

    This 30-minute presentation will step you through the following topics:

    • What is the Mikado Method?
    • How does it work?  
    • Exploring the issues and populating the Kanban backlog  
    • Why is Kanban a good fit for maintenance?
  • Slides

Part of a Collection

SATURN 2015 Presentations