Agile UX is all the rage and also widely debated. In a future post, we’ll outline the challenges and doubts surrounding Agile UX. Here, we define Agile UX and identify useful resources for refining this practice in your organization.
While Agile methodologies are well established, there is still confusion about Agile UX. As author and practitioner Debbie Levitt explains:
“Agile UX brings Agile software development together with the product and interaction design done by UX specialists. It embeds a UX expert on the Agile team and requires understanding and valuing the UX role. This means allotting time and budget for UX’s full process including research and testing.” (source: Agile UX: How to Incorporate UX and Product Design into Agile)
In other words, Agile UX does not mean adding one line to a checklist or assigning “UX tasks” to a product or project manager. To function properly, Agile UX requires allotting time for user research, interaction design, testing, and iteration by a seasoned UX practitioner.
A reminder: Agile refers to a group of software development methodologies. Iterative development is an essential part of this process. Widely used Agile frameworks include Scrum and Kanban.
In Here is how UX Design Integrates with Agile and Scrum author and Agile and Lean UX Expert Jeff Gothelf outlines five groupings of UX activities to include in the Scrum framework (again, Scrum is one of the most popular Agile frameworks).
Gothelf concludes by explaining that these activities cannot happen without a dedicated designer assigned to the scrum team. This designer’s presence ensures that design activities are prioritized and completed.
If the design work is outsourced to a designer outside of the team (whether that designer is in-house or not) then the team finds itself back in the “Big Design Up Front” style also known as waterfall or the “sprint ahead” method — all of which reduce collaboration, shared understanding, and trust between team members
Leaders and teams who are serious about human-centered design should read this passage carefully. Simply including UX on a checklist accomplishes nothing. Sprint planning must allot time for dedicated UX research, design, and iteration if there is any hope of creating usable and engaging products.
In a similar vein, author and Agile expert Jeff Patton describes Twelve Emerging Best practices for Adding UX Work to Agile Development. Patton provides a detailed description of each best practice. Highlights include:
This article is long but worth reading for UXers who need a deep understanding of how to include UX when Agile development is firmly established in an organization.
The Agile Manifesto was written from a development point-of-view. At the time, many did not grasp the importance of UX. In 8 success factors for UX in Agile development, the authors explain how they have adapted Agile in their UX practice. Key tactics include:
Read this article to learn how to refine UX Agile in your organization.
As explained above, integrating UX and Agile development is useful when properly executed. Another approach is to focus on making the design process Agile by following Google’s 5-day sprint design method.
While this method cannot replace all design processes, it allows for rapid iteration.
In a similar but more specific vein, Laura Rademaker describes 3 ways Scrum strengthened our UX team. She opens by explaining that her team does not follow the traditional Scrum process of dividing responsibilities between product owners, a scrum master, and the development team. “Our team instead consists of 4 UX designers with Scrum responsibilities split between us.”
While this unconventional approach to Scrum won’t work for every UX team, the idea merits consideration as UX teams strive to increase efficiency and collaboration.
Another way to approach efficiency is to consider which design stages can be reduced or even eliminated. It’s common knowledge that UX designers usually draw wireframes before creating high fidelity prototypes. The idea is to avoid wasting time on details that the team will likely change as the team modifies and refines the design.
With his article Wireframes are becoming less relevant — and that’s a good thing, Sean Dexter offers a contrarian view. He defines wireframes as “The prototypical wireframe attempts to be an accurate representation of layout and information architecture while intentionally avoiding high visual fidelity and sometimes high content fidelity as well.” This approach works well in a traditional, linear development environment.
In contrast, Agile focuses on “smaller, more frequent delivery of fully realized ‘vertical slices.'” With this approach, it makes sense to include visuals and information architecture in early design iterations.
Speed is key. UX practitioners on Agile teams must iterate within weeks, even days. In this accelerated environment, “the extensive up front mapping phase that so often gives birth to wireframes is less likely to have a place.”
Dexter does not argue that wireframes are never useful. Instead, he suggests that wireframes are not required for all projects involving UX design.
While we’re not ready to abandon wireframes here at UI UX Training we encourage UX practitioners to consider Dexter’s well-argued case for limiting wireframes in Agile UX environments.