Esther Derby

It’s not easy to build the right product. People sometimes don?t know exactly what they need, want things that won?t help, and don?t imagine what’s possible.

Agile project capture requirements on cards that contain a statement of want and benefit and notes on how to confirm the need is met. The intention isn’t to fully document the requirement on the card, but to make a note and create a reminder for a conversation with the customer.

Whether you are using agile methods or traditional requirements, valuable products start with understanding the customers context, their problems, what they want, and how they use a product.

However, most people aren’t born with the ability to speak naturally in user stories or fully formed requirements statements. So we must learn how to ask the right questions, draw out pertinent information and understand the customer?s world in those conversations.

In this session, you’ll learn about different types of questions, and when to use them to learn about how the customer currently uses a product, the problems they experience with the product, and problems that new features in the product might solve. Then, we’ll put that to work in practice interviews.

convert this post to pdf.

If you enjoyed this article and want to learn more about the conference, sign up for our email newsletter. We'll let you know about new developments, conference discounts, and other news. And we'll never, ever give away or sell your name or email address.

Tell a friend about this article

This entry was posted on Friday, January 8th, 2010 at 3:57 pm and is filed under Sessions 2010. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.