How to Build UX Into Your Dev Process
summary
Claims that UX must start at project inception and continue through release backed by concrete practices: UX starts at project inception, UX one to two sprints ahead. Requirements include behavior‑focused UX requirements and annotated wireframes, not wish lists; user stories need UX authorship or review. Front‑end specialists bridge design and backend. User observation and quick usability tests with a developer observing reveal real failures fast and drive fixes before rollout. wireframes annotated with behavior, developers must observe user tests.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 2:19UX challenges myth
- 9:44When UX starts
- 14:07User needs learning
- 17:42UX vs functional requirements
- 20:48UX in user stories
- 22:38UX in Agile processes
- 29:48Ideal UX workflow
- 32:39UX roles in teams
- 36:37When UX is done
- 39:31UX and dev as one
- 41:42Q&A
related talks
33mUX Testing: Let's Build Products Better Than Before!
09m"QA & UX"
37mThe UI is THE APPLICATION
01h 02mA developers guide to the UX galaxy
24mUX Testing: Planning, Preparation, Execution and Analysis
46mFundamentals of UX Design and Usability
43mUX in the mobile applications development
58mLet's Work Together!