Better requirements through story mapping­ h gidley

  • 620 views
Uploaded on

Presented at IUE 2011 October 2011 in Ann Arbor, MI. Presents story mapping and methods for use.

Presented at IUE 2011 October 2011 in Ann Arbor, MI. Presents story mapping and methods for use.

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
  • This session was really valuable. Just two days later I'm back in the office pulling up the slides to talk to colleagues about it. Thanks for sharing these here.

    Pam G
    Are you sure you want to
    Your message goes here
No Downloads

Views

Total Views
620
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
8
Comments
1
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. IUE 2011 Helene Gidley Carissa Demetris Owner, HSG Consulting Principal User Designer, ProQuest©HSG Consulting LLC 1
  • 2. ◦  Define requirements for features ◦  Obtain single interpretation of requirements ◦  Prioritize requirements ◦  Determine impact of de-scoping requirements ◦  Determine how much is completed for large features ◦  Provide a groomed backlog at beginning of sprint©HSG Consulting LLC 2
  • 3.   A physical story map 
 Visually arranges features or concepts based on an end-to-end user workflow   An interactive session
 Brings stakeholders together to discuss prioritization, planning, scope, design, technical feasibility, etc.   Introduced in 2009 by Jeff Patton ◦  http://www.viddler.com/explore/ naresh_jain/videos/36/©HSG Consulting LLC 3
  • 4.   Scoping requirements ◦  Brainstorms possible features ◦  Expose overlaps and gaps in existing requirements ◦  Drives writing of your requirements or scope documents. 
   Weighing design alternatives ◦  Requirements ◦  Enhancements ◦  Embellishments
   Planning release content ◦  Features supporting an end-to-end user experience ◦  Delivered in a given sprint/release.©HSG Consulting LLC 4
  • 5.   Provide forum for workflow and requirement elicitation   Assist in sizing of effort   Provide forum for conversations between product owners, development, business analysts ◦  Validated by walkthroughs with technical development leads, User Experience Designer/Business Analysts, and all team members   Foster shared view of work   Facilitated by User Experience Designer or BA, driven by Product Owner business needs and user experience©HSG Consulting LLC 5
  • 6.   Select persona   Identify high-level activities   Describe supporting tasks   Organize activity and task cards from left to right to describe the user’s experience with your product.   Organize from top to bottom by necessity And then And then activity time this task or…necessity or… sub-tasks or task details 6
  • 7.   Test the Story Map by telling bigger stories with it ◦  Choose an activity to start with ◦  When reading left to right use the conjunction “and then” to connect cards in the story ◦  With cards in the same column use “or” to connect cards in the story ◦  For cards below the top, “absolutely necessary” axis, use the phrase “might optionally” to communicate optionality ◦  Chose a concrete user name to help tell the story And then And then activity time this task or…necessity or… sub-tasks or task details 7
  • 8.   Tell bigger stories   Persona based   Technical team, Product Owners, User Experience/BA, Design   Facilitate estimates And then And then activity time this task or…necessity or… 8
  • 9. Activity Activity Activity Activity time Task Task first release more Tasknecessary second release necessity less third releasenecessary   Choose groups of features that support an end-to-end user experience   Support all necessary activities with the first release   Improve feature support and add additional features with subsequent releases © Jeff Patton 9
  • 10. ©HSG Consulting LLC 10
  • 11.   The problem ◦  Your company sells men’s and women’s casual clothing and wants to open an online shop ◦  The product owners aren’t quite sure about all the requirements and need some help in defining the scope of the effort
  The activity – 25 minutes ◦  Break out into groups of 6-8 people each ◦  Designate a business owner in each group ◦  Create story map of an online shopping experience   Indicate release planning by drawing lines on the map©HSG Consulting LLC 11
  • 12.   What was difficult about this process? 
 What kind of arguments did you have?
   What seemed to come together easily? 
   How could be applied to your situation? 
 What other problems could this technique help solve?©HSG Consulting LLC 12
  • 13. Helene Gidley, Owner, Senior Project Manager HSG Consulting, LLC Helene.gidley@hsgconsultingllc.com Carissa Demetris, Principal User Experience Designer ProQuest Carissa.demetris@proquest.com©HSG Consulting LLC 13
  • 14.   “ It’s the most fun I’ve had today”   Really helps in understanding the workflow   Very beneficial in identifying gaps in requirements   Useful in defining release targets   Provides forum for discussion and clarifying expectations among team members   Simpler, clearer stories and acceptance cases©HSG Consulting LLC 14