Top

Process: Agile Development

UXmatters has published 12 articles on the topic Agile Development.

Top 3 Trending Articles on Agile Development

  1. Agile Development Is No Excuse for Shoddy UX Research

    November 21, 2016

    Agile development and UX design are like a couple in an arranged marriage—a relationship between two strangers who are expected to coexist, develop trust and respect, and eventually, love each other. Throw UX research into the mix and you have the makings of an even more awkward alliance, as you can see in this typical conversation between a UX designer and a product owner, somewhere in the middle of Sprint 0:

    Product owner: “Hey Jen, when can we see some wireframes?”

    UX designer: “Well, we’re wrapping up our user interviews and putting together some personas—basically trying to get more clarity around our target users. We’ve already started on some sketches, but I expect we’ll need to make some tweaks based on what we learn.”

    Product owner: “That’s all very good. But we can’t afford the luxury of spending too much time on research. Sprint 0 ends next week. We can’t keep the developers waiting! Let’s speed things up. I’d really appreciate if you could get those wireframes going quickly?” Read More

  2. Agile, Spiral, Lean, DevOps, and User Experience

    Ask UXmatters

    Get expert answers

    A column by Janet M. Six
    May 17, 2021

    This month in Ask UXmatters, our expert panel discusses whether UX designers still receive frequent requests for agile, or whether they’re now receiving more requests for spiral, Lean, or DevOps. Our panelists also explore whether the rise of these other methodologies has affected the UX designs they create.

    Our experts first discuss what agile means and confront the reality that different organizations often implement agile in different ways. The panel then considers the impact of whether an organization implements agile across the entire company or only on individual teams. The root motivation for requesting agile, spiral, Lean, or DevOps is also important: why is the organization asking for a particular methodology? Is it really the methodology that the company wants or certain attributes of the resulting designs. Or maybe they request the methodology with the expectation that it would reduce the time or financial investment that would be necessary. Read More

  3. Keeping Your Clients Happy When Doing Agile Development

    August 12, 2019

    If you use—or want to start using—an agile-development process, you probably already know its benefits, but you might not be as aware of one of its main drawbacks. Even though 46% of US organizations and 85% internationally report that they’ve used an agile approach within the past year, communicating your agile process to clients remains a challenge.

    Specifically, the problem is bridging the gap between clients’ expectations of the process and the way agile really works. But overcoming this difficulty is well worth the effort if you wind up with a first-rate product and a fully satisfied client.

    Of course, some clients are already quite familiar with how agile works. However, for those who aren’t—and whose previous experience was with waterfall product-development approaches—explaining the process and merits of agile can be tough. Sure, your clients might know some agile buzzwords, be familiar with some of the tools, or know the importance of meetings to the agile process. However, it’s unlikely that they understand how agile actually works in practice. Read More

Champion Advertisement
Continue Reading…

New on UXmatters