This document discusses how UX can be integrated into Agile methodologies. It outlines some common challenges like the "superstar designer" who works alone and the "beast-feeder" who becomes a bottleneck by being integrated into development teams. It proposes solutions like pairing designers with developers, using low-fidelity prototypes, and rapid testing. It also recommends design spikes and sprints to maintain vision and address bigger problems in short workshops. The conclusion is that both UX and Agile need buy-in, UX is not just graphic design, and iterative design with space for creativity is important while maintaining a product roadmap.

1. How does Agile do UX?
6 Agile UX scenarios

2. Why traditional Agile doesn’t work for UX
The primary focus of Agile methodologies is the delivery of quality software
The primary focus of User Experience Design is the delivery of experiences

3. Customer ≠ End User

4. Agile Manifesto

5. Quality in Agile

6. IDEO’s design thinking

7. UK Design Council’s Double Diamond Methodology

8. UX strategy

9. Is there no hope?

11. - Highly Creative
- Works in Photoshop, Illustrator
- Sits alone in their room
- Perfectionist
- Produces beautiful designs
- Can become protective and defensive of their
work

12. The Superstar Designer can be the result of :
1. Shoehorning Design into Agile practices
2. Unmatched expectations in hiring - Graphic Design vs UX

13. Solving the Superdesigner problem

14. Erik Flowers
“UX is the intangible design of a strategy
that brings us to a solution”

15. UX vs UI

18. - The UX is integrated into the Agile
team
- Works one sprint ahead of dev
- But they have become a bottleneck
- Dev is frustrated by changing
requirements
- UXer feels can’t do proper design

19. Solving the Beast-Feeder problem
Software Development ≠ Product Development

20. Solving the Beast-Feeder problem
Are design and development priorities aligned?
● Involve the whole team in designing the next iteration
● Pair designers with developers and include developers in design review and
collaborative design practices
● Living design guidelines

21. Solving the Beast-Feeder problem
Is designer doing “Just enough design”?
● Lo-Fi wireframes
● Conversations are often more valuable than deliverables
● Rapid prototyping
● Discount User Testing methods

23. - Agile is fairly mature in the organisation
- Several cross-functional scrum teams with an embedded
designer
- UXers are involved in Agile activities
- The do Just Enough Design
- Pair with Devs
- Share results of user testing with the team

24. How do we make sure we don’t get lost in small
design problems and keep track of the big picture?

25. Design Spikes

27. “Basically it’s a process of structured
brainstorming for answering critical business
questions through design, prototyping, and
testing new ideas with users throughout one
to five days workshop”

28. The Google Design Sprints
Monday: Understand and define
Tuesday: Divergent design activities.
Wednesday: Decide on which ideas to go for. Create a Storyboard
Thursday: Prototype the storyboard.
Friday: Validate. Test your prototype with users

31. - Isolation
- Loss of vision
- Broken UX
- Lots of increments but no
innovation

32. Managing a growing UX team in Agile
- Good Cop/Bad Cop Design pairs
- Design guilds
- Design leadership
- Storyboards VS Product Roadmaps
- Design systems

35. Build - Measure - Learn

36. Conclusion
- The organisation needs to buy into Agile and understand what UX is
- UX is not Graphic Design
- UX needs to be integrated into the Agile methodologies
- Design needs to be iterative, but leave space to be creative as well
- Design vision set in Design Spikes and Sprints
- Evolve UX leadership
- Lean UX or Agile UX
No silver bullet!

37. Thanks!
Aurora@forecast.it
@roarsdraws