How to Provide User Stories in Tickets Effectively: A Guide

To ensure efficient resolution of your issues, it’s essential to follow a structured approach when opening tickets. This guide explains how to split the actual business need (User Story) from the Functional Requirement.

TABLE OF CONTENTS

• User Story
• Example User Story:
  • Example Scenario
  • Example Scenario:
• Proposed Functional Implementation (Optional)
  • Example Proposed Functional Implementation:
• Tips for Writing Effective User Stories
  • Focus on the Business Problem:
  • Use the Correct Format:
  • Provide Context:
• Summary

User Story

The User Story outlines the business problem you are trying to solve. It should be formatted as follows:

As a {user role}

(who)

I want {business requirement}

(what)

so that {goal}

(why)

Example User Story:

As a producer, I want visibility to the relevant project and job information when reviewing samples that haven't been shot, so that I can align marketing needs to my available inventory.

Example Scenario

The Example Scenario provides additional context around the problem you are trying to solve. It may include:

• Definitions
• How you are currently solving the issue (if applicable)
• Use cases that help explain the business problem

Example Scenario:

Producers must deal with physical sample inventory in terms of the larger projects/jobs that drive the need for content creation. Samples are only relevant if the product that sample represents is needed for a campaign or job, and that product does not already have all relevant content captured.

Proposed Functional Implementation (Optional)

This section can include one or multiple ways the problem could be solved. While you are welcome to propose how you think it should be solved, the optimal functional solution may vary.

Example Proposed Functional Implementation:

Create a View to show me the products needed for each Project/Job, where I can update the Status of the related sample(s) for those products.

Example of an Incorrect User Story

Incorrect User Story Provided By User:

I need to export all my ShotFlow data to an Excel file.

Why is this incorrect?

The user is describing a HOW (export data to Excel) rather than articulating the actual business requirement (WHAT) and the goal (WHY). By only providing the HOW, the user has not provided the business context for this work. This functional solution (exporting data to Excel) may not be the most efficient or easiest for the user if the primary system can deliver the User Story without the need for manual data manipulation in another tool.

Tips for Writing Effective User Stories

Focus on the Business Problem:

Clearly define the business problem you are trying to solve without suggesting a specific solution

Use the Correct Format:

Ensure your User Story answers the WHO, WHAT, and WHY.

Provide Context:

Include an Example Scenario if needed to describe the specific situation and provide more context.

Optional Functional Implementation:

Propose one or more ways to solve the problem, but remember that the technical team will determine the optimal solution.

Summary

User Story answers WHO, WHAT, and WHY.

Functional Implementation answers WHEN, HOW, and WHERE.

By following this guide, you can create clear, concise, and effective tickets that will help the support team understand and resolve your issues more efficiently.