Top

Process: Agile UX

UXmatters has published 36 articles on the topic Agile UX.

Top 3 Trending Articles on Agile UX

  1. Is Focusing on Agile or Lean Damaging the Practice of UX? Part 1

    Ask UXmatters

    Get expert answers

    A column by Janet M. Six
    January 20, 2020

    This month in Ask UXmatters, our panel of UX experts discusses how development teams’ prioritizing the use of agile or Lean methodologies affects the practice of User Experience. Our panelists lament how the goal of speeding up development devalues UX research and design, leads to design inconsistencies, and encourages product-team members to take shortcuts. Agile and Lean’s focus on speed can also make it more difficult for product teams to keep the big picture in mind.

    Some companies have even decided that their use of agile or Lean methodologies means they can reduce the number of UX designers and researchers working within their organization—or that they can even bypass UX research and design altogether. This is a big problem! Read More

  2. User Experience and the Big Picture, Part 1: Problems, Problems

    January 20, 2020

    This is Part 1 of a three-part series in which I’ll ultimately present some radical thinking about how we could improve the software-development lifecycle (SDLC) and the key role that UX professionals can play in achieving this improvement.

    Those of you who are familiar with my other UXmatters articles—such as “Are You Still Using Earlier-Generation Prototyping Tools?”—are aware that I’ve given a great deal of thought to making the UX function more effective and efficient. If you’re familiar with some of my other articles—such as “Agile Problems, UX Solutions, Part 1: The Big Picture and Prototyping”—you’ll also understand that I’ve given even more thought to making the entire SDLC more effective and efficient, and the key role that User Experience plays in this important goal. Read More

  3. Choosing the Right UX Process for Your Software-Development Model

    June 17, 2019

    “It’s very easy to be different, but very difficult to be better.”—Jonathan Ive, Chief Design Officer, Apple

    Deciding on the right product-development process for your team can often be a paradox. Maintaining balance amidst a proliferation of inconsistencies in product requirements and development outcomes is challenging for both large and mid-sized organizations —especially when teams lack any metrics to measure their impact on a release.

    Friction arises when there is a mismatch between the user’s mental model and product features. When a development team finds itself in an untenable situation, the blame game begins. But as Mad Men’s Don Draper often said, “Move forward.” Read More

Champion Advertisement
Continue Reading…

Columns on Agile UX

New on UXmatters