Organizing UX and Developers is a pain we all suffer. Based on feedback from different communities and from my recent experiments, the talk will give you insights into why Scrum is not the best tool to solve those pains.

1. UX & DEV
Why Scrum is not the answer?

2. Parallel Tracks
Scrum
Kanban
Mini-Waterfall
How to organize UX & DEV?
DesignSprint

3. UX & DEV

4. <John Doe> : Parallel Tracks / mix
approach where research is made
outside of the sprint.
<Agile Consultant> : mixing flight
levels with parallel tracks
Big Company : some teams work
in Kanban others in Sprints... in the
sprint teams, the UX is done at the
same time as Development.
Curious that in the sprint setup,
some teams are moving away from
that model and taking out the
UX/Research from the Sprints
UX & DEV

5. UX & DEV : Team?!

6. What is a Scrum team
Cross-functional teams have all competencies
needed to accomplish the work without
depending on others not part of the team
Incremental deliveries of "Done" product ensure
a potentially useful version of working product
is always available.
Development teams are cross-functional, with all
the skills as a team necessary to create a
product Increment

7. … and how about UX?
● User behaviour provided in the interaction with a product
● Focus placed on the quality of the user experience
● Elements
○ Research
○ Visual Design
○ Information architecture
○ Usability
○ Accessibility
○ Human-Computer Interaction

8. UX Process
Achieved without:
❏ Working product
❏ Creating a product increment

9. UX & AGILE
without
depending on
others

10. Not Scrum
UX DEV

11. … my recent endeavours

12. Head of
Technology
Engineering LeadProduct Lead
Product Owners UX/UI Designers Developers QA

13. W1 W2 W3 W4
Design
(sprint)
Develop
(sprint)
How we were organized?
Problems
● Mini-waterfall
● Silos
● Handover
● Involvement
● Understanding
● Ping-pong effect

14. We decided to go
“Super Saiyan”
...an experiment

16. UX (Kanban), UI+DEV (Scrum)
UX Research
(kanban)
UI Design + Develop
(sprint)
organic W1 W2

17. We gained agility & team work
Research +
Hi-Fi UI
Implementation
Implementation
before
after
Research +
Low-Fi UI
Hi-Fi UI
Agility
This is the
agility we’ve
gained
teamwork
we’ve gained

18. Changes… and reality

19. Lead Time improvements

20. Feedback & Experiments

21. Scrum is not the
only tool...
If your only tool is a hammer...