User-Centered Requirements

Issue addressed “We have our functional requirements, but how can we be sure that this is what our end-users really want, and would actually use?”

Your challenge: Don't spend money on the wrong user-requirements

Gathering and prioritizing a good set of end-user requirements is the foundation of a successful project. Misunderstood or missing requirements are the primary reason for cost overruns in software projects. Gathering and prioritizing end-user requirements is no place to skimp. Don’t waste time and money on features that your target market won't use.

My solution for your project

My service gathers and prioritizes user-requirements directly from representative samples of individuals from your target markets. I employ rigorous scientific psychological and statistical techniques to provide unmatched quality of data in user-requirements gathering and prioritization.

I use multiple convergent methods to maximize effectiveness: data are both qualitative and quantitative in nature, and are gathered on both an individual-user and on a group basis.

Task analysis procedures are incorporated into the process to ensure that outputs are truly user-centered, and can be directly used effectively in use-cases and object modelling. Where warranted, my contextual field study service can extend the requirements process right into the end-user's physical environment.

In addition, information is gathered from end-users that provide measurable targets for meeting end-user requirements in your product's design.

If required, the requirements process can be strategically focussed on your competitor's product as well. I can use these techniques in live group situations, or in distributed-internet adaptations for geographically diverse representation.

The effectiveness of these methodologies has been demonstrated in many large-scale development projects in which I have been involved. Analyses can be completed just a few days after the data are collected.

Pricing for user-centered requirements gathering and prioritization is largely determined by the complexity of the project, which is most directly affected by:

• the quality and comprehensiveness of the market-sample your project requires
• the difficulty in finding and incenting qualified individuals from your target market to participate in requirements activities (e.g., teenage web surfers vs. investment bankers)
• the amount of existing requirements information your project team already possesses

Last update: May 07, 2002
(c) 2002 Don Hameluck Usability Consulting Inc.

Home   -   Usability for your project   -   Services   -     Partnerships   -    Clients & Resume   -    Contact me