Agile UX - How to Combine Agility with Usability
summary
Explains how agile development can still produce poor UX and gives concrete practices to prevent that: use quick sketches and wireframes/prototypes early, include designers, domain experts and real users continuously, and perform regular frontend refactoring. Recommends treating UI requirements as nonfunctional stories, using Fibonacci sizing for estimation, preferring late localization, and choosing frontend frameworks deliberately; includes a cost-saving anecdote about moving a fax machine to save $2 million rather than rebuilding a system.
AI-written summary · about
chapters (25)
- 0:00Agile UX introduction
- 3:02App language and users
- 5:12User memory and support
- 7:10Error messages and usability
- 8:45User expectations for ops
- 9:50Web app navigation pitfalls
- 11:28Shortcuts and UI personalization
- 13:15UI simplicity and consistency
- 16:27Team collaboration in UX
- 19:36Product Owner's UX role
- 22:50Domain experts in UX
- 24:55User feedback processing
- 29:06Agile requirements and usability
- 31:17User pain threshold
- 35:27Project pricing challenges
- 37:54Frontend feature comparison
- 38:56Frontend tech and usability
- 41:46Business app design process
- 43:34Sketches and prototypes
- 45:37Graphic details in UX
- 46:41Cumulative inconvenience effect
- 49:10Pre-iteration feedback
- 50:35Mid-project refactoring
- 51:39Final navigation refinement
- 52:43App localization timing
related talks
01h 01mAgile UX for Developers (or, Why Fluff is Stuff Too)
49mUX and an Agile Development Process
41mIntegrating User Experience and Agile
24mOvercoming Resistance: UX Practices in Agile Teams
37mHow They Work Better Together: Lean UX, Agile Development and User-Centered Design
33mIs Lean UX Agile’s Brain? How Lean UX Fixes Common Agile
36m"UX for Developers, Seriously!"
49mCo-creating with UX and Software