How do we collaborate? Ben Burton Will Evans Ben Grohe Presented at Agile Experience Design Meetup June 25th
Oct 17, 2014
How do we collaborate?
Ben BurtonWill EvansBen Grohe
Presented at Agile Experience Design Meetup June 25th
04/07/23 2
Organization sets strategic KPIs
04/07/23 3
Scrums are organized around a specific domain / customer segment
04/07/23 4
Scrum team organization
• Product Owner• Dev. Manager• Scrum Master• Product Manager• UX Lead• 3 or 4 Engineers• Copywriter• Visual Designer• Quality Assurance
04/07/23 5
High-level problem statements are articulated
(A huge fucking flood is coming -> We face extinction)
04/07/23 6
Quantitative & qualitative research is conducted to understand the nature of the problem space(s)
04/07/23 7
Focus group is pulled together with real customers to gauge needs/pains/desires/goals
04/07/23 8
Problem statements are broken down into smaller, more edible problem statements
04/07/23 9
Product owner does not present scrum with solutions (you will build an Ark!)
04/07/23 10
Team brainstorming and/or design studioShitload of ideas are generated
04/07/23 11
Problem statements are turned into hypotheses
04/07/23 12
Ideas are turned into stories based on sketches or wireframes (based on size of potential solution)
04/07/23 13
Not all deliverables are bad.
04/07/23 14
Sometimes, no deliverables at all are needed
04/07/23 15
Metrics are agreed upon to define choice set of pivot or persevere
04/07/23 16
Use Trello to pull stories through the flow
04/07/23 17
Validate sketches/designs/mocks/prototypes with real users in usability testing
04/07/23 18
Share everything with the team
04/07/23 19
Release the damn thing (in small, testable chunks)
04/07/23 20
We have deep BI expertise, but sometimes, we need numbers faster….
04/07/23 21
Use Mixpanel to move quantitative analysis down to the scrum team
04/07/23 22
Report learnings back to product owner
04/07/23 23
If fail, pivot. If succeed, celebrate & iterate
04/07/23 24
25