1. Story mappingWhen your story backlog is a map

2. The next hour (or so) Well talk a bit about Agile Development Teach you the fundamentals of Story Mapping Youll create your own Story MapEnjoy, Hans De Mondt, Jan Moons2 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: Wikimedia3 4. Product backlogFrom: Agile Product Management with Scrum4 5. Problem with the product backlog No holistic view Prioritization usually based on development effort estimates rather thanadded value to user Consistency? Completeness? (only in the mind of the product owner) Poor explanation of what the system does; dev members mostly dont have a clue what the complete system will do Is there something missing? Feeling of incompleteness5 6. Real-life product backlog6 7. Example user story"As a , I want so that "As a user researcher I want to observe people using the web application So that I can detect problems and suggest a proper solution7 8. User stories look like they mind the user of the system. The aim is actually todescribe the feature as concretely as possible. are usually not based on user research. are atomic and do not necessarily have context. Software developersdo not always know what the feature they are working on actuallydoes, in the context of the full product.8 9. What is story mapping? Popularized by Jeff Patton Explained in a blogpost:http://agileproductdesign.com/blog/the_new_backlog.html Basically turns the story backlog into a big picture view. Holistic end-to-end story 9 10. 10 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 1sprint; example: As an organizer I want to schedule meetings so theteam can meet Tasks and sub-tasks are pieces of functionality that help cover the activityand can be done in 1 sprint. We added user roles as a top level 11 12. The top level In the top level the bigger user stories are shown in an order that makessense 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.ManageLog in Manage emails Log outscheduleExample for an online mail and calendar app12 13. Tasks User stories like youre 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 asthe project progresses13 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 cant build acar with either an engine or brakes, they both are needed; the type ofbrakes or engine can be better defined later on (lower on the map)14 15. Sprint planning activity activitytasktask task Sprint 1tasktask Sprint 2 15 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. 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. 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 http://www.cardmapping.com 18 19. For additional features Sometimes additional features get their own storymap, specially if theproject 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. Thats itNow its your turn:Build a story map for an online ice cream delivery service Any questions/remarks, just ask us20