Elicitation and Usage-Centric Requirements

#133 - Software Requirements Essentials - Karl Wiegers

Topic 6 of 12

Published May 15, 2023 · Clip 30:49–37:07 (6:18)

Karl explains that elicitation is richer than 'gathering': it's partly collection, partly discovery, partly invention, with the business analyst as a guide, not a scribe. He then covers practice six — understand what users need to do with the solution — arguing that usage-centric exploration beats feature-centric thinking, enables prioritization at a higher abstraction, and uses better questions like 'what do you need to do?' He cites data that over 50% of features in common products are rarely or never used, and notes the analogy to jobs-to-be-done.