Overview
User stories is an option available on projects within the Enterprise Service Management (ESM) system. User stories are short, user-focused feature descriptions created within the project to represent a customer's need and value it provides. User stories are a core part of agile project management, where they can be assigned story points and linked to sprints.
Important
User stories are used in conjunction with Card Walls project plan.
Most user stories are summarized in a one-sentence story following a universally recognized format.
As a <type of user>
I want <some goal or action>
So that <some benefit or value>
An example:
As a registered user, I want to save my payment information, so that I can check out faster on future purchases.
Story Points and Value Points
To prioritize and plan these stories, projects use Story Points and Value Points. The following table summarizes the differences between the two. Together, they ensure the project builds what is easiest to deliver and delivers the highest impact first.
Core Differences Between Story Points and Value Points
| Feature |
Story Points |
Value Points |
| Description |
Measurement to estimate the overall effort, complexity, and risks required to implement a specific user story, the primary focus being effort & cost. Instead of estimating in hours, points provide a relative scale (often using Fibonacci sequence: 1, 2, 3, 5, 8) so teams can size tasks compared to one another. |
Measure the business impact or return on investment (ROI), with the primary focus being the benefit & impact. |
| Primary Focus |
Effort & Cost |
Benefit & Impact |
| What it considers |
Work volume, complexity, and risk |
Customer satisfaction, revenue, and strategic goals |
| Who Determines it |
The project team |
Product/Service Owners and Stakeholders |
| Common Scales |
Fibonacci sequence (1, 2, 3, 5, 8 ...) |
1-10 scale, 1-100 scale |
| Key Use Cases |
Sprint planning, team capacity, forecasting velocity |
Backlog prioritization, roadmap planning |
Best Practices for Implementation
- Separate the Estimates: Don't let the project team's effort estimates (i.e. Story Points) bias the Product/Service Owner's view of customer benefits (i.e. Value Points).
- Keep Points Relative: Story points are relative to each other (e.g. a 5 is twice a big as 2.5), while Value points should align with business KPIs (like revenue generated or users affected).
- Maintain Consistency: Remember that Story Points are unique to individual teams; what is a "3" for one group may be a "5" for another. However, Value Points should ideally be standardized across the project portfolio so leadership can compare features across projects.
Next Steps
Review the following articles for information on User Stories within project management.
Need additional help or have issues
For support, requests may be submitted anytime using the appropriate Enterprise Service Management form. Requests generate a Ticket which will be worked in order received and urgency by IT Employees with the knowledge and permissions to assist with the request.
For immediate assistance please review the Contact Us page for the appropriate support group.