Embed Size (px)
Citation preview
GREAT UX IN AN AGILE WORLD
Anthony VivianoMobile Interaction [email protected]@anthviv Copyright 2016 Bloomberg LP. All rights reserved.
5 YEARS AGO …
ENTERPRISE ADVOCATE FOR LEAN UX
Educating: UX Team, Other interested parties, Executives
Teaching: Hosted training classes, lunch and learns
Selling: One-week experiment
3
ONE WEEK EXPERIMENT
Picked a thorny problem
Gathered a crack team
Locked ourselves in “war room” for a week
Hypothesized a solution, created low fi prototype and tested
4
5
NOW WHAT?
LEFT ME WONDERING
Learnings were valuable - wrong team
My day job suffered – never really given the mandate to do this fulltime
Co-location? Not really
6
7
Source: http://www.slideshare.net/TomIllmensee/build-a-recipe-for-better-ux-process-with-fresh-lean-ingredients
OPPORTUNITIES
Validation: Difficult to get user validation
Design decisions: Wireframes are heavy deliverables and not the end product
Planning: Shifting priorities within milestones
Feedback: Not always timely
Feature driven: Not stepping back and working toward user goals and problems
9
SO WE TRIED
Small batch production – both design and dev
Early and frequent validation – internal and external
Collaborative design – design studio (tweaks) and more time between dev and design
Focus on solving user problems – manifested in user stories
The build is the deliverable – weekly build reviews
Minimum viable design – just enough design to start building
10
ENTER AGILE
agile Agile
12WHAT ABOUT UX?
• Scrum is all about Product Owners, Developers and a Scrum Master. What about design?
• We were told that from the perspective of Scrum, we were Developers
• We learned that Product Owners prioritized, created and maintained the roadmap and interfaced with users
13AND FURTHER
How does design and development work within a single sprint (often only two weeks)?
What about … » UX Strategy
» Consistency
» User research?
14WHAT WE LOVE ABOUT AGILE
Stories are focused on personas
Software is built prioritizing what the user values
Spikes can be used to do design explorations and validation
Collaboration with developers is efficient and could mean lighter deliverables
15WE RESEARCHED
Internal Agile teams
External Agile teams
Best practices in industry (papers and presentations)» NN/g Paper: Agile Development that Incorporates User Experience
Practices
» White Paper: Scaling Agile @ Spotify
» UIE: Josh Seiden’s Presentation for Lean UX in the Enterprise
» Jeff Kelley’s Presentation: Adapting Agile Techniques to User Experience in a non-Agile World
16VALUED PRINCIPLES
Collaborate cross team, cross discipline and cross time zones
Working Software is our deliverable
Seek out early customer (end user) validation of user stories and continue to iterate
The team as a whole and each team member should have a willingness to change
17FLAVORS OF SCRUM
Religious
Agilefall (a.k.a. The Design Sprint)
UXaaS – Individual
UXaaS - Team
18CHALLENGE: THE UX PROCESS TAKES TIME
Iteration cycle
Review cycle
Unknowns discovered
Typical UX work
19CO-LOCATED TEAMS?
UXDEV
WHAT ARE WE DOING?
RECOMMENDED CHANGES TO SCRUM TRAININGCustomer – not just the stakeholder but think of the end user
Developers – better describe who is included» UX Team Members
» Software Developers
» QA Testers
Definition of Done – include UX examples
Testing – include user testing
22RECOMMENDED BEST PRACTICES TO UX
Discovery and delivery
Staggered sprints
Special considerations for UXaaS
How to employ Community of Practice methodology to maintain consistency
23TWO TRACK DEVELOPMENT
Discovery
Delivery
24DISCOVERY TRACK
25DELIVERY TRACK
26
27SOMETIMES YOU TAKE A SHORTCUT
28UX AS A SERVICE: KANBAN
29MAINTAINING UX CONSISTENCY
Community of Practice
30RISKS OF STAGGERED SPRINT
Slight waterfall, risk of change
Unplanned work
Mitigating the risk» If minor – do it
» If major – make a decision (prioritize with PM)
• Defer to a future sprint? • Disrupt the current sprint and work on it
31CAN WE DO IT ALL IN ONE SPRINT?
Tightening the gap reduces risk since things can change
Reduces need for documentation even further
Allows UX to contribute in new ways (QA?)
32SINGLE SPRINT – PAIR UX/DEV
UX sits with Dev and gives live direction
UX supports several developers in this method
33SINGLE SPRINT: BREAK DOWN STORIES
Task is small (an afternoon)
Dev can begin quickly
UX moves on to next small task
UX contributes to QA at the end of the sprint (or dev)
34BENEFITS
Better working relationship between dev, product and design since we’re all on the same team
Everyone speaks the same language since we’re tightly integrated
Shared knowledge and shared ownership
Focus on end user increases product value, building the right stuff
