Scrum & UX
1 like508 views
The document discusses integrating UX design teams into Scrum processes. It notes that traditionally, development teams are separate from designers, which can lead to issues like diverging visions and late feedback. However, Scrum does not explicitly address this problem. The document suggests co-locating UX designers with Scrum teams and empowering teams to own the user experience as ways to better integrate UX work into Scrum.
Scrum & UX
- 1. Scrum & UX Paul Goddard CSM, CSP, CST Agile Coach © Agilify Ltd. 2008
- 2. Core Problem • Development (Scrum Development Team) are separate from Designers (UX) Scrum Team UX Team © Agilify Ltd. 2008
- 3. Possible Consequences • Us vs. Them culture • Feedback comes too late • Wireframes become contracts • Scrum Product Owner & UX visions diverge • UX teams work too far in advance of Scrum teams • UEDs are matrixed across a number of Scrum teams / functional areas © Agilify Ltd. 2008
- 4. Q: “How does Scrum tell us to solve this problem?” A: “It doesn’t.” © Agilify Ltd. 2008
- 5. Scrum UX Design Development Team Team From “Case Study of Customer Input For a Successful Product” by Lynn Miller © Agilify Ltd. 2008
- 6. What UX fear the most... © Agilify Ltd. 2008
- 7. Winchester Mystery House © Agilify Ltd. 2008
- 8. What I like to see... Scrum Team © Agilify Ltd. 2008
- 9. What I like to see... UED Scrum Team © Agilify Ltd. 2008
- 10. What I also like to see... UED Product Owner Team PO © Agilify Ltd. 2008
- 11. What else helps... • Scrum teams become feature focussed • Use of personas • “Working software over comprehensive documentation” © Agilify Ltd. 2008
- 12. What else helps... • Fast feedback – mocks, prototyping • One vision • Scrum teams who USE the product they build • Empowered teams – own the UX © Agilify Ltd. 2008
- 13. © Agilify Ltd. 2008
- 14. © Agilify Ltd. 2008