Agile & elusive big pic lutx
•Download as PPTX, PDF•
2 likes•452 views
This document discusses how story mapping can help development teams maintain the big picture view of a project. It describes how user stories are typically written from sources like user research and product goals. The document advocates moving to a more user-centered approach where stories are written in the third person based on personas developed from user research. Story mapping techniques are presented as a way to organize user stories into a visual map that shows the overall flow and context of tasks. Maintaining an up-to-date story map can help teams make better decisions and ensure nothing is missed from the project scope.
Recommended
More Related Content
Viewers also liked
Viewers also liked (17)
Similar to Agile & elusive big pic lutx
Similar to Agile & elusive big pic lutx (20)
Recently uploaded
Recently uploaded (20)
Agile & elusive big pic lutx
- 1. Agile & the elusive big picture HOW STORY MAPPING CAN FRAME A PROJECT
- 2. Getting Started 03/07/2017Agile and the Elusive Big Picture: using story maps 2
- 3. Objectives Students will be able to: Identify where user stories come from Write user-centered user stories Organize user stories into a story map Maintain a story map for a team Access resources for practice on their own 03/07/2017Agile and the Elusive Big Picture: using story maps 3
- 4. Where do user stories come from? 03/07/2017Agile and the Elusive Big Picture: using story maps 4
- 5. Project charter • Product roadmap and associated goals • Project goals as described in the project charter 03/07/2017Agile and the Elusive Big Picture: using story maps 5
- 6. Other sources of user stories? Conversations with users: Support team Sales & pre-sales User experience (UX) Monitoring user communities Other? 03/07/2017Agile and the Elusive Big Picture: using story maps 6
- 7. Writing user stories MOVING TO A USER- CENTERED PERSPECTIVE 03/07/2017Agile and the Elusive Big Picture: using story maps 7
- 8. Traditional user stories As a <role> I can <activity> So that <business value> 03/07/2017Agile and the Elusive Big Picture: using story maps 8
- 9. Moving from traditional stories Problem with the traditional – structurally flawed: Roles are not suitable focus of attention for many systems The “As a <role> I want form is unnecessarily wordy and repetitive The use of first person is counter-productive 03/07/2017Agile and the Elusive Big Picture: using story maps 9
- 10. Moving to User-Centered Stories The first person focus can lead development into believing that the users are similar to them. You are not your user! Given this perspective, what can we do? 03/07/2017Agile and the Elusive Big Picture: using story maps 10
- 11. Building user-focused user stories Minimal – each primary persona requires a different interface Collaborative – the core team should be involved in the development of the personas 03/07/2017Agile and the Elusive Big Picture: using story maps 11
- 12. Persona stories / scenarios They are written as third person stories They are written with the user experience (UX) team in collaboration with the business analysts and core team members They are based on research that discovers the needs and behaviors of the persona 03/07/2017Agile and the Elusive Big Picture: using story maps 12
- 13. ExerciseOne: UnderstandingUsers For our exercise, take a couple of minutes and interview the person sitting next to you about how they manage and use email 03/07/2017Agile and the Elusive Big Picture: using story maps 13
- 14. User-focused user story form <persona[:role]> <performs a task> [so that]<unobvious goal> The optional “so that” clause should be provided only if the goal of the task is not obvious. “Julie adds an item to the shopping basket” does not really need an explanation 03/07/2017Agile and the Elusive Big Picture: using story maps 14
- 15. Creating context By focusing on the users’ activities and tasks, we keep the context of the entire project We build the map to tell the Big Story about the system 03/07/2017Agile and the Elusive Big Picture: using story maps 15
- 16. ExerciseTwo: Practicewritinguserstories Write user stories about Managing Email Since we are all using the same persona, start with a verb. 03/07/2017Agile and the Elusive Big Picture: using story maps 16
- 17. Creating a story map 03/07/2017Agile and the Elusive Big Picture: using story maps 17
- 18. ExerciseThree:Creating sharedunderstanding Read them aloud within your group and place them on the table in front of you. Remove any duplicates. 03/07/2017Agile and the Elusive Big Picture: using story maps 18
- 19. ExerciseFour: Startingthemap As a team, group the sticky notes, putting items that are similar to one another together. If different, put them farther apart. 03/07/2017Agile and the Elusive Big Picture: using story maps 19
- 20. ExerciseFive:Arranging themap Arrange the groups from left to right in the order a user would typically complete the tasks. Use a different color sticky to name the groups. 03/07/2017Agile and the Elusive Big Picture: using story maps 20
- 21. You should have something that looks like this ©Winnipegagilist.blogspot.com 03/07/2017Agile and the Elusive Big Picture: using story maps 21
- 22. ExerciseSix:Slicingthe userstories Break down or “slice” the tasks into sub- tasks 03/07/2017Agile and the Elusive Big Picture: using story maps 22
- 23. Walking the backbone / skeleton This is the process of making sure that you haven’t left out any tasks. You can walk through user scenarios or even ask users to walk through their job functions to make sure no tasks have been missed. 03/07/2017Agile and the Elusive Big Picture: using story maps 23
- 24. An example 03/07/2017Agile and the Elusive Big Picture: using story maps 24
- 25. An example 03/07/2017Agile and the Elusive Big Picture: using story maps 25 High Priority Slices
- 26. Why Story Mapping? 03/07/2017Agile and the Elusive Big Picture: using story maps 26
- 27. Why Story Mapping? 03/07/2017Agile and the Elusive Big Picture: using story maps 27 1. It allows you to see the BIG Picture. 2. It creates shared understanding of the project. 3. It is a tool for better decision making. 4. It encourages iteration. 5. It’s a useful model for discussing & managing scope.
- 28. Story mapping is the beginning Other techniques to build great products: Creating minimal valuable solutions Creating customer journey maps Creating product ecosystem maps Encouraging design thinking 03/07/2017Agile and the Elusive Big Picture: using story maps 28
- 29. ...in the end The biggest waste of all is building something no one wants.” 03/07/2017Agile and the Elusive Big Picture: using story maps 29 Eric Ries Author of Lean UX
- 30. Story mapping Tools http://Storiesonboard.com http://Featuremap.co http://Cardboardit.com http://Boardthing.com https://mural.co 03/07/2017Agile and the Elusive Big Picture: using story maps 30
- 31. References Patton, Jeff (2014) User Story Mapping: Discover the Whole Story, Build the Right Product, O’Reilly Gigante, Andrea (2013) Creating an Agile Road Map using Story Mapping www.scrumalliance.org Rogalsky, Steve (2012) Winnipeg Agilist: User Story Mapping Series www.winnipegagilist.blogspot.com Patton, Jeff (2008) The new user story backlog it a map http://jpattonassociates.com/the-new-backlog/ 03/07/2017Agile and the Elusive Big Picture: using story maps 31
- 32. Contact information Elisa Kaplan Miller Design Transformation Coach CA Technologies Elisa.miller@ca.com 214-681-9888 Twitter: elisakm LinkedIn: /elisakmiller 03/07/2017Agile and the Elusive Big Picture: using story maps 32
Editor's Notes
- Personas start much richer discussions and help us stay focused on the users
- Stories like this facilitate a conversation with a goal of shared understanding between all of the members of the team.
- The context also includes: Customer segments Users and user goals Product uses Business strategy Legacy products and architecture
- The idea is to create a map that is a mile wide and an inch deep. It’s really about business process modeling that is focused on the user.