Home » All Blogs » Salesforce User Stories in Action

Salesforce User Stories in Action

Join this interactive session to understand how to write Salesforce specific user stories, how to prioritize user stories, and learn some guidelines around story estimation. Join us to learn about Salesforce User Stories in Action and How to Write User Stories for Salesforce.

What is Backlog?

Backlog is a prioritized list of identified values (items). That is associated with products/services and/or results. That are delivered to an identified customer (individual, group, entity/system).

Salesforce User Stories in Action

User Stories refers to the delivery of specific value to a specific user – Provides the Who?, What? & Why?

  • Description Format: As a [user], I need [some outcome], so that I can [achieve some benefit/value].
  • Decomposition: The User Story must be decomposed into multiple Sub-tasks (actions to be taken). Note: if no Sub-tasks (or only one Sub-task) are identified, then the User Story is likely merely a Sub-task of some other User Story.
  • Duration: Must be right-sized to be completed in a Sprint (typically 2 weeks), or in the case of Kanban, a reasonably short cycle time (maybe 2 – 4 weeks)
  • Sizing: Typically sized by Story Points.

Story Point

Story Point Expresses the estimated “size” of a backlog item. Are relative, i.e., are not connected to any specific unit of measure (e.g., time, etc.). Various factors are used to establish a story point value:

  • Volume: How many “things” to be done?
  • Complexity: How hard/difficult is the work?
  • Knowledge: What do we currently know about what needs to be done?
  • Uncertainty: What do we currently not know about what needs to be done?

Based on the modified Fibonacci Sequence of numbers (1, 2, 3, 5, 8, 13, 20…)

Diagram

Description automatically generated

Using an abstract measure of Story Points makes us focus on relative sizes of Backlog items. Regarding Knowledge and Uncertainty, the team could consider the following:

  • Group experience – “We’ve done this before and we can do it again.”
  • Similar experience – “We’ve done something like this before and we can use what we learned then.”
  • Unique experience – “We’ve never done this but we have the skills in place to figure it out.”
  • Individual experience – “I’ve done this before and I can show others how.”
  • No experience – “This has never been done before.”

Size Estimation Games

Development Team can use a pseudo-poker game to estimate (relatively) the size (story points) of backlog items.  Examples of virtual games are:

Salesforce User Stories in Action Video

We will learn about User Story Writing and how User Story should be Prioritize. Best practices for User Story Estimation

YouTube video

Please subscribe our YouTube channel to get notification for video upload.

Share your love:
Amit Chaudhary
Amit Chaudhary

Amit Chaudhary is Salesforce Application & System Architect and working on Salesforce Platform since 2010. He is Salesforce MVP since 2017 and have 17 Salesforce Certificates.

He is a active blogger and founder of Apex Hours.

Articles: 417

Leave a Reply