{"id":11950,"date":"2021-01-05T07:00:37","date_gmt":"2021-01-05T12:00:37","guid":{"rendered":"https:\/\/mgrush.com\/blog\/?p=11950"},"modified":"2026-04-21T13:03:02","modified_gmt":"2026-04-21T17:03:02","slug":"scenario-planning","status":"publish","type":"post","link":"https:\/\/mgrush.com\/blog\/scenario-planning\/","title":{"rendered":"How Scenario Planning Helps Prevent Missing Requirements"},"content":{"rendered":"

Poor requirements don\u2019t impede projects, missing<\/em> requirements do.<\/h2>\n

Experience has taught us that one approach stands above all others when you want to scour for missing requirements\u2014consider \u2018dry runs\u2019 by using various scenarios found in scenario planning. Strive to build a range of understanding from the sunny and optimistic \u201csunny skies\u201d (best case\u2014rare) through the calamitous \u201cstormy skies\u201d (worst case\u2014rare). For robust analysis, include partly sunny and\/or partly cloudy conditions (most likely or frequent cases).<\/span><\/p>\n

For example, recently a vendor offered us a twenty percent discount for making a second purchase. However, without cookies and screen history, their site defaulted to their \u2018new customer\u2019 discount of ten percent. Thus, we were unable to use their \u2018special offer.\u2019 They had gathered the initial requirements properly (i.e., ten percent discount for new customers) but had not considered the occasional exception (special twenty percent discounts). Scenario planning built around functional requirements helps you anticipate and identify \u2018exceptions\u2019 while building more rigorous acceptance criteria.<\/span><\/p>\n

User Story Procedure<\/b><\/h3>\n

A familiar format for compiling User Stories<\/i> completes the following procedure but does not anticipate exceptions or conditions. For example, what alternative story develops when a customer\u2019s electricity is interrupted? What might customers do differently if they suddenly realize a financial windfall such as a tax return? Standard approaches create a baseline but do not leverage structure to understand or extract requirements under ALL conditions.<\/span><\/p>\n

As a _____________________ (persona)<\/span><\/p>\n

I want ____________________ (functionality)<\/span><\/p>\n

So that ___________________ (I get business value or benefit)<\/span><\/p>\n

Gherkin Syntax<\/b><\/span><\/p>\n

\"Scenario<\/a>

Gherkin Syntax<\/span><\/strong><\/p><\/div>\n

For others\u2019 User Stories<\/i>, some people prefer using the Gherkin Syntax<\/a>. Complete the Gherkin Syntax from each persona\u2019s perspective. However, it also lacks the rigor to explore or prompt for specific exceptions rather than baseline standards.<\/span><\/p>\n