Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

UX Camp 2017 – How UX survives in agile development

520 views

Published on

So I want to share some of my experiences - both good and bad - of how to deal with agile development as a UX Designer. What I have learned in the strive to be an agile UX designer myself.

Published in: Design
  • Be the first to comment

  • Be the first to like this

UX Camp 2017 – How UX survives in agile development

  1. 1. Janne Bjørsted Lead UX Designer How UX survives in Agile Development
  2. 2. Lead UX Designer
  3. 3. 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
  4. 4. Agile
  5. 5. We value responding to change over following a plan. Jeff Gothelf Superheroes & Villains in Design - https://vimeo.com/70030549
  6. 6. Build Measure Learn
  7. 7. Users Relations Design
  8. 8. Users Have you ever been part of a project where you lost track of the users (experiences and needs) when you dived into implementation?
  9. 9. Project A
  10. 10. Project A UX designer Product
  11. 11. Project A UX designer Product Users
  12. 12. Project A UX designer Client Product Users
  13. 13. Project A UX designer Client Client’s client Product Users
  14. 14. Project A UX designer Client Client’s client Product Users
  15. 15. User experience is your business plan. Aral Balkan Superheroes & Villains in Design - https://vimeo.com/70030549
  16. 16. Project A UX designer Client Client’s client Product Users
  17. 17. Prototype Structure Full experience / HTMLSketch
  18. 18. User test prototype
  19. 19. User test prototype – observation with client and team
  20. 20. Project A UX designer Client Product Users Team
  21. 21. Pitfalls Many stakeholders Only sharing WHAT not WHY with team Letting framework determine UX Being a UX ‘know it all’
  22. 22. 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’
  23. 23. 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?
  24. 24. UX Designer – role in scrum ?
  25. 25. 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
  26. 26. 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
  27. 27. Project B
  28. 28. Scrum Master Stakeholder UX Designer / Product Owner Team Stakeholder Stakeholder Project B Client
  29. 29. Human Project B HumanHuman
  30. 30. Structure for input
  31. 31. Client input
  32. 32. Accept chaos a bit of
  33. 33. … for a little while
  34. 34. Product Owner Project B Scrum Master Client Product Owner
  35. 35. Team input
  36. 36. Backlog – prioritize
  37. 37. Backlog – prioritize with your client and team Product Owner Scrum Master Client Product Owner
  38. 38. Accept chaos a bit of
  39. 39. … for a little while
  40. 40. Client and team input
  41. 41. Formal + Informal meetings
  42. 42. 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/
  43. 43. 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/
  44. 44. Pitfalls A lot of individual stakeholders TOO many detail specifications TOO structured Being a UX ‘know it all’
  45. 45. 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’
  46. 46. Design Have you ever been blindsided of either “new” design gimmicks or your developer simply saying ‘No, can’t do’?
  47. 47. Project C
  48. 48. Frontend Project C Team Product Owner Client Stakeholder Stakeholder Design Scrum Master
  49. 49. We forgot that ...
  50. 50. Design Development LeadsInforms
  51. 51. UX … in sprints
  52. 52. UX … in progress
  53. 53. UX Design FramesRealize
  54. 54. Guide the client
  55. 55. Guide the client as a team
  56. 56. Guide the client as a team in a human way
  57. 57. Design in sprints
  58. 58. Change your mind
  59. 59. Design Measure Learn
  60. 60. 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
  61. 61. 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
  62. 62. Being an agile UX designer
  63. 63. Only sharing WHAT not WHY with team TOO structured Forgetting you are an expert Being an UX ‘know it all’ Pitfalls
  64. 64. 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
  65. 65. 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
  66. 66. Thanks.
  67. 67. ?

×