Successfully reported this slideshow.

How to Combine Design Methods with Agile & Remain Sane

2

Share

Loading in …3
×
1 of 81
1 of 81

How to Combine Design Methods with Agile & Remain Sane

2

Share

Download to read offline

How in 3 months we at StudyPortals combined 9 different design methods with agile development and still remain sane.
Presentation from UX Camp NL, some slides are blurred.

How in 3 months we at StudyPortals combined 9 different design methods with agile development and still remain sane.
Presentation from UX Camp NL, some slides are blurred.

More Related Content

Related Books

Free with a 14 day trial from Scribd

See all

Related Audiobooks

Free with a 14 day trial from Scribd

See all

How to Combine Design Methods with Agile & Remain Sane

  1. 1. How to Combine Design Methods with Agile & Remain Sane Den Tserkovnyi @dtserkovnyi
  2. 2. 16 million users per year 2000+ universities 139000+ programmes
  3. 3. and now
  4. 4. Please prepare
  5. 5. Put your hands in the air
  6. 6. If you ever been frustrated with…
  7. 7. vague requirements?
  8. 8. not being involved in the process?
  9. 9. lack of long term planning?
  10. 10. It’s OK. We can solve it*
  11. 11. Design is not just about function and aesthetics
  12. 12. It is also how you “get there”
  13. 13. Scrum UX process
  14. 14. March 2014
  15. 15. Now
  16. 16. me
  17. 17. + More creative solutions + Easier cooperation + Speed of development − Long term planning − Style consistency
  18. 18. Device testing
  19. 19. Scrum UX process
  20. 20. Usability testing
  21. 21. Some obvious rules
  22. 22. All meetings should…
  23. 23. have fixed times (if it’s regular)
  24. 24. be timeboxed
  25. 25. be structured and have an agenda
  26. 26. focused on goals
  27. 27. be reflected upon
  28. 28. Design strategy event
  29. 29. + Kicked off UXD activities + Good brainstorms and team building − Doesn’t happen often enough − Requires preparation
  30. 30. Working together
  31. 31. + Working together in the same room − Workspace differences are annoying − Easy to completely hijack the meeting
  32. 32. Workshops
  33. 33. + Good in-company feedback − Do more of them
  34. 34. Design Sprint
  35. 35. From http://www.thesprintbook.com/tools/
  36. 36. FM T W T If you do 3 sprints in a row… FTWT FT …they won’t all take 5 days. From http://www.thesprintbook.com/tools/
  37. 37. + UX promotion within the company + Cross department alignment + Good brainstorms and team building + Quick decisions − Too much external work outside of the sprint − Needs preparation and commitment
  38. 38. Heuristic evaluation
  39. 39. + Structure + Quick feedback − Time consuming − Not often enough
  40. 40. Design critique
  41. 41. What feedback are you interested in?
  42. 42. What is the problem we are solving?
  43. 43. + Nice and useful input + Sharing feedback with the group + Good structure − Hard to contain feedback type at times
  44. 44. Sketch session
  45. 45. From http://www.thesprintbook.com/tools/
  46. 46. + Useful input + Good structure − Needs time for conclusions
  47. 47. Conclusion
  48. 48. Never stop experimenting
  49. 49. Start small & deliver value
  50. 50. Measure everything
  51. 51. Next steps
  52. 52. It is also how you get there
  53. 53. “Design hub” days
  54. 54. Hybrid design team
  55. 55. Living style guide
  56. 56. Design spikes
  57. 57. Remote testing
  58. 58. Ask me anything @dtserkovnyi or LinkedIn

