Marla Scott — Mon, 16 Jul 2007 00:55:47 GMT

Thanks for this breakdown, Adam. Our project team recently used this method of breaking out user stories with regard to priorities, project deliverables and tasks.

It’s worked very well for us with a strong project manager keeping us on track and supporting the appropriate meetings. The “what we did well” column at the end of each iteration far outweigh the “what we didn’t do so well” column from all team member perspectives, including development, product owner, IA, design and technical analyst.

I think it’s in the way the user stories are defined. In our case, that meant a conscious effort to remove design/UI language such “a checkbox option” or “a drop down list” that helped define the skeleton under the muscle.

Like you said, it removes the politics, frees the UI in a way I have not experienced in a multi-role team environment and tames the value business creates for certain visual aspects and interactions by putting them into the proper perspective.

Boxes and Arrows: Comments by Marla Scott