Top

Process: Requirements Definition

UXmatters has published 21 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. Communicating Customer and Business Value with a Value Matrix

    December 15, 2008

    So, you’ve wrapped up your customer research, completed your personas, and have even written a few scenarios that show how users would want to interact with your brand new product. What’s next? What happens to the personas and scenarios once you’re ready to start requirements definition and design. Are you sure you’ve adequately communicated the type of system your users need to the Business Analyst and Interaction Designer on your team?

    If you’re like me, you’ve always felt something was missing once you finished creating your personas and scenarios. They communicate the heart and goals of the user, but miss out on a lot of details. And while it’s the intent of both documents to do just that, neither personas nor scenarios succinctly communicates to your business what features a product or service should have and why it should have them. Read More

New on UXmatters