UX and Dev - How To Build Killer Features Together v2
•Download as PPTX, PDF•
1 like•123 views
Developers and designers have very different job profiles. We often hear designers complain about developers ruining their work. Developers avoid designers as they make their job more complicated. Instead, we should learn to work together to make our difficult jobs easier and to create the most efficient process for everyone. Nadia is sharing some tips that helped her team of UX professionals to work efficiently with developers in a highly development-driven organisation.
Recommended
More Related Content
Similar to UX and Dev - How To Build Killer Features Together v2
Similar to UX and Dev - How To Build Killer Features Together v2 (20)
Recently uploaded
Recently uploaded (20)
UX and Dev - How To Build Killer Features Together v2
- 1. UX & DEV How to BUILD KILLER FEATURES and not kill each other Nadia Udalova UX Team Lead @XebiaLabs uxnadiaudalovaNadiaUdalova
- 2. Let’s imagine… Scrum Team = Building Team Product Owner = House Owner 1. 2.
- 3. Scoped work
- 5. Impediments!
- 7. Initial goal
- 8. COMMUNICATIVE teams achieve GREATER results
- 9. Nadia Udalova • Joined XebiaLabs in 2014 as UX designer • Leading UX Team since 2017 • Co-founder of Ladies That UX Amsterdam • Certified Design Sprinter (2017) UX Team Lead
- 12. Main challenges Allocation of UX resources UX and Dev work alignment 1. 2.
- 13. Main challenges Allocation of UX resources UX and Dev work alignment 1. 2.
- 14. TWO ways to integrate UX into Agile 1. Allocation of UX resources
- 15. A. INTERNAL AGENCY MODEL 1. Allocation of UX resources
- 16. PO DEVs PO DEVs PO DEVs PO DEVs Lead UX UX UX Feature team 1 Feature team 2 Feature team 4Feature team 3 1. Allocation of UX resourcesA. INTERNAL AGENCY MODEL
- 17. 1. Allocation of UX resourcesA. INTERNAL AGENCY MODEL UX team culture UX focused on future Consistency + + + Features prioritization No strong connection with Dev - -
- 18. B. CROSS FUNCTIONAL MODEL 1. Allocation of UX resources
- 19. Lead PO DEVs UX Feature team 1 Feature team 2 Feature team 4Feature team 3 PO DEVs UX PO DEVs UX PO DEVs UX 1. Allocation of UX resourcesB. CROSS FUNCTIONAL MODEL
- 20. Fast response UX involvement in Dev UX aligned to Dev’s focus + + + No UX team as such Consistency problems Day to day work focus - - - 1. Allocation of UX resourcesB. CROSS FUNCTIONAL MODEL
- 21. PO DEVs PO DEVs PO DEVs PO DEVs Lead UX UX UX Feature team 1 Feature team 2 Feature team 4Feature team 3 Lead PO DEVs UX Feature team 1 Feature team 2 Feature team 4Feature team 3 PO DEVs UX PO DEVs UX PO DEVs UX 1. Allocation of UX resources1. Allocation of UX resources A or B?
- 22. PO DEVs PO DEVs PO DEVs PO DEVs Lead UX UX UX Feature team 1 Feature team 2 Feature team 4Feature team 3 Lead PO DEVs UX Feature team 1 Feature team 2 Feature team 4Feature team 3 PO DEVs UX PO DEVs UX PO DEVs UX 1. Allocation of UX resources1. Allocation of UX resources Depends!
- 23. PO DEVs PO DEVs PO DEVs PO DEVs Lead UX UX UX Feature team 1 Feature team 2 Feature team 4Feature team 3 Lead PO DEVs UX Feature team 1 Feature team 2 Feature team 4Feature team 3 PO DEVs UX PO DEVs UX PO DEVs UX 1. Allocation of UX resources1. Allocation of UX resources Designers < Developers More autonomous Dev teams Focus on future Designers ~ Developers Less autonomous Dev teams Focus on day to day
- 24. HOW did we do it at ? 1. Allocation of UX resources
- 25. “SPOC” designer
- 26. PO DEVs PO DEVs PO DEVs PO DEVs Lead UX UX UX Feature team 1 Feature team 2 Feature team 4Feature team 3 Feature team 5 UX 1. Allocation of UX resources
- 27. Main challenges Allocation of UX resources UX and Dev work alignment2. 1.
- 28. UX is an ICEBREAKER
- 29. Icebreaker CREW
- 30. 2. UX and Dev work alignment UX work Development work v 1 v 2 v 3 Release Release Release
- 31. 2. UX and Dev work alignment Lean UX
- 32. 2. UX and Dev work alignment 1. Move from uncertainty to clarity Lean UX 2. Driving away from long debates to actions 3. Removing waste - early validation 4. Shared understanding!
- 34. 2. UX and Dev work alignment 1. UX is absent in Dev’s day to day work UX Team member attends Dev team’s daily stand-up. NO EXCEPTIONS!
- 35. 2. UX and Dev work alignment 2. Design decisions made without design a. “UX required” column on sprint board b. Scrum master and SPOC designer in sync
- 36. 2. UX and Dev work alignment 3. No learning between UX and Dev UX Team member attends Dev team’s retrospective. NO EXCEPTIONS!
- 37. 2. UX and Dev work alignment 4. End result is different from the design a. Detailed refinement sessions with Dev and UX b. UX as a part of DOD c. UX is a part of QA
- 38. 2. UX and Dev work alignment But, WHAT IF …
- 39. 2. UX and Dev work alignment … we CAN’T convince designers to ATTEND Dev’s rituals?
- 40. 2. UX and Dev work alignment
- 41. 2. UX and Dev work alignment
- 42. 2. UX and Dev work alignment
- 43. 2. UX and Dev work alignment a.Educate to understand each other’s value b.Fixed time and frequency of team rituals c.Only relevant discussions Shared values!
- 44. UX in Dev Sprint cycle Problems addressed on the go Everybody is on same page Product's consistency Collaborative teams Results 2. UX and Dev work alignment
- 45. 2. UX and Dev work alignment Design Systems Graphic EditorsPrototypingHand-off / Inspect Design Files Versioning May tools help!
- 46. Summary Communicate teams achieve greater results TOGETHER Correct allocation of UX resources is a baseline of success 2. 1. UX is an icebreaker 4. Lean UX: more important than ever before 3. UX team in Dev rituals, Dev involved into UX5.
- 47. Thank YOU! Nadia Udalova uxnadiaudalova@NadiaUdalova
Editor's Notes
- Hi DigitalOcean! Great to be speaking here today crowd is technical But good top bring a bit of design perspective Do we have designers? Who works with designers? Who thinks that we can work better together?
- House Owner perfectly know hwat house he wants: 2 floors Wide entrance Flower stands
- NL weather
- Why is this happening? Where do we deviate from the initial plan? Who is to blame? The problem is that the team didn’t make a correct decision to move on during the decision time
- It is possible, however, to set up the environment and rituals that will help teams communicate and make fast decisions to avoid failure and resolve issues. Faster Smarter More inputs
- XebiaLabs is a DevOps platform provider. We help organizations deliver their software faster and with less risk
- Our products are made by developers for developers. IT for IT Developers were thinking that they perfect know what users want. Most of decisions made with little or no user input.
- This is how I felt.. So between then and now we have gone through a long way of adjustment and learning to work together, and today I would like to share my personal experience with you. I am going to be talking today about my experience - from perspective of a designer rather than developer. But I believe it has to be a two-side work, just like in a relationship. Two things that helped me make some progress at the company I currently work at:
- But this is not everything that helped us communicate with Dev team better..
- So.. Here is the point.. It is important to align UX and dev work properly in order to have all as much as needed information before we can start coding. Sometimes UX works in isolation, throwing heir work over the wall.
- Here is what worked for us: Ux starts right before the release is planned to do the needed investigation. We try to involve Dev as much as possible . It important that UX goes first before the actual development will start. Some people call it “waterfall” approach…
- However, it is pretty Agile approach. Have you heard of lean UX? Lean UX unites product development and business, through constant measurement and so called “learning loops” (build – measure – learn). Lean UX uses Agile approach to unify developers and designers in the Agile process of product development.
- Okay. Sounds great. But let’s talk about ICEBERGS left after the icebreaker.. What are the most common challenges when Dev and UX are working together?
- Make sure to time box it Make sure that people are willing to listen – tell a our story