Esri UC 2012 Lightning Talk by Keita (Del Valle) Wangari. Based on knowledge learned in the "Agile UX Toolkit" tutorial taught by John Schrag & Desiree Sy at the 2012 UPA Conference.
Fitting UX into an Agile
Development Environment
Keita Del Valle
Esri International User Conference
July 23–27 | San Diego Convention Center
Based on knowledge learned in the “Agile UX Toolkit” tutorial taught
by John Schrag & Desiree Sy at the 2012 UPA conference. The slides
from that tutorial can be found here.
Design & UX
Development
I0 I1 I2
Research
Designs for I2
Research for I3
Structure
Minimum UI work
Designs from I1
User test I1 Code
Designs for I3
Research for I4
Who’s Doing What When?
Train Everyone on Agile
Design
Marketing
UX
Documentation
Development
Product Mgmt Project Mgmt
Business Analyst
Hinweis der Redaktion
Planning only – no code or developmentMost important when defining a new product instead of refining an existing oneShare product vision (what, for who, why is it better) & release mission (feature agnostic) Creates shared and explicit understanding of business goalsWhat to do and what to cut will be more clear laterHelps to skew the design & development tracksImportance for UX: product vision & release mission dictates user research & helps keep an intact user story when cutting
Done needs to include time to fix bugs that QA found, not just code completionThe whole team has to buy inProduct vision & release mission from Iteration 0 will help hereImportant for UX Team – you need to be aware if you’re testing something that has bugs in it
Ideas need to be tested with usersDon’t assume that skipping testing will save time overallOne track should feed the otherWorking a sprint ahead of the development team allows design team time to test and iterate and allows the development team to use the results
UX teams like to document: research, test results, personas, scenariosAgile: no will read, document only what it needed to get message acrossCross disciplinary collaborationRich:face-to-face, high quality videoconference systemPoor: email, instant messagingIn the middle: phone calls, so-so video conference
This is where the UX research, based on the product vision and release mission, adds the most valueKnowledge of user workflow in the field is critical hereCapabilities span stories … need to cluster them and determine minimum viable version of capabilityToo often iterating previous iteration’s problems gets abandoned in favor of newer exciting features
Don’t design details of final product all at once – things will change through iterationBreak down enough so a complete story or sub-story is delivered each iteration
Formative is where you’re testing prototypes with the goal of improving the design, use a fast, cheap prototypeSummative testing isn’t Agile enough … need feature or product to be complete, looking for all usability problemsNot enough time to recruit test subjects … continuously recruit & scheduleUpdate prototypes between tests if it fails the design goal – leave enough time between test sessions