Editor's Notes

  • How we run design and development processes rapidly scaling up
    Search for the ideal workflow
  • My name is Den, and barely anyone can pronounce my surname. Born in Ukraine, moved to the Netherlands 4 years ago.
    I had a pleasure to work in a dynamic environments with a great teams as UX researcher, UX designer, Scrum Master, Product Owner.

    The most exciting challenge I’m working on right now is building the best UX team in the Netherlands. It’s impossible to build best team without the great processes.
    Therefore we are always experiment with the new approaches.
  • First a bit about the company I work at. It’s called StudyPortals and it is aiming to make higher education transparent worldwide.
    As you may noticed from your past, the process of the selection of the higher education is one of the hard ones.
    That’s where we come in and help students to find an education of their dream.
  • In Eindhoven HQ we are having 28 nationalities out of 95 employees.
    For all the vacancies that we have an experience of getting education abroad is very valuable.
  • * it’s a long way that require commitment and experimentation
  • In this presentation I will mention different parts of our process with feedback given by designers
  • 2.5 years ago: 4 full time developers.
    Gantt chart planning
  • Scrum?
    No one knows the future
  • Separate design team VS designers in dev teams
    No multidisciplinary teams. Less creative solutions
    Less UX promo in Dev. Harder to pull things through
    Better consistency
  • Spotify model
    How do we scale? Different styles of design
  • Pros/Cons of agile development for UX. Separate design team VS designers in dev teams

    No multidisciplinary teams. Less creative solutions
    Less UX promo in Dev. Harder to pull things through
    Better long term and consistency
  • Sprint planning
    Daily standup
    Scrum of Scrums
    Testing
    Demo
    Retro
  • Company demo & development transparency
    + video for all who work in the other offices

    Scrum in the sales and client success departments.
  • UX sprint update: alignment on quarter targets. May be focus more on personal development

    Daily standups:
    Fast, saves time on double work
    Nice alignment
    Give more context of the issue

    Open meeting for coop: critique, heuristic evaluation, sketch session.
    Usability testing of what was developed and presentation
  • Prototyping and checking the vision before development

    Watching usertests online
  • Which are rarely applied
  • Obvious topics ahead
  • Not enough time to procrastinate
  • Explain the topic ahead of the session
  • retrospective
  • Hallway wall to make discussions more transparent
    Blurred slide
  • Prepared in advance whole day of activities about: workflow, tools, personal growth, pain points, place of UX in the company (NN, promo, stakeholder involvement)
  • We need to restructure it
  • Blurred slide
  • Collection of design methods
  • Talk to one person at a time and take notes.

    Blurred slide
  • Positive feedback
  • Art museum makes sense without creating heatmaps in the same time, because you are influencing each other too much and it’s easy not to pay attention to the details.
    A lot of decisions before the lunch

    Blurred slide
  • Blurred slide
  • Simple to use software

    Blurred slide
  • Edit the porotype and interview

    Blurred slide
  • Our real clients. 3 online, 2 in the office.
    Team watched in the separate room
    Semi-structured interview
  • Outcomes
    It was a great and a busy week running our first design sprint! In just five days we decided on the direction, sketched, prototyped and tested a new product vision with five users.


    Blurred slide
  • Different projects are possible within (Branding)
    UX promotion within the company
    Observe + time for UX design.
    Not all the steps were extremely obvious and I had an uneasy feeling in terms of procedure. I expected some pitfalls and issues with the process. Mainly from my side, like forgetting important steps, doing things wrong. I was mistaken
    Feedback: very intense putting all effort, people don’t understand amount of effort designers put in, interview observation. No disruptions

  • NN + some other heuristics
    Did it with the prototype from the Design Sprint
    Nice meeting. Need to do it more before starting an isolated project.
    Focus on concerns, not solutions. Avoid long discussions.
  • Ask a lot of questions
    Understand the context
    Take notes


  • Ask a lot of questions
    Understand the context
    Take notes


  • Good topic: style guide and consistency
    More time for reflection was needed and more clear way to follow it up
    Text matters
  • Intro design sprint every Q for setting the strategy
  • to support us in consistency
  • A design spike is a bubble of time during which the designers and potentially other team members focus primarily on design questions. Design spikes can take place at the start of a project or anytime during the normal scrum process, but the introduction of a design spike changes the nature of the working scrum team temporarily. 
  • We are hiring
  • ×