Presenter: Jeff Patton
Facilitator: Andy Powell
Attendees list at bottom (including contact address)
Thanks for Jeff for being a true agilist and leading this session on about 25 minutues notice! Thanks to Ron Jeffries for having an always ready supply of index cards.
Photo of our story map.
Resources for learning more:
http://agileproductdesign.com/blog/the_new_backlog.html
Action Item for Andy: figure out how this community can collaborate!
The Need for Story Maps
With a backlog you go from high levels of granularity to lower levels of granularity. Roadmap > Features > User Stories. As you get down the user story level, you start to lose the forest by focusing only on a single tree. Story Maps are a visualization that let you see both the forest and the trees. Story maps are a way to organize your backlog. It's primary focus is to provide context and it also shows priority.
Steps to Create Story Map
1. What is the project and why are you doing it?
2. Who are your users --get concrete
3. Capture Day in hte life story into ACTIVITIES. Creates the backbone. Organize them from left to right to show the time an activity occurs in relation to anothers from a user perspective.
4. Capture more specific user tasks below the activities.
5. More important tasks should go above the less important ones.
Usage and Discussion Notes
Attendees
tkcjfguard-scm at yahoo dot com
tom.flynn at sungardps.com
sarah_pochyla at keybank.com
lucie_odette.lapointe at tdinsurance.com
bazil at agilechange.com
mgalloway at sncoast.com
pesmith at adobe.com
akausel at sncoast.com
anu_ramaswamy at csaa.com
raff_90 at yahoo.com
acockburn at aol.com
jpatton at acm dot org
andy.powell at versionone.com
Ford Spares Parts in Ford Parts Gateway