So I want to share some of my experiences - both good and bad - of how to deal with agile development as a UX Designer. What I have learned in the strive to be an agile UX designer myself.
5. Established 1998
2000+ digital turn key solutions
E-commerce, Member
solutions, Apps, In-store
concepts, Chat bots and more
Strategy, Concept, Design,
UX, Integration, Usability lab,
Testing and Conversion
Barcelona, Berlin,
Boston, Copenhagen,
Kaunas, Vilnius
24. Share your work in early stages
Involve your team in UX analysis
Say your opinion … again
See user test … together
Pitfalls TO DO’s
Many stakeholders
Only sharing WHAT not WHY with team
Letting framework determine UX
Being a UX ‘know it all’
25. Relations
Have you ever thought that your client (or your team) was building the
wrong experience, but you didn’t speak up or know how to convince them
otherwise?
27. Agile process and scrum method
Scrum team
Product owner Product backlog Sprint backlog Sprint (2-4 weeks)
As a <type of user>,
I want <some goal>
so that <reason>.
Implementing
IntegrationTest
Installation
28. Agile process and scrum method
Scrum team
UX Designer Product backlog Sprint backlog Sprint (2-4 weeks)
As a <type of user>,
I want <some goal>
so that <reason>.
Implementing
IntegrationTest
Installation
46. Marcin Treder
The ultimate goal of Agile UX is to
unify developers and designers in the Agile
process of product development
UXPIN – https://www.uxpin.com/studio/blog/lean-ux-vs-agile-ux-is-there-a-difference/
47. Marcin Treder
The ultimate goal of Agile UX is to
unify developers and designers [and clients] in
the Agile process of product development
UXPIN – https://www.uxpin.com/studio/blog/lean-ux-vs-agile-ux-is-there-a-difference/
48. Pitfalls
A lot of individual stakeholders
TOO many detail specifications
TOO structured
Being a UX ‘know it all’
49. One touch point with client
Keep updating team of client needs
Storytime and workshops
Ask the team to find best UX
Pitfalls TO DO’s
A lot of individual stakeholders
TOO many detail specifications
TOO structured
Being a UX ‘know it all’
50. Design
Have you ever been blindsided of either “new” design gimmicks or your
developer simply saying ‘No, can’t do’?
64. Full design upfront
Saying yes without a why
Not framing your project
Forgetting you are an UX expert
Being an UX ‘know it all’
Pitfalls
65. Full design upfront
Saying yes without a why
Not framing your project
Forgetting you are an expert
Being an UX ‘know it all’
Only design enough to start dev
Say no to client and team
Share all your (mis)steps
Guide in a human way
Patiently share why UX matter
Pitfalls TO DO’s
67. Only sharing WHAT not WHY with team
TOO structured
Forgetting you are an expert
Being an UX ‘know it all’
Pitfalls
68. Only sharing WHAT not WHY with team
TOO structured
Forgetting you are an expert
Being an UX ‘know it all’
Explain your analysis
Accept chaos – and structure for input
Guide in a human way
Be an UX ambassador
Pitfalls TO DO’s
69. Only sharing WHAT not WHY with team
TOO structured
Forgetting you are an expert
Being an UX ‘know it all’
Explain your analysis
Accept chaos – and structure for input
Guide in a human way
Be an UX ambassador
Test – a lot
Ask WHY – a lot
Change your mind – a lot
Pitfalls TO DO’s