User Feedback at the Speed of DevOps
summary
Visual Studio Team Services moves to a three-week cadence and pairs PMs, designers and one researcher to run FAST (one-week studies): plan Monday, build prototypes Tuesday–Wednesday, test five users Thursday, debrief and email results Friday. Teams run 5–6 users per week in lab or use usertesting.com/userzoom, log findings on the VSTS Kanban, and ship iterative fixes the next sprint. Heuristic checks and launch‑and‑learn emails to ~100‑person agile teams track metrics; a conversion funnel example shows non‑linear but measurable improvement over several iterations.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 0:59Visual Studio Team Services
- 1:37Release cadence
- 2:50Planning cycles
- 3:57Execution cycles
- 5:24Customer feedback
- 5:46Customer driven
- 10:49Tools
- 14:00Process
- 19:01Personas
- 22:36Build Measure Learn
related talks
59mVisual Studio Online: The Inside Story from COTS to Cloud
44m#Devops Journey
36mMixing Lean UX & Agile Development
06mGetting VSTS to "Production"
37mFrom Waterfall to Agile
24mPanel Talk: Integrating UX for Improved Product Development
01h 01mAgile Evolution: An Enterprise transformation that shows that you can too
01h 04mDiscount Usability Testing for Agile Teams