According to Cambridge dictionary, a scenario is a description of possible actions or events in the future.

For example, "there are several possible scenarios, including a horrific/nightmare scenario such as a Third World War."

A scenario is a written outline of a movie, novel, or stage work giving details of the plot and individual scenes.

For example, "imagine the scenarios for four short stories."

A scenario is a setting, in particular for a work of art or literature.

For example, "the scenario is World War II."

In scenario based approach we construct a sequence of actions or events according to the inner logic of the protagonist (often the user) to accomplish certain objectives.

Therefore a scenario based approach is centered on the protagonist (often the user). Thus the term "user centered approach". Scenario based thinking requires one to "think according to the inner logic of the protagonist" or "think like the user". (This is also the basic requirement of a creative writer.)

Scenario based approach can be applied to scenario based design, user story design, patterns design, object oriented design and so on. In what follows we will discuss each one briefly to illustrate the main idea.

Scenario Based Design

Scenario based design, or SBD for short, is a method of user centered design. It considers very different user groups and situations when designing the interface. SBD is an iterative process.

Process design for scenario planning can be broken down into three components: direction setting, approach development, and roadmap creation.

DIRECTION SETTING

The first component, direction setting, helps orient the process towards specific needs, outcomes, and stakeholder identification. By understanding this component and its steps, an organization will have a solid base for the next two components, approach development and roadmap creation.

APPROACH DEVELOPMENT

The second component, approach development, helps further detail the process by focusing on key factors and building out stakeholder interaction. An understanding of this component and its steps prepares an organization for the next component, roadmap creation.

ROADMAP CREATION

The third and last component, roadmap creation, further supports organizations in generating a roadmap that is tailored to their specific scenario planning needs. As the culminating component, its steps require an understanding of the first two components, direction setting and approach development. There are many software tools to create roadmaps.


JIRA software to create Roadmaps


DRAGON software to create Roadmaps

Roadmap Creation Step 1: Select a scenario planning process manager

A scenario planning process requires a "process manager" to oversee all activities and ensure connectivity between the various moving parts of the effort.

Roadmap Creation Step 2: Establish milestones and list associated tasks

There is a basic set of milestones common to scenario planning processes. Each milestone has a series of tasks or efforts associated with it.

User Story Design

Each User Story needs to be testable, need to demonstrate, that requirement has been met. Here is effective formula, which demonstrate, that specific user story has been met:

Given < context > [and < more context > ], When < something happens >
Then < outcome > [and < another outcome > ]

Here is the example of using this Given/When/Then recipe, which specify furfure detail, about the original user story. Before it was broken in smaller user stories und now it is associated to Given/When/Then Criteria.

Title: User cancels reservation

User Story:

As a user with a reservation, I want to cancel my reservation 
so that I get a refund.

Scenarios of user story:

Scenario 1: User is a premium member
Given I am a premium member, when I cancel under 24 hours, then 
I incur no penalty.

Scenario 2: User is a typical member

Given I am a non-premium member, when I cancel less that 24 hours 
in advance, then I pay 50% fee.

Scenario 3: Email confirmation

Given I am a site member, when I cancel my reservation, then I am 
emailed a confirmation.

Very offen we can put the whole user story on a card, which is called the Story Card.

Here you can find user story title, description or user story and success criteria or scenarios. At the bottom of the card we can also see the estimation information for the card.

Patterns Design

According to Christopher Alexander, each pattern must occur in a certain context, and faced with a certain problem, a certain solution is proposed:

Given < context > [and < more context > ], When < a problem happens >
Then < solution > [and < another solution > ]

A list of some patterns:

1.	TOY Motivation
a.	Context: Modern Times
b.	Problem: Old and young not together as much
c.	Solution: TOY service


2.	Software motivation
a.	Context: TOY Service
b.	Problem: Don’t have software to execute plans
c.	Solution: Create website/tool that allows sign-up, searches sex offender 
	registry, recommends pairings, provides “mad libs”-like 
	GUI interface to generative AI, report generation


3.	Someone gets injured
d.	Context: TOY scenario
e.	Problem: A kid or senior or staff falls and gets hurt
f.	Solution: Follow injury protocol


4.	Parent doesn’t show up
g.	Context: TOY scenario
h.	Problem: Parent doesn’t show up
i.	Solution: Call parent, then call emergency contact 
	(collected from parent at sign up), then call alternative 
	care/authorities if no responses


5.	Senior doesn’t show up/cancels
j.	Context: Leading up to and at TOY scenario
k.	Problem: Senior cancels at last minute or doesn’t show up
l.	Solution: Call seniors 1 day prior to appointments to confirm,
	collect senior consent to serve as “on-call” volunteer
	(they don’t mind being called for short notice appointments)
	in case senior cancels or doesn’t show up 

Object Oriented Design using IC Cards

IC Cards were developed by Shi-Kuo Chang as a generalization of CRC (Context Responsibility Collaboration) Cards for Object Oriented Design (OOD).

Scenario Lab at National TsinHua University

Conclusion: Think Like the User and Walk Like an Egyptian!

Scenario based thinking requires one to "think according to the inner logic of the protagonist" or "think like the user". (This is also the basic requirement of a creative writer.)

King Tut - SNL