Process: Requirements Definition

UXmatters has published 20 articles on the topic Requirements Definition.

Top 3 Trending Articles on Requirements Definition

  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. The Best Ways to Prioritize Products and Features

    Ask UXmatters

    Get expert answers

    A column by Janet M. Six
    December 23, 2013

    In this edition of Ask UXmatters, our experts discuss the best ways of prioritizing a list of products and features.

    In my monthly column Ask UXmatters, our panel of UX experts provides answers to our readers’ questions about a broad range of user experience matters. To get answers to your own questions about UX strategy, design, user research, or any other topic of interest to UX professionals in an upcoming edition of Ask UXmatters, please send your questions to: [email protected]. Read More

  3. Sharing Ownership of UX

    May 28, 2007

    A UX architect, or lead UX designer, is the member of a product team who is primarily responsible for ensuring all aspects of a digital product that users experience directly—including its form, behavior, and content—are learnable, usable, useful, and aesthetically pleasing. Thus, a UX architect has an important role to play from a product’s conception to its launch. But creating truly great products requires an entire product team to place the needs of users foremost when making product decisions—or even better, a user-centered corporate culture. If you find yourself in a less enlightened company or on a product team that just does’t get how creating great user experiences contributes to a company’s success, you should take every opportunity to evangelize the value of UX to people in your company—from the executive management team to your peers in other disciplines on product teams. If you need help making the case for UX, have a look at my article on UXmatters, “Why UX Should Matter to Software Companies.” Read More

Supporter Advertisement
Continue Reading…

New on UXmatters