aspose file tools*
The moose likes Agile and Other Processes and the fly likes Mikado question- weak stories Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Engineering » Agile and Other Processes
Bookmark "Mikado question- weak stories" Watch "Mikado question- weak stories" New topic
Author

Mikado question- weak stories

Karina Guenther
Ranch Hand

Joined: Sep 16, 2005
Posts: 55
Since your method depends upon the story as a basis for what needs to be done, do you discuss how to clarify weak or incomplete stories? Or how you handle if the story needs to change as you go through the process. In my company, the developers are still working on creating good stories for those of us creating automated tests.
Daniel Brolund
author
Greenhorn

Joined: May 21, 2013
Posts: 5
    
    5
Hi Karina,

Writing stories, or collecting information of what needs to be done from a business perspective, is a huge topic and beyond the scope of this book. Effect mapping is one way to do that, and it does share some ideas with the Mikado Method. See
http://www.use.se/index.php/2009/11/06/everyone-project-should-have-an-effect-map-im-doing-an-effect-map-one-for-my-iphone-app/
for a quick overview.

If you need to change the story (or Goal) you have to look at the impact of the change on your code base. In general, you can probably just assume the current state as a new starting position for the changed story. If you want or need to, and can, revert your partially implemented story you can do that.

If that happens often, maybe you should not try to find a rock solid process to handle it, but rather see if you can change how you work, to avoid it altogether? This is just a thought, and has little to do with the Mikado Method. :-)
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Mikado question- weak stories