This document discusses various techniques for understanding users and their contexts in order to design effective products. It covers understanding user types, goals, and contexts. It also discusses building user roles, developing personas, considering extreme personalities, interaction contexts, and user needs at different times of day. The document provides examples and exercises for applying these techniques.
At the start of a project or start of a major release, we always face the problem of "How do we break down this big release into stories?" " How do I move from this vision to lower level details in user stories?". My workshop & presentation at the #India Agile Week 2013 Pune was focussed on providing answers to this. This presentation provides a way to move from high level vision to user stories using Story Map.
At the start of a project or start of a major release, we always face the problem of "How do we break down this big release into stories?" " How do I move from this vision to lower level details in user stories?". My workshop & presentation at the #India Agile Week 2013 Pune was focussed on providing answers to this. This presentation provides a way to move from high level vision to user stories using Story Map.
What are User Stories? How should we write them? How to write them well?
Effective User Stories allow your team to be effective (deliver want the User needs) and efficient (Deliver it quickly and importantly don't deliver unneeded features).
Techniques for Effectively Slicing User Stories by Naresh JainNaresh Jain
In order to achieve my goals, as a buyer of your product, I want awesome feature. AT: make sure your users stories don't get in the way.
Users Stories, the tool teams use to break big ideas into small demonstrable deliverable, are easy to describe and challenging to write effectively. In this hands-on workshop you'll learn how to write great user stories and acceptance criteria, that everyone on the team understands. We'll learn various techniques to slice your stories using the tracer-bullet approach. We will discuss what elements should be included in the stories, what criteria you should keep in mind while slicing stories; why the size of your user story is important and how to make them smaller and efficient.
Agenda:
What do you do to Large Stories? Spike, Split, Stub & Timebox (SSST) technique.
Core Slicing Techniques:
1. System Slice
1.a. Static vs. Dynamic
1.b. Real-time vs. Batch Processing
1.c. Build vs. Buy
1.d. Automated vs. Manual Steps
1.e. Defer certain roles
2. Behavioural Slice
2.a. Adjusting Sophistication - MVF (Minimum Viable Feature) or Walking Skeleton
2.a.1. Acceptance Criteria
2.b. By-pass certain steps in the workflow
2.c. Focus on Happy Path First (edge cases later)
2.d. No options - 1 option - Many options
3. Incrementally improve ‘Ilities' (Usability, Scalability, Reliability, etc.)
3.a. Simpler UI (even consider using a standard UI)
3.b. Minmal Data
3.c. Improve Performance Iteratively
User Stories Writing - Codemotion 2013Fabio Armani
Stefano Leli (Freelance) - Fabio Armani (OpenWare)
Scrivere user stories dovrebbe essere facile...almeno in teoria. In realtà nella pratica ci troviamo troppo spesso a combattere con storie vaghe o troppo tecniche, storie che non possono essere testate o addirittura che non portano alcun valore. In questo workshop cercheremo assieme di comprendere la differenza tra requisiti funzionali e User Story, tra User Story e Use Case, mediante dei case study.
This presentation provides the who, what, why, how, and when for user stories. It shows you examples of good and bad stories, how to get them in the first place, and how they define done on agile projects.
This presentation describe
What is the need for user stories in Agile project?
What is a story?
Why story?
What is criteria for a good story?
What are not stories?
Prerequisite? Knowledge of Scrum and it’s terms
Douglas Talbot & Sandy Mamoli
One of the most fundamental problems facing a project is how you decide on, document, and manage your requirements.
Obviously Agile software development promotes handling this very differently than a Waterfall approach. One mechanism used by Agile projects to track requirements is the "User Story" - but what are they, how are they created, who uses them, when and how, within the development cycle?
Writing Good User Stories (Hint: It's not about writing)one80
User stories are typically the foundation of the Product Backlog. However, the original purpose has been lost. This is from a presentation that was given to help remind everyone of what User Stories are, and what they aren't. The purpose of User Stories is to drive conversations, not to hand "requirements" from one group to the next.
What are User Stories? How should we write them? How to write them well?
Effective User Stories allow your team to be effective (deliver want the User needs) and efficient (Deliver it quickly and importantly don't deliver unneeded features).
Techniques for Effectively Slicing User Stories by Naresh JainNaresh Jain
In order to achieve my goals, as a buyer of your product, I want awesome feature. AT: make sure your users stories don't get in the way.
Users Stories, the tool teams use to break big ideas into small demonstrable deliverable, are easy to describe and challenging to write effectively. In this hands-on workshop you'll learn how to write great user stories and acceptance criteria, that everyone on the team understands. We'll learn various techniques to slice your stories using the tracer-bullet approach. We will discuss what elements should be included in the stories, what criteria you should keep in mind while slicing stories; why the size of your user story is important and how to make them smaller and efficient.
Agenda:
What do you do to Large Stories? Spike, Split, Stub & Timebox (SSST) technique.
Core Slicing Techniques:
1. System Slice
1.a. Static vs. Dynamic
1.b. Real-time vs. Batch Processing
1.c. Build vs. Buy
1.d. Automated vs. Manual Steps
1.e. Defer certain roles
2. Behavioural Slice
2.a. Adjusting Sophistication - MVF (Minimum Viable Feature) or Walking Skeleton
2.a.1. Acceptance Criteria
2.b. By-pass certain steps in the workflow
2.c. Focus on Happy Path First (edge cases later)
2.d. No options - 1 option - Many options
3. Incrementally improve ‘Ilities' (Usability, Scalability, Reliability, etc.)
3.a. Simpler UI (even consider using a standard UI)
3.b. Minmal Data
3.c. Improve Performance Iteratively
User Stories Writing - Codemotion 2013Fabio Armani
Stefano Leli (Freelance) - Fabio Armani (OpenWare)
Scrivere user stories dovrebbe essere facile...almeno in teoria. In realtà nella pratica ci troviamo troppo spesso a combattere con storie vaghe o troppo tecniche, storie che non possono essere testate o addirittura che non portano alcun valore. In questo workshop cercheremo assieme di comprendere la differenza tra requisiti funzionali e User Story, tra User Story e Use Case, mediante dei case study.
This presentation provides the who, what, why, how, and when for user stories. It shows you examples of good and bad stories, how to get them in the first place, and how they define done on agile projects.
This presentation describe
What is the need for user stories in Agile project?
What is a story?
Why story?
What is criteria for a good story?
What are not stories?
Prerequisite? Knowledge of Scrum and it’s terms
Douglas Talbot & Sandy Mamoli
One of the most fundamental problems facing a project is how you decide on, document, and manage your requirements.
Obviously Agile software development promotes handling this very differently than a Waterfall approach. One mechanism used by Agile projects to track requirements is the "User Story" - but what are they, how are they created, who uses them, when and how, within the development cycle?
Writing Good User Stories (Hint: It's not about writing)one80
User stories are typically the foundation of the Product Backlog. However, the original purpose has been lost. This is from a presentation that was given to help remind everyone of what User Stories are, and what they aren't. The purpose of User Stories is to drive conversations, not to hand "requirements" from one group to the next.
User stories are core to many agile methodologies but are often misunderstood by those new to agile. However, proper user stories are important for planning, scoping, delivering value, and change management. This hands-on event will be spent creating, evaluating, and hopefully improving our own user story skills. Bring post-its and sharpies.
The video for this presentation is available here: http://vimeo.com/33850718
ATDD And BDD The Great Beat Down…or…DebateTEST Huddle
Key Takeaway’s
1. - A solid overview of the intent behind the User Story as a requirement artefact.
2. - A solid overview of Acceptance Test Driven Development, including Behavior-Driven Development.
3. - An understanding of the intent behind Acceptance Criteria.
4. - An understanding of the balance required in the User Story and the Acceptance Criteria/tests.
View the webinar here - https://testhuddle.com/atdd-and-bdd-the-great-beat-down-or-debate/
Agile Architecture and Modeling - Where are we TodayGary Pedretti
Ideals, Misinterpretations, Backlash, a New Hope - A talk on where we've been and where we're going with agile application architecture. As presented at Toronto Agile and Software 2014 on 11/10/2014.
User Story Mapping Workshop (Design Skills 2016)Bartosz Mozyrko
User Story Mapping (USM) is a top-down approach of gathering "requirements" in agile environments.
"A user story map arranges user stories into a useful model to help understand the functionality of the system, identify holes and omissions in your backlog, and effectively plan holistic releases that deliver value to users and business with each release (from Jeff Patton's The New User Story Backlog Is a Map)."
User Story Mapping, Discover the whole storyJeff Patton
Variations of these slides have been used in a variety of talks.
These slides support discussions on why stories work, and when they don't. And, on story mapping, how and why it works.
Creating a backlog of user stories is pretty straight forward but it doesn't help you when it comes to decisions like what to build first, how to prioritize and groom the backlog, how to scope and plan the project, and how to visualize progress. The traditional backlog is simply too flat and often too long to help you see the bigger picture and make good decisions. User Story Mapping helps simplify all of these common project issues. By adding a third dimension to your backlog, your team will make better decisions about priorities, scope, and planning while improving your ability to visualize progress.
In this practical session I’ll cover the basics of user story mapping before walking you through case studies of how our teams are using this approach and the results we are achieving. I'll show you the before, during, and after pictures from several projects so that you can understand how our maps progress during the projects and how we use them to influence iterative development, promote good decision making, and visualize priorities, plans, scope and progress.
This tutorial teaches you how to employ the Product Canvas, an agile UX tool that helps you create a product with a great user experience and the right features. Download the Product Canvas at: http://www.romanpichler.com/tools/product-canvas/
This presentation covers the why, who, what and when of writing requirements for Agile projects. Then we look at an example and how we can use mindmapping to brainstorm
Personas - redesigning their content, rethinking their formBen Crothers
This is for UX designers, HCI and service designers, as well as anyone in product strategy, marketing and product management. At IxDA on Thursday 27 Nov 2014, I shared how we at Atlassian redesigned our personas. But what's more important is how you can re-think your personas and not only design their *content* the right way, but their *form* in a new way, to make them much more intuitive to use.
Create Knowledge with Users at Agile Korea 2013Kenji Hiranabe
My presentation at Agile Korea 2013, Sept.7
Scrum is a word used in "New Product Development" first by Ikujiro Nonaka. I explained his knowledge creation model, SECI.
1. People as the conveyor of the knowledge
2. Mindmapping for User Interview
Let's break the wall between developers and users!!
Leveraging Data in EMEA: LinkedIn Recruiter, Jobs, & Talent Pool Analysis | T...LinkedIn Talent Solutions
Does data play an important role in your recruiting efforts? Learn how your data can strengthen your recruiting success across Europe.
Find all LinkedIn Talent Pool Reports here on SlideShare: http://slidesha.re/15ryPlr
Learn more about LinkedIn Talent Solutions: http://linkd.in/1bgERGj
Subscribe to the LinkedIn Talent Blog: http://linkd.in/18yp4Cg
Follow the LinkedIn company page: http://linkd.in/1f39JyH
Tweet with us: http://bit.ly/HireOnLinkedIn
This is seminar report on Sentiment Analysis.This report gives the brief introduction to what is sentiment analysis?what are the various ways to implement it?
Keynote presented at ILA19 - Interaction Latin America, in Medellín CO.
Some tips on how to create personas (characterization of a specific customer group) from my own professional experiences leading UX Research challenges and creating personas from millions of users.
UXPA 2023: Learn how to get over personas by swiping right on user rolesUXPA International
This session walks through the concept of user roles as an alternative to personas as a means to generate and disseminate user insights for product development teams. We will describe the tools and methods used to create a research database organized by user roles, along with examples and short exercises to help attendees think through user roles within their own context.
By the end of the session, attendees should be aware of tools and approaches for:
Organizing user research information in a database
Disseminating user role information to product and design teams
Managing a user roles database as part of a long term UX Research program
If you’re ready to ditch personas but don’t know how, this session is for you!
This is an introductive session for software engineers about the user experience. Including psychological concepts, identification of user goals, wireframing, mockups, prototyping and practical examples which you want to understand as software engineers those who practising UX.
With Fashion Week to inspire us, this webinar focuses on sharing a few favorite digital trends for 2018. Instead of discussing denim separates and art-inspired prints, our team explores hot digital to keep an eye on. The webinar focuses on emerging technologies, exciting design trends and standout digital strategies to adopt in the new year.
Associate Creative Director Jessica DeJong and Chief Strategist Kalev Peekna dive into concepts that could disrupt how we think about digital experiences, as well as trends to easily fold into your 2018 marketing strategy.
Access the full recording: https://youtu.be/N_4XAsXDoYI
Similar to User Stories Workshop For Agile Product Development (20)
2. Constituents & Context
Business Goals Drive Constituencies and Context.
Business Goals:
• Improve Click Rate.
• Motivate Sale of Digital Products.
• Accelerate Mobile Search Capability.
• Establish A/B Testing in Design.
User Constituencies:
• Advertiser.
• Housewife.
• Mobile User.
• …..
Usage Contexts:
• Desktop.
• Laptop on Airplane.
• iPad.
• …..
R. Anantha Narayanan, CSPO, CSP 2
3. Understand Use
To design a product we need to Understand Use.
User Type
Actor
User Role
Persona
User Goal
What am I trying to accomplish with the product ?
What will make me happy when using the product ?
User Context
When will I use the product ? Where will I be at that
time ?
What other thing I may be doing when I Use the
product ?
R. Anantha Narayanan, CSPO, CSP 3
4. User Roles
User Roles are a best choice for
aggregating individual users of a
system.
A User Role reflects the common
interactions of a set of users have in the
system.
User Roles allow stories to be written
with multiple perspectives.
Map Searcher, Keyword Searcher, Walk-In User, Mobile User,
Category Searcher, Google User, Advertiser, monitor.
R. Anantha Narayanan, CSPO, CSP 4
5. Build User Roles
Brainstorm Roles.
Categorize them on broad system
boundaries.
Find overlap between roles within a
category and consolidate.
Identify individual attributes for the roles
and record them.
Map Searcher, Keyword Searcher, Mobile User, Category Searcher,
, Advertiser,.
R. Anantha Narayanan, CSPO, CSP 5
6. Long , Long, Ago …
there was a swamp in central valley and a
diverse group of people had different ideas
on how to use the land. One Afternoon a
group of interested folks came together to
talk about their ideas about what to do with
the land, but…
• Who are these people ?
• Why do they care about this swamp ?
Your Job in Next 10 minutes is to find those people and
write them down. Also write what is their motivation to
come together ?
R. Anantha Narayanan, CSPO, CSP 6
7. Personas
Alan Cooper, The Inmates are Running the Asylum.
Deep Dive into User Roles.
Idea is, if you want effective products
then design it for specific user.
Paint a persona with real names,
personalities, motivations and even a
face.
„Mary Saver‟ works in AT&T as a sales manager. She is 35 years old
married with two kids, her husband is a small business owner. She
is a savvy technology user and loves her iPhone. She is big on
finding deals and uses social networking to find deals and also
shares deals with her network.
R. Anantha Narayanan, CSPO, CSP 7
8. Long , Long, Ago ……2
now that you know who came together to
discuss the land use, develop personas
that match the roles and motivation you
identified in the first step. (10 mins)
Paint a vivid picture of the user roles you have identified,
make them as personalized as possible.
Avoid detailing how they will use the land, instead focus on
their intentions, motivations and general behavior.
R. Anantha Narayanan, CSPO, CSP 8
9. Avoiding Tunnel Vision
Take a look at the requirements of Dex
Learning Center (2 mins).
You know they are incomplete , but the
problem is not knowing how they are
incomplete.
Need to go beyond obviousness to
create resilient products.
R. Anantha Narayanan, CSPO, CSP 9
10. Extreme Personas
Look at the requirements of DLC (2 mins).
Take Five Index Cards and write down names
of five personas that are popular. Select a mix
of Extreme Personalities (60 seconds).
When Complete Pass the Index Cards to the
person on your right.
Write down the feature this Persona will want
from the system. (4 mins).
Pass the cards to the person on your right.
Now write why this feature would be valuable
to this persona. (6 mins)
Discuss Results (6 mins)
R. Anantha Narayanan, CSPO, CSP 10
11. Interaction Context
Interaction Context is a an abstract
place in your system that supports
number of User tasks (Jeff Patton, Design Thinking)
Normally when the goal of the user
changes then an interaction context
switching happens.
Starting Point: give the user a clear starting point for
starting a search for businesses in the site.
Search Return: Evaluation: help the user decide if the
searched for items were the items she was looking for or
an easy way to reinitiate the search if not.
R. Anantha Narayanan, CSPO, CSP 11
12. Time of the Day
Imagine you are the Users of DLC.
In pairs walk over to the Wall Board with
Time Frames written down.
At each time frame in the wall board, take
an index card and write down a DLC
persona,
Write, what do you imagine this persona
needs from the DLC system on that time,
Write, what activities they might be doing
on that time frame and stick it to the wall.
Go to each time frame in the wall board
and repeat the exercise.
R. Anantha Narayanan, CSPO, CSP 12
13. Acceptance Criteria
Be explicit
“The system will display the date.” …
In what format? Is “2006, April 1st” acceptable?
Provide examples for clarity
“The system date will be displayed in the format 1/4/06”
List any assumptions you made.
Specify your expectations of what should be
done loudly.
“The category selection should have a default.”
Also be clear about what the system is not
expected to do
“User Registration is not expected at this time.”
R. Anantha Narayanan, CSPO, CSP 13
14. Essential Use Case (Constantine & Lockwood)
An Essential Use Case is a good method to map Acceptance
Criteria.
A use case focusing on the interaction
between user and system
Avoid describing what the user
specifically does by focusing on the
user‟s intention
Determine the system responsibilities
based on user goals
R. Anantha Narayanan, CSPO, CSP 14
15. Essential Use Case (Constantine & Lockwood)
An Essential Use Case is a good method to map Acceptance
Criteria.
As a casual browser I want to find the most
reviewed restaurant for a particular category
so that I can get more information to make a reservation.
Write an Essential Use Case for this User Story.
(10 minutes)
Exchange your Essential Use Case within your group and
write Acceptance Criteria from the Use Case. (10 mins)
R. Anantha Narayanan, CSPO, CSP 15
16. Splitting Stories
A story that is difficult to estimate is a good candidate for splitting.
1. Try to find splits that produce value.
2.. Try for symmetrical splits that gives
stories that are equal and small.
3.. Splitting stories is a skill that is
developed through experience.
4.Identifying patterns is a key skill for
splitting stories.
R. Anantha Narayanan, CSPO, CSP 16
17. Splitting Stories
A story that is difficult to estimate is a good candidate for splitting.
1. Most teams try to split stories by
architectural boundaries such as one for
UI, one for DB, one for Backend, even
though these stories are small they fail
the Independent and Valuable step.
1 2 3
UI UI UI
APP APP APP
DB DB DB
R. Anantha Narayanan, CSPO, CSP 17
18. Splitting Stories
A story that is difficult to estimate is a good candidate for splitting.
Split on Work flow steps
As a content manager, I can publish a news story to the corporate website.
…I can publish a news story directly to the corporate website.
…I can publish a news story with editor review.
…I can publish a news story with legal review.
…I can view a news story on a staging site.
…I can publish a news story from the staging site to production.
R. Anantha Narayanan, CSPO, CSP 18
19. Splitting Stories
A story that is difficult to estimate is a good candidate for splitting.
Split on CRUD boundaries
As a user, I can manage my account.
…I can sign up for an account.
…I can edit my account settings.
…I can cancel my account.
R. Anantha Narayanan, CSPO, CSP 19
20. Splitting Stories
A story that is difficult to estimate is a good candidate for splitting.
Split on Architectural Spikes aka not knowing
the implementation.
In the “investigate” story, the acceptance criteria
should be questions you need answered.
Do just enough investigation to answer the
questions and stop..
As a user, I can pay by credit card.
Investigate credit card processing.
Implement credit card processing.
R. Anantha Narayanan, CSPO, CSP 20
21. Splitting Stories - Pitfalls
Some times small stories have their own problems.
1. Small Stories stop making sense individually and kill conversations.
2. The „so that…‟ part becomes meaningless.
R. Anantha Narayanan, CSPO, CSP 21
22. Find the Patterns
Match the Stories to the Patterns (10 mins)
I want to search for jobs I am interested in.
I want to manage my business profile.
I can search for a business based on geo-location.
I want to register using my social profile.
I can search for businesses in categories.
Workflow Data Simple/
CRUD Spike
Steps Entry Complex
1. Take five Index Cards and write the stories in them
2. Now match the Stories to Work flow patterns and write them in the Index
Card.
3. Walk to the Wall Board and Stick your Stories to the Patterns that you have
chosen
R. Anantha Narayanan, CSPO, CSP 22
23. SEE YOU
Q&A
Thank You
@tekzenpdm
tekzenpdm.blogspot.com
Credits:
User Stories Applied for Agile Product Development, Mike Cohn
Design Thinking, Jeff Patton
Look Forward Consulting, Carlton Nettleton.
.
R. Anantha Narayanan, CSPO, CSP 23
Editor's Notes
A single task can be used by many users in the system for example a Time sheet Entry.By selecting roles , Users can be grouped by the interactions they have in the system, managers, employees, contractors.
Involve all possible stake holders together to develop user rolesUse Index Cards to write down roles.Identify usage by the roles to categorize. For example mobile searcher, geographic searcher, keyword searcher belong to same category whereas advertiser is not.
Come a group and discuss your choices.
Incomplete requirements makes you think If I could encourage people to “think out of the box”, then there is a chance of getting beyond essential requirements.When teams work with User stories they learn pretty quickly to identify the obvious requirements, however building for current market needs will leave the product vulnerable for low-cost, disruptive attacks.
Six MinutesWhat were the User Stories Like?How did this experience compare to previous experiences ?Was this a creative experience ?How can we improve Out of the box thinking in writing User Stories ?
The product may be static but our relationship to it changes based on how we use it.Interaction context switching happens based on lots of factors including when, where, age, experience etc.One of the most used change in context is when, aka time of the day.
user action system response insert card in ATM read card request PIN enter PIN verify PIN display option menu select option display account menu select account prompt for amount enter amount display amount confirm amount return card take card dispense cash if available
Most teams try to split stories by architectural boundaries such as one for UI, one for DB, one for Backend, even though these stories are small they fail the Independent and Valuable step