Which of the following is a technique commonly used for requirements gathering?

Storyboarding is a valuable technique for requirements gathering because it allows stakeholders to visualize processes, workflows, or systems in a manner that is engaging and easy to understand. By creating a sequence of images or diagrams that tell a story, stakeholders can better conceptualize how a product or service will function in real-world scenarios. This visual approach fosters communication and collaboration among team members and stakeholders, ensuring that everyone has a clear understanding of the requirements being gathered.

Storyboarding also helps identify gaps or misunderstandings early in the requirements-gathering process, as stakeholders can discuss and iterate on the visuals to refine their needs and expectations. This can lead to more accurate and comprehensive requirements, ultimately enhancing the development process and the final product quality.

In contrast, while budget analysis, DIP analysis, and retroactive evaluation may play roles in broader project management or evaluation contexts, they are not primarily focused on the initial phase of capturing and defining user requirements. They lack the interactive and exploratory aspects that make storyboarding particularly effective for gathering requirements.