Download as PDF, PPTX
Uploaded byForecast
Agile in UX
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.
More Related Content
![Copy of Presentation - [Your Organization Name]_20250924_181258_0000.pdf](https://cdn.slidesharecdn.com/ss_thumbnails/copyofpresentation-yourorganizationname202509241812580000-251117131601-9744dd2d-thumbnail.jpg?width=640&height=640&fit=bounds)
Agile in UX
- 1. How does Agiledo UX? 6 Agile UX scenarios
- 2. Why traditional Agiledoesn’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 ≠ EndUser
- 4.
- 5.
- 6.
- 7. UK Design Council’sDouble Diamond Methodology
- 8.
- 9. Is there nohope?
- 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 Designercan be the result of : 1. Shoehorning Design into Agile practices 2. Unmatched expectations in hiring - Graphic Design vs UX
- 13. Solving the Superdesignerproblem
- 14. Erik Flowers “UX isthe intangible design of a strategy that brings us to a solution”
- 15.
- 18. - The UXis 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-Feederproblem Software Development ≠ Product Development
- 20. Solving the Beast-Feederproblem 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-Feederproblem Is designer doing “Just enough design”? ● Lo-Fi wireframes ● Conversations are often more valuable than deliverables ● Rapid prototyping ● Discount User Testing methods
- 23. - Agile isfairly 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 wemake sure we don’t get lost in small design problems and keep track of the big picture?
- 25.
- 27. “Basically it’s aprocess 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 DesignSprints 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 - Lossof vision - Broken UX - Lots of increments but no innovation
- 32. Managing a growingUX 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 organisationneeds 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.