Managing Software Requirements: A Use Case Approach, Second Edition

Chapter 13. Storyboarding

Key Points

• The purpose of storyboarding is to elicit early “Yes, But” reactions.

• Storyboards can be passive, active, or interactive.

• Storyboards identify the players, explain what happens to them, and describe how it happens.

• Make the storyboard sketchy, easy to modify, and not shippable.

• Storyboard early and often on each project with new or innovative content.

Perhaps no requirements elicitation technique has been subject to as many interpretations as has “storyboarding.” Nonetheless, most of these interpretations agree that the purpose of storyboarding is to gain an early reaction from the users on the concepts proposed for the application. In so doing, storyboards offer an effective technique for addressing the “Yes, But” ...