Icebreaker 1. Introduce yourself 2. Tell us one thing cool/unique about the space you work in, or a team/product you work with. Anything. 3. A favorite cartoon, animated film, graphic novel, or kids tv show?
Wicked Problems a wicked problem is a problem that is difficult or impossible to solve because of incomplete, contradictory, and changing requirements that are often difficult to recognize.
Have you ever… - created development tickets? - had to be a PM and a UXer? - had to write user stories for devs? - kept the team’s focus on the user? - interviewed users? - diagnose pain points?
5 Whys Technique Sakichi Toyoda, the Japanese industrialist, inventor, and founder of Toyota Industries, developed the 5 Whys technique in the 1930s. The method is remarkably simple: when a problem occurs, you drill down to its root cause by asking "Why?" five times. Then, when a counter-measure becomes apparent, you follow it through to prevent the issue from recurring.
For the purposes of this presentation… if you find any videos, reviews, testimonials – as well as if you have your own experiences or knowledge – feel free to consider/include… cross research is great.
Now… 1. Take some time to cluster similar ideas 2. Put yourself in the mind of your user and… a. Think about what steps ‘they say’ that they would take b. Does your user have a plan/need one? c. Are there phases that they would go through? 3. Share with the room
You got the touch… 1. Create columns with actions/steps user is taking “the workflow as it is today” 2. Create rows for what they are doing, thinking, and feeling 3. Work separately, and everyone makes more/new stickies!
In As-Is Mapping… Where do you think your user is experiencing pain? [it’s ok to project in this workshop, but normally we ask, or it’s evident in feedback/testing]
User Stories - As a I can , so that - As a [type of user], I want [some action], so that [outcome] “When an important new customer signs up, I want to be notified, so I can start a conversation with them.”
Setup like this… Somebody in group write the Needs Statement template at the top of your sheet 1. Incorporate User 2. Refer to Empathy Map 3. Refer to As-is Mapping 4. Refer to Pain Points
Activity Time 1. Write the Needs Statement template at the top of your sheet 2. Start writing Needs Statements to… a. Accomplish what the user needs b. Address pain points c. Summarize user problems d. Capture user needs 3. Start to mix and match, building on others
1. Rewrite the pair(s) if that helps. 2. Label the clusters. 3. Try writing one big Needs Statement that represents the entire cluster—use the same need + insight structure What did you say?
Evaluating Needs Statements Democratic evaluation (X rule voting) or voting on Needs Statements that are the strongest, most representative, best worded, etc.
Tickets !!! How do I love Scrum? Let me count the ways. I love it for its sprints of up to twenty days. The product backlog: Writing and refining! I love Scrum when I see a pile of story cards declining. I love burndown charts, or up if you prefer. They show team progress, otherwise hard to infer. I like my Scrum Master and my product owner, too. Having each makes issues easier to get through. I love Scrum with a love deeper than a waterfall. There are no impediments. I love it all. Scrum brings me joy. Work is fun. No overtime! I shall but love Scrum better if we ship on time. –Mike Cohn, Scrum Software Development Method
1. Problem is initiative (new project) 2. Needs Statements items, that have the most votes, or capture a group, become Epics. 3. Consider the different users or user roles involved needed to make that Epic happen… those become the User Stories 4. Tasks are to make that happen Let’s make a backlog
timbroadwater
minorun365
k1low
nttcom
rakus_dev
antimon2
picardparis
yamamuteki
orgachem
dahatake
pict3
kosui
notwaldorf
aleyda
phodgson
schacon
bkeepers
jponch
deanohume
jmmastey
robhawkes
addyosmani
smashingmag
shpigford