Current approaches to integrating UX into agile development processes like Agile and Lean focus either on building features quickly (Agile) or launching products quickly (Lean), which can result in UX testing happening too late. While agile values speed, it is important for UX designers to be involved throughout the development process to ensure the best user experiences are designed, tested and validated. UX practitioners need to communicate frequently with development teams, be present at all stages of the sprint, and establish trust and shared understanding of the UX process and vision to successfully integrate UX into agile.

1. Current state of UX
process
Agile ¨UX¨

2. Processes and methodologies provide a framework
teams with diverse skills to work together effectively.

3. No strict guidelines how long should take
Traditional UX Old waterfall process
Research
Design
Test

4. Agile ¿UX?
Agile development
process
Is great for our dev
process!
I want to be
part of that!
UX
UX
Dev.
when UX designers try to fit into a developer’s methodology, the best UX ideas don’t always get built, tested and validated.

5. Lean ¿UX?
MVP Concept
Launch quickly
Build quickly
Short CYCLES…
which means that testing the idea or the
user experience only happens after the
product is built and launched.

6. All have speed in common
What they have in
common?

7. Focus: Agile on build; Lean on launch;
Agile
Methodology
Lean Methodology
Traditional UX

8. Focus: Agile on build; Lean on launch; esign sprint on idea(s).
Agile
Methodology
Lean Methodology
Simply UX
Design Thinking
Design Sprint
UCD
ACD
TCD / PCD
Co operative Design
Scrum
XP
Kanban
Lean Software Dev.
Crystal
DSDM
FDD
TDD

9. Value of Agile
MethodologyIt’s very expensive to build products without research.
The time you “save” from skipping the research phase almost always
comes back to bite you 10 times over.
10X

10. “
“On Agile development practices, the training rarely
discusses best practices for integrating UX design into the
development process”
—

11. -RESEARCH -
What others
UXsers think?

12. Opinions
on what’s
working
Trust and earned respect
Being transparent about the
UX process helped some
respondents foster trust
between themselves, their
product managers, and the
technical staff on their
scrum teams.
Be present on the life of scrum
team
Being a constant voice in the
development lifecycle helps
keep the UX vision in line.
Frequent communication outside agile meetings
UX colleagues shared that adding meetings specifically
devoted to coordinating UX activities with the team were
successful in increasing ownership and a shared vision of the
design direction.

13. Opinions
on wasn’t
working
Confilct expectations about quality
The opinion that ‘This is good enough.’ Design implementation
always goes to the bottom of the priority for the sake of MVP…
Pushed to the next release and stay in the UX bug list forever
Lack of holistic planning and prioritization for UX
No time is considered for design of the overall framework.
Scrum teams jump into feature releases. They’re building
inside out instead of outside in or holistically
Unclear expectations about the UX role on the team
UX was seen as pixel pushers who made things look nice after the
developers built their features”
“Developers build whatever UI they think is appropriate while a
designer is working on design iteration or testing.”

14. Opinions
on wasn’t
working
1. Perception of UX as less valued than development
2. Perception that technical staff is disinterested in
users’ needs
3. Being disconnected from the regular activities of
the scrum team

15. -SUGGESTIONS -

16. ◉ Be Proactive no reactive
◉ Ux must work at least one sprint ahead (sprint 0)
◉ Improve Agile practice makes perfect
◉ Agile changes in each organization
◉ Helping new UX team members with time management skills
◉ Explicitly training people to recognize that there is specialists on the team
◉ Setting clear expectations for involving UX in team activities
◉ Including UX goals and needs in sprint retrospectives.
My Point of view...

17. Thanks!