Process: Agile Development

UXmatters has published 13 articles on the topic Agile Development.

Top 3 Trending Articles on Agile Development

  1. Design Sprints Revisited: Designing with Your Users and Developers

    December 20, 2021

    Many development teams are now working in some form of agile—be it Scrum, Kanban, or another form of agile that a team has adapted to their own needs. Thus, most teams organize their work in sprints. Sprints start with planning and end with reviewing the goals that you’ve accomplished and the process you’ve followed. However, because many UX designers think agile methodologies are primarily for developers, they face the problem of not knowing exactly where their work fits into the development process.

    In trying to solve this problem, Google Ventures created the idea of design sprints. During a process that usually lasts just one week, a team considers the problems, ideates a solution, tries it out, and learns from the experience. Ideally, all members of a product team participate in the design process. Leaving individual members or disciplines out of the product team can lead to miscommunication and barriers in the path of future implementation. Read More

  2. 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

  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