How to Combine Design Methods with Agile & Remain Sane
•Télécharger en tant que PPTX, PDF•
2 j'aime•608 vues
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.
Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à How to Combine Design Methods with Agile & Remain Sane
Similaire à How to Combine Design Methods with Agile & Remain Sane (20)
Dernier
Dernier (20)
How to Combine Design Methods with Agile & Remain Sane
- 1. How to Combine Design Methods with Agile & Remain Sane Den Tserkovnyi @dtserkovnyi
- 3. 16 million users per year 2000+ universities 139000+ programmes
- 5. and now
- 7. Put your hands in the air
- 8. If you ever been frustrated with…
- 10. not being involved in the process?
- 11. lack of long term planning?
- 12. It’s OK. We can solve it*
- 13. Design is not just about function and aesthetics
- 14. It is also how you “get there”
- 15. Scrum UX process
- 16. March 2014
- 18. Now
- 20. me
- 21. + More creative solutions + Easier cooperation + Speed of development − Long term planning − Style consistency
- 23. Device testing
- 25. Scrum UX process
- 31. have fixed times (if it’s regular)
- 32. be timeboxed
- 33. be structured and have an agenda
- 34. focused on goals
- 40. + Kicked off UXD activities + Good brainstorms and team building − Doesn’t happen often enough − Requires preparation
- 41. Working together
- 42. + Working together in the same room − Workspace differences are annoying − Easy to completely hijack the meeting
- 43. Workshops
- 45. + Good in-company feedback − Do more of them
- 46. Design Sprint
- 56. 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/
- 57. + 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
- 61. + Structure + Quick feedback − Time consuming − Not often enough
- 62. Design critique
- 63. What feedback are you interested in?
- 64. What is the problem we are solving?
- 65. + Nice and useful input + Sharing feedback with the group + Good structure − Hard to contain feedback type at times
- 66. Sketch session
- 69. + Useful input + Good structure − Needs time for conclusions
- 70. Conclusion
- 72. Start small & deliver value
- 74. Next steps
- 75. It is also how you get there
- 79. Design spikes
- 80. Remote testing
Notes de l'éditeur
- 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