SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.
SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.
Successfully reported this slideshow.
Activate your 14 day free trial to unlock unlimited reading.
Shared learnings and practical tips on how to make UX work with Agile software development based on what The Economist UX mobile team has done in the past year.
Helping product teams deliver business result with UX/Product Consulting & Training | Focusing on Blockchain tech & ICO
Shared learnings and practical tips on how to make UX work with Agile software development based on what The Economist UX mobile team has done in the past year.
1.
@dsetia_1
UX in Agile
Danny Setiawan
Moving towards User-Centered Design Culture
Lead UX for Mobile, The Economist
New York, 04.07.2016
2.
@dsetia_1
Objective
Share insights and practical steps to improve UX
contribution in Agile based on my experience
3.
@dsetia_1
Agenda
• Intro
• UX activities
• At The Economist
• How? Change of Culture
4.
@dsetia_1
Intro
• 15+ years of experience in Product Design and UX
• Has worked with established brands (The Economist,
Yahoo!, Microsoft) as well as start ups
• Currently :
• UX Lead/Manager at The Economist
• UXD Instructor at General Assembly
• Product/UX mentor for startups
6.
@dsetia_1
Operational
• Goal: Flow (unblocking dev)
• Activity: Reacting to issues raised by developers during sprint
• UX role: Produce deliverables so dev team can complete stories
• Measure: Team’s velocity
14.
@dsetia_1
Tactical
• Goals: Flow (smooth implementation), value (what’s important for
customers)
• Activity: Preparing everything that’s required to implement stories
for upcoming sprint (prioritize use cases, test solutions)
• UX role: Contribute to story definition, prioritization and produce
deliverables addressing potential blockers
• Measure: Team’s velocity, customer satisfaction
16.
@dsetia_1
Development
Task 1 Task 2 … DoneBacklog
UX resource
Elaboration
Ideate Prototype Test Prep for dev
17.
@dsetia_1
Development
Task 1 Task 2 … DoneBacklog
Elaboration
Ideate Prototype Test Prep for dev
18.
@dsetia_1
Development
Task 1 Task 2 … DoneBacklog
Elaboration
Ideate Prototype Test Prep for dev
19.
@dsetia_1
Development
Task 1 Task 2 … DoneBacklog
Elaboration
Ideate Prototype Test Prep for dev
20.
@dsetia_1
Development
Task 1 Task 2 … DoneBacklog
Elaboration
Ideate Prototype Test Prep for dev
21.
@dsetia_1
Development
Task 1 Task 2 … DoneBacklog
Elaboration
Ideate Prototype Test Prep for dev
22.
@dsetia_1
Development
Task 1 Task 2 … DoneBacklog
Elaboration
Ideate Prototype Test Prep for dev
23.
@dsetia_1
Development
Task 1 Task 2 … DoneBacklogIdeate Prototype Test
Elaboration
Prep for dev
24.
@dsetia_1
Strategic
• Goals: Growth (customer segment and problem to solve)
• Activity: Research to identify and validate opportunities
• UX role: Facilitate discovery phase, ideate and test solution
• Measure: Acquisition metrics
25.
@dsetia_1
Development
Task 1 Task 2 … DoneBacklogIdeate Prototype Test Prep for dev
Elaboration
26.
@dsetia_1
Development
… DoneBacklog
Elaboration
Ideate + test solution
Discovery
Identify + validate new opportunities
User Research
Stakeholders’
Input
31.
@dsetia_1
“
Culture
set of beliefs, values, and behaviors, including
their embodiment in artifacts; that are
shared by a group of people
WORKING DEFINITION
32.
@dsetia_1
Culture
• Belief: How we believe things work (world view)
• Value: What we consider important (prioritize)
• Behavior: What we do to get the value based on
the world view we subscribe to
• Artifacts: Manifestation of our behavior
33.
@dsetia_1
Example
• Belief: User testing is a waste of time
• Value: Efficiency
• Behavior: Not supporting user testing initiative
• Artifacts: Email, verbal communication
34.
@dsetia_1
Practical Tips
• Start Small
• Small team, small cost, small time, small risk
• Build momentum : Many small wins > One big win
• Don’t dictate, motivate
• Provide real value (that can be felt)
• Help others succeed
• Don’t bulls#*t
• It’s ok to say “I don’t know the answer (but I can help you find out)”
• Drop the buzzwords
• Lead with a story (meaning & purpose)
• Co-create
• Be transparent about your method
• Include others in your process
• Let others contribute
35.
@dsetia_1
How we started…
• Start with unblocking dev to earn trust
• Facilitate small ideation sessions that involves the
team (proto-persona, sketching exercise , etc.)
• Visualize process, highlighting contribution UX can
make
• Support Product Owner and Scrum Master in
product roadmap creation