Resources > Articles

Use Scenarios are Stories That Provide Context

Post Author
  • Steve Johnson was a founding instructor at Pragmatic Institute, a role he held for more than 15 years before he left to start Under10 Playbook. In his return to Pragmatic Institute, Steve supports the complete learning path for product teams, ensuring they are fully armed for success.  Over the course of his career, Steve has helped thousands of companies and tens of thousands of product professionals implement product management processes. He has worked in the high-tech arena since 1981, rising through the ranks from product manager to chief marketing officer. Steve has experience in technical, sales and marketing management positions at companies that specialize in both hardware and software. In addition, he is an author, speaker and advisor on product strategy and product management.

Use Scenarios are Stories That Provide Context

Over the years, product management has attempted many different approaches to describing customer needs. We’ve used traditional requirements, use cases and open discussions. Today, we often use some form of a story. Here’s the Pragmatic argument explaining the power of use scenarios.

Most teams have adopted a user story formula for writing requirements: “As a <role>, I want <a feature> so I can <achieve an outcome>.”

Structure is nice. But the problem with today’s user stories is that they aren’t interesting. And they aren’t stories.

 

A story should be a use scenario—one or more illustrations of a problem for a persona.

Use scenarios are narratives. It explains the problem in the form of a real-life story. And it doesn’t mandate the implementation. And it doesn’t have to be boring.

 

Jennifer is a divorced working mom and she worries about her daughter, Sally. After all, who doesn’t worry these days? To make things worse, Jennifer’s ex-husband is unreliable; he often makes commitments to pick up Sally at school or at after-school projects, and then forgets completely.

For example, one afternoon at 3:30, Jennifer learned that Sally was still at school when she was supposed to be at soccer practice. Jennifer wondered, “Why did I ever marry that jerk?” as she raced from the office to pick up Sally.

Jennifer would feel a lot better if she always knew where Sally was—that is, when she was where she’s supposed to be, and more important, when she’s NOT where she’s supposed to be.

 

The question for your product team is: What can we do for Jennifer and Sally?

Bring a group of smart designers and developers together to talk about Jennifer and Sally and their problems. Tell the team about the business opportunity found in solving those problems. And participate in a brainstorming session on how you might solve them with your organization’s expertise and innovations.

Ron Jeffries, one of the three founders of Extreme Programming (XP), advocates the form of “card, conversation, confirmation” for stories.

By itself, the card isn’t valuable, it is merely a placeholder for the story. Each story requires a discussion with the product team and a method for determining when the story capabilities have been delivered successfully. Unfortunately, many teams seem to have forgotten the conversation and confirmation parts.

Don’t wait until the end of planning to involve your product team. Good stories and use scenarios are written with the team, not for the team.

 

Learn more about how to utilize and craft use scenarios  

Pragmatic Institute Course: Build 

This course gives you the tools you need to prioritize requirements and plan releases that deliver truly remarkable experiences to your market.  

What you’ll learn in Build:

  • Implement a proven approach for working across locations and development methodologies
  • Empower product management to focus on the “what,” and development to focus on the “how” of building better products
  • Group requirements to ensure releases deliver results
  • Provide clear context on who to build for and what problems to solve
  • Streamline estimates for increased efficiency

>> learn More 

Author

  • Steve Johnson was a founding instructor at Pragmatic Institute, a role he held for more than 15 years before he left to start Under10 Playbook. In his return to Pragmatic Institute, Steve supports the complete learning path for product teams, ensuring they are fully armed for success.  Over the course of his career, Steve has helped thousands of companies and tens of thousands of product professionals implement product management processes. He has worked in the high-tech arena since 1981, rising through the ranks from product manager to chief marketing officer. Steve has experience in technical, sales and marketing management positions at companies that specialize in both hardware and software. In addition, he is an author, speaker and advisor on product strategy and product management.

Author:

Other Resources in this Series

Most Recent

plan, strategy
Article

How to Create a Strategic Product Plan

Most technology companies have a product management department serving as the voice of the customer and helping to understand market needs better but is product management really being used strategically?
Optimizing product management budgets
Article

How to do More With the Same (or fewer) Resources in 2023 with Segmentation and Targeting Updates

Six steps to a data-driven understanding of your best-fit buyer. Improve the efficiency and effectiveness of your marketing programs by shifting your focus (and budgets) to best-fit personas and ICPs. 
Person working on project management software on a tablet
Article

10 Tools for Product Managers 

The right product tools can make it easier to manage your team, but there are hundreds out there—so how do you choose which one is right for you?
Purchasing on a mobile device with a credit card
Article

8 Distribution Strategy Examples For Product Teams 

A distribution strategy is a blueprint for how your company delivers its products to customers. Here are 8 methods and helpful examples. 
Magnifying glass emphasizing the word data
Article

Going Beyond Win/Loss Data

The true value of a win/loss program comes from unfolding the narrative behind that data. 

OTHER ArticleS

plan, strategy
Article

How to Create a Strategic Product Plan

Most technology companies have a product management department serving as the voice of the customer and helping to understand market needs better but is product management really being used strategically?
Optimizing product management budgets
Article

How to do More With the Same (or fewer) Resources in 2023 with Segmentation and Targeting Updates

Six steps to a data-driven understanding of your best-fit buyer. Improve the efficiency and effectiveness of your marketing programs by shifting your focus (and budgets) to best-fit personas and ICPs. 

Sign up to stay up to date on the latest industry best practices.

Sign up to received invites to upcoming webinars, updates on our recent podcast episodes and the latest on industry best practices.

Training on Your Schedule

Fill out the form today and our sales team will help you schedule your private Pragmatic training today.

Subscribe

Subscribe

Training on Your Schedule

Fill out the form today and our sales team will help you schedule your private Pragmatic training today.