August 12, 2011
From the book, 5.1.3 ‘Large scale improvements’:
When large portions of the code is changed the whole team will have to be engaged, and everyone needs to know the goal to be able to help out and understand. The team also has to communicate outside of its immediate vicinity, especially if the change is based on an external goal.
This is the perfect situation for the Mikado Method.
As the code undergoes these changes work is probably spread out over several days, weeks or months, and can benefit a lot from being carried out by several developers on a team. Putting the Mikado Graph on a whiteboard during this period of change is a great way to communicate that goal, the progress and its current state. External stakeholders, managers and other people with interest in the progress are also more likely to get involved if they can see what is happening.
February 20, 2011
We just split and moved the Mikado Method code examples and exercises on github.
The new location is a github organization for the Mikado Method:
(Old location: https://github.com/brolund/mikadomethod)
The examples are now split in separate repositories for better separation of concerns.
The examples are
The example from the book, in C#.
Some messy code containing a solar system simulation and an breakout embryo, all in one. We intent to specify some good goals to practice larger refactorings and restructurings.
Another example. We intend to give you some hints on meaningful goals here as well.
April 6, 2010
Upcoming talks about the Mikado Method:
Øredev in Malmö, Sweden, November 12
Previously, the Mikado Method has been presented at the following places:
Agile2010 in Orlando FL, USA, August 9-13
XP2010 in Trondheim, Norway, June 1-4
SPA2010 in London, UK, May 16-19
XPDay 2009 in London, UK, December 7-9
SDC2009 in Gothenburg, Sweden, March 24
We are of course interested in speaking at your conference or company, please contact us.
February 2, 2010
For those of you who wonder what the Mikado method is and don’t have the time to read through a lot of text. This one is for you: