Difference between revisions of "Story map"

Revision as of 13:54, 17 November 2015

Reemphasize the Business Vision and its expected outcome (from the PID?)
Reiterate the Product Vision, Measurable Product Goals and output
- Unique value of initiative
Establish either (in the column headings of the story map):
- a basic workflow or flow of activities
- Epics
- Key activities
- major components
Feature Thinning Guidlelines (Jeff Patton)
- Make the top most row the first, smallest release.
- Minimize a release so that to reap financial and risk reduction benefits earlier.
- Top slice represents the minimal tasks needed to reach the Measurable Product Goals.
- How can you split the stories into its smallest parts?
  - Can the features to support the task have
    - reduced safety?
    - reduced comfort?
    - reduced luxury?
    - options slated for a later release?
- Which steps in the tasks are optional for now?

Give each slice of your story map a distinct name that suggest its major focus and value.
Consider slivering each slice so a small number of slivers fill up a season beat release schedule.

You are building a city for the graying population. Consider the following slices (and releases):

Another roadmap example from Sensei, a tool that facilitates fun, effective retrospectives for distributed agile teams.

Guided Retrospective (MVP)
- Benefit: A guided retrospecive that tracks improvement & works for remote teams too.
- Features:
  - Moderate retros locally or remotely
  - Facilitates and tracks retros
  - Plan and review actions and their results
Retrospective Customization
- Benefit: Make and share your own retros
- Features:
  - More built-in retro flows & visualizations
  - Customizable questions and flow
  - Tips for moderators
Progress Tracking
- Benefit: Powerful & beautiful improvement visualization & reporting
- Features:
  - Visualize Sprint Rating, Happiness Index, Action Results, Customer Satisfaction & more
  - Custom metrics
  - Track and trend multidimensional improvement

Yet another example of a theme park overhauling their in-park app:

Smooth & Silk
- Benefit: Snappy, fluent, and elegant beautiful experience.
- Features:
  - State of the art user experience and graphics
  - Actual and accurate information (directly from Sitecore CMS).
  - POIs show basic daily stats.
Full Day Thrill
- Benefit: Get the most out of your day at the park by minimizing waiting and travel time
- Features:
  - Clear visual waiting times
  - Discovery of hidden park pearls
  - Overview of show times—never miss a show
Zero Waiting Times
- Benefit: Never spend more than five minutes in a queue
- Features:
  - Plan your park trip in advance
  - Change your trip at any moment
  - Go to the front of the line with priority access on your next ride

@@ Line 28: / Line 28: @@
 ==Story Map Roadmap==
-Give each slice of your {{p|story map}} a distinct name that hints its major focus and value. For example, if you are building a city for the graying population, you may consider the following slices (and releases):
+*Give each slice of your {{p|story map}} a distinct name that suggest its major focus and value.
+*Consider slivering each slice so a small number of slivers fill up a {{p|season beat}} release schedule.
+===Roadmap examples===
+====Elderly City—for healthy & safe days====
+You are building a city for the graying population. Consider the following slices (and releases):
 #Basic City
 #Safe City
@@ Line 34: / Line 39: @@
 #Bingo City
+====Sensei—continuous distributed retrospectives====
 Another roadmap example from [http://senseitool.com Sensei], a tool that facilitates fun, effective retrospectives for distributed agile teams.
 #'''Guided Retrospective''' (MVP)
@@ Line 54: / Line 60: @@
 #**Track and trend multidimensional improvement
+====Theme Park App—for maximizers====
 Yet another example of a theme park overhauling their in-park app:
 #'''Smooth & Silk'''