Got through the huge stack of cards from Friday’s story workshop. Everything’s in our application (VersionOne). I found it kind of hard not to editorialize the process as I transformed these things from paper to an electronic form, but I stayed disciplined. A couple issues I noticed were duplicate stories, too-small stories (interesting, I thought we’d have more of a problem with epics), and an awful tendency to write stories in terms of comparison to the legacy software.
Any changes I did make were to steer the stories away from “too-small” or “comparison specific”. For example, we had lots of situations where we’d have three or four stories representing a CRUD scenario (e.g. “Create an Entity Type“, “Delete an Task Type“, “Modify a Task Type“). If they were simple, lookup-type items I merged them into “Manage Entity Type” stories. Another thing I did was to create a title for each story. This makes it easier for people to identify the item in a list or report.
Tomorrow we’ll spend a good chunk of the day estimating the stories, then we’ll hit the customer team with prioritization duty.
Post a Comment