Prioritizing Requirements

#133 - Software Requirements Essentials - Karl Wiegers

Topic 10 of 12

Published May 15, 2023 · Clip 49:20–52:23 (3:03)

Karl discusses practice 13: prioritize the requirements. Teams should prioritize as simply as possible — a conversation may suffice, or a spreadsheet-based analytical approach when needed. He lists factors to consider: business value, contribution to goals, who requested it, frequency of use, and cost/difficulty. He emphasizes deciding early who has the authority to make priority decisions and how, mentioning techniques like planning poker and the hundred-dollar allocation, and notes rank ordering works for 15 items but not 300.