Agile software development and user experience (UX) design share common goals of delivering systems faster that are more valuable and widely used by customers.
Adding UX to Scrum is crucial to delivering value, however, resistance can arise due to contextually dependent design needs.
In the Waterfall-based projects, there is a significant risk of missing the mark in terms of user experience.
In Scrum-based development, the risk of building an unusable or non-useful system is much lower as users are frequently considered and validated at short intervals.
Introducing Scrum into traditional organizations raises a challenge. Self-sufficient teams are required to make decisions by pulling people from separate departments.
In Agile organizations, quality control has been integrated into teams, though it may remain partially separate in contexts where critical.
When trying to integrate UX and development work, an intuitive option for traditional organizations is to create Sprint cycles. This approach called dual-track has several problems including poor interaction between the user, designer and developer leading to misunderstandings and wasted work.
Another approach is to have a single Sprint where designers and developers work concurrently, the method raises doubts on planning and work alignment, but is explained in Scrum.org courses for Dual-track integration.
The second article in this series How to Integrate UX and Scrum - Adapting the Framework to UX addresses questions by reviewing the Product Backlog, PBIs, refinement, and events.