![Marcin Treder
The ultimate goal of Agile UX is to
unify developers and designers [and clients] in
the Agile process of product development
UXPIN – https://www.uxpin.com/studio/blog/lean-ux-vs-agile-ux-is-there-a-difference/](https://image.slidesharecdn.com/uxcamp2017agileux-170916092009/85/UX-Camp-2017-How-UX-survives-in-agile-development-47-320.jpg)
UX Camp 2017 – How UX survives in agile development
- 1. Janne Bjørsted Lead UX Designer How UX survives in Agile Development
- 5. Established 1998 2000+ digital turn key solutions E-commerce, Member solutions, Apps, In-store concepts, Chat bots and more Strategy, Concept, Design, UX, Integration, Usability lab, Testing and Conversion Barcelona, Berlin, Boston, Copenhagen, Kaunas, Vilnius
- 6. Agile
- 7. We value responding to change over following a plan. Jeff Gothelf Superheroes & Villains in Design - https://vimeo.com/70030549
- 10. Users Have you ever been part of a project where you lost track of the users (experiences and needs) when you dived into implementation?
- 11. Project A
- 15. Project A UX designer Client Client’s client Product Users
- 16. Project A UX designer Client Client’s client Product Users
- 17. User experience is your business plan. Aral Balkan Superheroes & Villains in Design - https://vimeo.com/70030549
- 18. Project A UX designer Client Client’s client Product Users
- 19. Prototype Structure Full experience / HTMLSketch
- 21. User test prototype – observation with client and team
- 23. Pitfalls Many stakeholders Only sharing WHAT not WHY with team Letting framework determine UX Being a UX ‘know it all’
- 24. Share your work in early stages Involve your team in UX analysis Say your opinion … again See user test … together Pitfalls TO DO’s Many stakeholders Only sharing WHAT not WHY with team Letting framework determine UX Being a UX ‘know it all’
- 25. Relations Have you ever thought that your client (or your team) was building the wrong experience, but you didn’t speak up or know how to convince them otherwise?
- 26. UX Designer – role in scrum ?
- 27. Agile process and scrum method Scrum team Product owner Product backlog Sprint backlog Sprint (2-4 weeks) As a <type of user>, I want <some goal> so that <reason>. Implementing IntegrationTest Installation
- 28. Agile process and scrum method Scrum team UX Designer Product backlog Sprint backlog Sprint (2-4 weeks) As a <type of user>, I want <some goal> so that <reason>. Implementing IntegrationTest Installation
- 29. Project B
- 30. Scrum Master Stakeholder UX Designer / Product Owner Team Stakeholder Stakeholder Project B Client
- 33. Client input
- 35. Accept chaos a bit of
- 36. … for a little while
- 38. Team input
- 41. Backlog – prioritize with your client and team Product Owner Scrum Master Client Product Owner
- 42. Accept chaos a bit of
- 43. … for a little while
- 44. Client and team input
- 46. Marcin Treder The ultimate goal of Agile UX is to unify developers and designers in the Agile process of product development UXPIN – https://www.uxpin.com/studio/blog/lean-ux-vs-agile-ux-is-there-a-difference/
- 47. Marcin Treder The ultimate goal of Agile UX is to unify developers and designers [and clients] in the Agile process of product development UXPIN – https://www.uxpin.com/studio/blog/lean-ux-vs-agile-ux-is-there-a-difference/
- 48. Pitfalls A lot of individual stakeholders TOO many detail specifications TOO structured Being a UX ‘know it all’
- 49. One touch point with client Keep updating team of client needs Storytime and workshops Ask the team to find best UX Pitfalls TO DO’s A lot of individual stakeholders TOO many detail specifications TOO structured Being a UX ‘know it all’
- 50. Design Have you ever been blindsided of either “new” design gimmicks or your developer simply saying ‘No, can’t do’?
- 51. Project C
- 53. We forgot that ...
- 55. UX … in sprints
- 56. UX … in progress
- 58. Guide the client
- 59. Guide the client as a team
- 60. Guide the client as a team in a human way
- 62. Change your mind
- 64. Full design upfront Saying yes without a why Not framing your project Forgetting you are an UX expert Being an UX ‘know it all’ Pitfalls
- 65. Full design upfront Saying yes without a why Not framing your project Forgetting you are an expert Being an UX ‘know it all’ Only design enough to start dev Say no to client and team Share all your (mis)steps Guide in a human way Patiently share why UX matter Pitfalls TO DO’s
- 66. Being an agile UX designer
- 67. Only sharing WHAT not WHY with team TOO structured Forgetting you are an expert Being an UX ‘know it all’ Pitfalls
- 68. Only sharing WHAT not WHY with team TOO structured Forgetting you are an expert Being an UX ‘know it all’ Explain your analysis Accept chaos – and structure for input Guide in a human way Be an UX ambassador Pitfalls TO DO’s
- 69. Only sharing WHAT not WHY with team TOO structured Forgetting you are an expert Being an UX ‘know it all’ Explain your analysis Accept chaos – and structure for input Guide in a human way Be an UX ambassador Test – a lot Ask WHY – a lot Change your mind – a lot Pitfalls TO DO’s
- 70. Thanks.
- 71. ?