Storymapping workshop for CHI Belgium


Published on

Slides for the CHI Belgium Storymapping workshop 28 MAR 2012

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Usually in open-plan officesVery often you can see 2 people “pair programming”, sitting in front of 1 screenPeer review is crucial – features are delivered and checked in 1 sprint. (or should be)
  • Storymapping workshop for CHI Belgium

    1. 1. Story mappingWhen your story backlog is a map
    2. 2. The next hour (or so)• We’ll talk a bit about Agile Development• Teach you the fundamentals of Story Mapping• You’ll create your own Story Map Enjoy, Hans De Mondt, Jan Moons 2
    3. 3. What is agile development?• Cross-functional & self-organizing teams• Small teams• Flat organization, no hierarchy• Relatively short cycles (±2 weeks to 1 month)• Different “flavors” e.g. Scrum and XP From: Wikimedia 3
    4. 4. Product backlogFrom: Agile Product Management with Scrum 4
    5. 5. Problem with the product backlog• No holistic view• Prioritization usually based on development effort estimates rather than added value to user• Consistency? Completeness? (only in the mind of the product owner) • Poor explanation of what the system does; dev members mostly don’t have a clue what the complete system will do • Is there something missing? • Feeling of incompleteness 5
    6. 6. Real-life product backlog 6
    7. 7. Example user story "As a <role>, I want <goal/desire> so that <benefit>" As a user researcher I want to observe people using the web application So that I can detect problems and suggest a proper solution 7
    8. 8. User stories…• …look like they mind the user of the system. The aim is actually to describe the feature as concretely as possible.• … are usually not based on user research.• … are atomic and do not necessarily have context. Software developers do not always know what the feature they are working on actually does, in the context of the full product. 8
    9. 9. What is story mapping?• “Popularized” by Jeff Patton• Explained in a blogpost:• Basically turns the story backlog into a “big picture” view.• Holistic – end-to-end story 9
    10. 10. 10
    11. 11. High level to fine grain• The map is constructed from left to right• The top level are activities: big user stories that cannot be tackled in 1 sprint; example: “As an organizer I want to schedule meetings so the team can meet”• Tasks and sub-tasks are pieces of functionality that help cover the activity and can be done in 1 sprint.• We added “user roles” as a top level 11
    12. 12. The top level• In the top level the bigger user stories are shown in an order that makes sense to the user of the system• There are usually many ways to order activities Tip: List activities in the order you use when explaining the system to an outsider. That is the order. Manage Log in Manage emails Log out schedule Example for an online mail and calendar app 12
    13. 13. Tasks• User stories like you’re used to.• For ease-of-reading shorthand version is fine (so skip the “as a …” and “so that” parts)• Tasks are small enough to be picked up in 1 sprint.• TIP: if the project is heavy on UX you can add screenshots of the UI as the project progresses 13
    14. 14. Skeleton and backbone• Activities are the backbone = the big picture• Tasks are the skeleton, the higher the need, the higher the task• Tasks with equal necessity are on the same level: e.g. you can’t build a car with either an engine or brakes, they both are needed; the type of brakes or engine can be better defined later on (lower on the map) 14
    15. 15. Sprint planning activity activity task task task Sprint 1 task task Sprint 2 15
    16. 16. Releases / sprints• Support all necessary ACTIVITIES with the first release • Smallest working system with end-to-end functionality• Create a swim lane for each release / sprint • In each subsequent release improve activity support (add additional activities) • Value/benefit for the user (frequency of use) • Value/benefit for business 16
    17. 17. Side effect: from incremental to iterativeStory mapping forces you to think iterative rather than incremental. Rather have a completebut early system than a set of well-defined features and no system 17
    18. 18. Story map = communication• The story map should be present at all times• On a wall with post-its or on a TV using e.g. cardmapping 18
    19. 19. For additional features…• Sometimes additional features get their own storymap, specially if the project did not have a story map yet. Same rules apply.• Also in the case of different user roles different maps can be used. 19
    20. 20. That’s itNow it’s your turn:Build a story map for an online ice cream delivery service Any questions/remarks, just ask us 20