Win a copy of 97 Things Every Java Programmer Should Know this week in the Java in General forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Jeanne Boyarsky
  • Junilu Lacar
  • Henry Wong
Sheriffs:
  • Ron McLeod
  • Devaka Cooray
  • Tim Cooke
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Frits Walraven
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Piet Souris
  • salvin francis
  • fred rosenberger

Mikado and Software development

 
Ranch Hand
Posts: 88
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Ola,

It was interesting to read the introduction chapter. Does the Mikado development address all areas of software development viz. Requirements, desing , development and delivery?
Or Is it just applicable predominantly to the "Design and Development" of software?
 
author
Posts: 5
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Sunderam,

I take the liberty of answering your question. :-)

The Mikado Method is primarily to make code changes to existing systems, and it shines in situations where you have a lot of entangled dependencies to keep track of. We've mostly used it for just that when implementing new features, or just changed the way things work, as in refactorings/restructurings. This is what the book is about.

We have also used a Mikado-like dependency graph to keep track of things needed for e.g. deliveries, but this is not in the book.

A friend and former colleague of ours has used it for organizational change. This is not in the book either.
http://nomad8.com/organisational-change-with-mikado/

We strongly believe that dependency graphs are good for making models of the world that help us understand how things are connected and to act upon that information. We encourage you to try the next time you have a problem. Software development, deliveries, refurnishing a room, or something completely different. :-)
 
Sunderam Goplalan
Ranch Hand
Posts: 88
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks Daniel.

Yes I like dependency graphs too. Along those lines, I've used one of the maven plugins that reports dependencies amongst modules and have found it useful. It
will tell us if discrepancies exist in the project modules etc. It's good to know that such a tool is part of Mikado!

 
If tomatoes are a fruit, then ketchup must be a jam. Taste this tiny ad:
Devious Experiments for a Truly Passive Greenhouse!
https://www.kickstarter.com/projects/paulwheaton/greenhouse-1
    Bookmark Topic Watch Topic
  • New Topic