Using card sorting to decide software requirements

Indecision can arise in the software requirements phase when a team is deciding what field type and process should surround the field information. Card sorting can mitigate that.

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.


This was last published in July 2007

Dig Deeper on Software Requirements Gathering Techniques

PRO+

Content

Find more PRO+ content and other member only offers, here.

Start the conversation

Send me notifications when other members comment.

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

Please create a username to comment.

-ADS BY GOOGLE

SearchSOA

TheServerSide

SearchCloudApplications

SearchAWS

SearchBusinessAnalytics

SearchFinancialApplications

SearchHealthIT

Close