Agile & elusive big pic lutx

Agile & the elusive big pictureHOW STORY MAPPING CAN FRAME A PROJECT

Agile and the Elusive Big Picture: using story maps

2

Getting Started

03/07/2017


3Objectives

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/2017


4

Where do user stories come from?

03/07/2017


5Project charter

• Product roadmap and associated goals

• Project goals as described in the project charter

03/07/2017


6Other sources of user stories?

Conversations with users: Support team Sales & pre-sales User experience (UX) Monitoring user communities Other?

03/07/2017


7

Writing user stories

MOVING TO A USER-CENTERED PERSPECTIVE

03/07/2017


8Traditional user stories

As a <role>I can <activity>

So that <business value>

03/07/2017


9Moving from traditional stories

Problem with the traditional – structurally flawed:Roles are not suitable focus of attention

for many systemsThe “As a <role> I want form is

unnecessarily wordy and repetitiveThe use of first person is counter-

productive03/07/2017


10Moving 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/2017


11Building 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/2017


12Persona 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/2017


13

Exercise One: Understanding Users

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/2017


14User-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/2017


15Creating 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/2017


16

Exercise Two: Practice writing user stories

Write user stories about

Managing EmailSince we are all using

the same persona, start with a verb.

03/07/2017


17

Creating a story map

03/07/2017


18

Exercise Three: Creating shared understanding

Read them aloud within your group and place them on the table in front of you. Remove any duplicates.

03/07/2017


19

Exercise Four: Starting the m

apAs a team, group the sticky notes, putting items that are similar to one another together. If different, put them farther apart.

03/07/2017


20

Exercise Five: Arranging the m

apArrange 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/2017


21You should have something that looks like this

©Winnipegagilist.blogspot.com

03/07/2017


22

Exercise Six: Slicing the user stories

Break down or “slice” the tasks into sub-tasks

03/07/2017


23Walking 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/2017


24An example

03/07/2017


25An example

03/07/2017

High Priority Slices


26Why Story Mapping?

03/07/2017


27Why Story Mapping?

03/07/2017

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.


28Story 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/2017


29...in the end

The biggest waste of all is building something no one

wants.”

03/07/2017

Eric RiesAuthor of Lean UX


30Story mapping Tools

http://Storiesonboard.com http://Featuremap.co http://Cardboardit.com http://Boardthing.com https://mural.co

03/07/2017


31References

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/2017

https://www.scrumalliance.org/community/articles/2013/august/creating-an-agile-roadmap-using-story-mapping

http://www.winnipegagilist.blogspot.com/

http://jpattonassociates.com/the-new-backlog/


32Contact information

Elisa Kaplan MillerDesign Transformation CoachCA [email protected]: elisakmLinkedIn: /elisakmiller

03/07/2017

Agile & elusive big pic lutx

Software

Transcript of Agile & elusive big pic lutx