Using card sorting to decide software requirements

Indecision can arise during the software requirements phase when a team is deciding what field type and process should surround the field information. To mitigate that, use simple card sorting. Pose questions that are open-ended, give multiple-choice answers, and make each person decide quietly. Reveal the answers as a group, and the "ah-ha" veil will be lifted that everyone sees data differently. From there, work on the commonalities and start talking about the process.

    Requires Free Membership to View

This was first published in July 2007

There are Comments. Add yours.

TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.