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
When you register, you'll receive targeted emails designed to keep you informed of the most relevant information on Agile development, application security, testing & QA, software requirements, and more.
Hannah Smalltree, Editorial Director
This was first published in July 2007