Lessons learned integrating ux into agile teams.2012.08.with notes
Agile UX In Real Life - Lessons Learned
-
Upload
philipp-schroeder -
Category
Design
-
view
6.024 -
download
3
description
Transcript of Agile UX In Real Life - Lessons Learned
![Page 1: Agile UX In Real Life - Lessons Learned](https://reader034.fdocuments.in/reader034/viewer/2022052521/53f14c558d7f72e94b8b476f/html5/thumbnails/1.jpg)
(P)
LESSONS LEARNED(P)HILIPP SCHRÖDER
AGILE UX IN REAL LIFE15.5.2013
![Page 2: Agile UX In Real Life - Lessons Learned](https://reader034.fdocuments.in/reader034/viewer/2022052521/53f14c558d7f72e94b8b476f/html5/thumbnails/2.jpg)
➡ Individuals and interactions over processes and tools
➡ Working software over comprehensive documentation
➡ Customer collaboration over contract negotiation
➡ Responding to change over following a plan
AGILE MANIFESTO
HTTP://AGILEMANIFESTO.ORG/
![Page 3: Agile UX In Real Life - Lessons Learned](https://reader034.fdocuments.in/reader034/viewer/2022052521/53f14c558d7f72e94b8b476f/html5/thumbnails/3.jpg)
1 ITERATION = 1 SPRINT = 1 TO 3 WEEKS
ITERATIVE DEVELOPMENT(SCRUM PROCESS)
24hrs
Sprint planning End of project
Sprint reviewSprint retrospective
Product Backlog Development
Goal achieved / money run down
![Page 4: Agile UX In Real Life - Lessons Learned](https://reader034.fdocuments.in/reader034/viewer/2022052521/53f14c558d7f72e94b8b476f/html5/thumbnails/4.jpg)
WATERFALL VERSUS AGILEWaterfall Development Model
Agile Development Model
Analysis
Design
Programming
TestingTime
Handover Handover Handover
i1
A
P
D
TTime
i2
A
P
D
T
i3
A
P
D
T
i4
A
P
D
T
i5
A
P
D
T
Inspect Inspect Inspect Inspect
AdaptAdapt
Inspect
Adapt Adapt
![Page 5: Agile UX In Real Life - Lessons Learned](https://reader034.fdocuments.in/reader034/viewer/2022052521/53f14c558d7f72e94b8b476f/html5/thumbnails/5.jpg)
A way to improve efficiency & effectiveness➡ Keeping focus on (customer) value➡ Removing non valuable activities
(e.g. excessive documentation)➡ Optimizing the workflow & information flow
to achieve the shared goal (cf. Kanban)➡ Attention to symptoms of overburden
(work with a sustainable pace)
LEAN THINKING
![Page 6: Agile UX In Real Life - Lessons Learned](https://reader034.fdocuments.in/reader034/viewer/2022052521/53f14c558d7f72e94b8b476f/html5/thumbnails/6.jpg)
Visual Design
Site ObjectivesUser Needs
Content Requirements
Functional Specifications
Interaction Design
Information Architecture
Information DesignNavigation DesignInterface Design
Concrete Completion
ConceptionAbstract
time
Surface
Skeleton
Structure
Scope
Strategy
Concrete Completion
ConceptionAbstract
time
HTTP://WWW.JJG.NET/ELEMENTS/
THE ELEMENTS OF USER EXPERIENCE
Surface: Design the visual presentation of user interface
Skeleton: Design the arrangement and contents of individual screens; navigation
Structure: Define the 'information architecture' of the user interface
Scope: Narrow down the requirements for features and content
Strategy: Gather business goals and user needs
![Page 7: Agile UX In Real Life - Lessons Learned](https://reader034.fdocuments.in/reader034/viewer/2022052521/53f14c558d7f72e94b8b476f/html5/thumbnails/7.jpg)
Visual Design
Site ObjectivesUser Needs
Content Requirements
Functional Specifications
Interaction Design
Information Architecture
Information DesignNavigation DesignInterface Design
Concrete Completion
ConceptionAbstract
time
HTTP://WWW.JJG.NET/ELEMENTS/
THE ELEMENTS OF USER EXPERIENCE
User Needs & Business Goals
Observe
Both!
![Page 8: Agile UX In Real Life - Lessons Learned](https://reader034.fdocuments.in/reader034/viewer/2022052521/53f14c558d7f72e94b8b476f/html5/thumbnails/8.jpg)
My personal favorites...BENEFITS OF AGILE
![Page 9: Agile UX In Real Life - Lessons Learned](https://reader034.fdocuments.in/reader034/viewer/2022052521/53f14c558d7f72e94b8b476f/html5/thumbnails/9.jpg)
Agile can shorten the time from idea to delivery➡ Fast delivery (an increment of working
software each iteration)➡ Focus (focus on business value, important
features first, less waste)➡ Informed decisions (decide in the latest
responsible moment)
TIME TO MARKET
![Page 10: Agile UX In Real Life - Lessons Learned](https://reader034.fdocuments.in/reader034/viewer/2022052521/53f14c558d7f72e94b8b476f/html5/thumbnails/10.jpg)
IMAGE: CC BY SA CHARLIE LLEWELLIN ON FLICKR
SUSTAINABLE PACE
The iterative process facilitates working at a regular pace.
The pace of last iterations can guide the target for the next iteration.
The agile principles enable flow, a state of focussed concentration.
![Page 11: Agile UX In Real Life - Lessons Learned](https://reader034.fdocuments.in/reader034/viewer/2022052521/53f14c558d7f72e94b8b476f/html5/thumbnails/11.jpg)
SCRUM PROCESSJANICE FRASER'S UX CYCLES
UX CYCLES
AGILE DEVELOPMENT
COMMON GROUND: WORKING ITERATIVELY
THINK Generative Research,
Ideation,Test Results,
Competitive Analysis MAKESketches,Wireframes,Mockups,Prototypes,Deployed Code
EVALUATEFeedback,Site Analytics,Usability Testing
Planning End
ReviewRetrospective
Backlog Development
![Page 12: Agile UX In Real Life - Lessons Learned](https://reader034.fdocuments.in/reader034/viewer/2022052521/53f14c558d7f72e94b8b476f/html5/thumbnails/12.jpg)
Sometimes referred to as “iteration zero”
WHAT NEEDS TO BE IN PLACE AT THE START OF ITERATION ONE?
![Page 13: Agile UX In Real Life - Lessons Learned](https://reader034.fdocuments.in/reader034/viewer/2022052521/53f14c558d7f72e94b8b476f/html5/thumbnails/13.jpg)
An UX practitioner’s answer:➡ The (design) strategy➡ Business requirements➡ User research➡ Personas, scenarios➡ ... yaddi yaddi yadda ...➡ And a design framework
Big
Design
Up Front
WHAT NEEDS TO BE IN PLACE AT THE START OF DEVELOPMENT?
![Page 14: Agile UX In Real Life - Lessons Learned](https://reader034.fdocuments.in/reader034/viewer/2022052521/53f14c558d7f72e94b8b476f/html5/thumbnails/14.jpg)
An agile practitioner’s answer:➡ A product vision➡ A prioritized product backlog➡ A product owner➡ A development team
WHAT NEEDS TO BE IN PLACE AT THE START OF ITERATION ONE?
Inspect &
Adapt
![Page 15: Agile UX In Real Life - Lessons Learned](https://reader034.fdocuments.in/reader034/viewer/2022052521/53f14c558d7f72e94b8b476f/html5/thumbnails/15.jpg)
AGILE PROJECT CHARTER
DON’T OBSESS ABOUT THE BIG PICTURE, GET A COMPASS.
Business goal 1
Business goals
Success criteria
Users / customer value
Team / roles
Working agreements
Project context
...
➡ How do we know we are successful?
➡ Who are our users? What is the value for them?
➡ Clarify expectations about the roles in the team.
➡ Jointly define operational guidelines (Definition of Done, ...)
➡ Clarify interfaces to parties involved in the project
➡ Adjust / add as needed
Project title
Business goal 2 Business goal 3
How
Why
Use agile chartering to map out the territory
![Page 16: Agile UX In Real Life - Lessons Learned](https://reader034.fdocuments.in/reader034/viewer/2022052521/53f14c558d7f72e94b8b476f/html5/thumbnails/16.jpg)
How to best integrate user research in agile development?
USER RESEARCH AND THE AGILE FEEDBACK LOOP
![Page 17: Agile UX In Real Life - Lessons Learned](https://reader034.fdocuments.in/reader034/viewer/2022052521/53f14c558d7f72e94b8b476f/html5/thumbnails/17.jpg)
LOTS OF OPPORTUNITIES FOR RESEARCH & CO-DESIGN
Product Owner
Developers
UX Researcher
Customer Service Rep
Users
MON TUE WED THU FRI MON TUE WED THU FRI
●
●
●
●
●
●
●
●
●
●
●
●
●
●
○ ○ ○ ○ ○ ○ ○ ○
![Page 18: Agile UX In Real Life - Lessons Learned](https://reader034.fdocuments.in/reader034/viewer/2022052521/53f14c558d7f72e94b8b476f/html5/thumbnails/18.jpg)
SHOULD A UX DESIGNER ACT AS PRODUCT OWNER IN AGILE (“UXPO”)?
![Page 19: Agile UX In Real Life - Lessons Learned](https://reader034.fdocuments.in/reader034/viewer/2022052521/53f14c558d7f72e94b8b476f/html5/thumbnails/19.jpg)
THE AGILE PRODUCT OWNER
Domain expertise
Business User-centered Design
Technology
![Page 20: Agile UX In Real Life - Lessons Learned](https://reader034.fdocuments.in/reader034/viewer/2022052521/53f14c558d7f72e94b8b476f/html5/thumbnails/20.jpg)
PO TEAM- Focus on the “what” / problem space
- Who is our customer and what is a problem that is worth solving?
- Leverages user research methods (cf. Lean startup: customer development)
THE PO TEAM / DEV TEAM COMBO
DEVELOPMENT TEAM- Focus on the “how” / solution space
- Figures out how to best solve the defined problem
- Leverages agile development principles
Relieving the "PO as a bottleneck" problem
close collaboration / collaborative design
![Page 21: Agile UX In Real Life - Lessons Learned](https://reader034.fdocuments.in/reader034/viewer/2022052521/53f14c558d7f72e94b8b476f/html5/thumbnails/21.jpg)
COLLABORATING IN A MULTI-DISCIPLINARY AGILE TEAM
![Page 22: Agile UX In Real Life - Lessons Learned](https://reader034.fdocuments.in/reader034/viewer/2022052521/53f14c558d7f72e94b8b476f/html5/thumbnails/22.jpg)
COMMUNICATE LIGHT, VISIBLY & COLLABORATE ACROSS ROLES
![Page 23: Agile UX In Real Life - Lessons Learned](https://reader034.fdocuments.in/reader034/viewer/2022052521/53f14c558d7f72e94b8b476f/html5/thumbnails/23.jpg)
HTTP://STYLETIL.ES/
STYLE TILES FINAL SITE
ITERATE VISUAL LANGUAGE IN A LIGHTWEIGHT WAY
![Page 24: Agile UX In Real Life - Lessons Learned](https://reader034.fdocuments.in/reader034/viewer/2022052521/53f14c558d7f72e94b8b476f/html5/thumbnails/24.jpg)
LIVE STYLE GUIDE
BUILD A MODULAR DESIGN. CONTINUALLY REFINE & REFACTOR.
![Page 25: Agile UX In Real Life - Lessons Learned](https://reader034.fdocuments.in/reader034/viewer/2022052521/53f14c558d7f72e94b8b476f/html5/thumbnails/25.jpg)
My personal take on it➡ Good profits and repeat business requires
happy and loyal customers➡ Happy and loyal customers require products /
services with great user experience➡ Great software requires great collaboration
during product development (cf. Conway's Law)
TAKE AWAY: COLLABORATION IS KEY