Prioritizing user stories is a fundamental aspect of agile project management. It involves determining the order in which user stories should be addressed based on their importance, value to the customer, and other relevant criteria. Prioritization ensures that the team focuses on delivering the most critical and valuable features early in the development process

1. Prioritization Technique
~Mohit Budhiraja

2. Prioritizing
Techniques
• Prioritizing user stories is a
fundamental aspect of agile
project management. It involves
determining the order in which
user stories should be addressed
based on their importance, value
to the customer, and other
relevant criteria. Prioritization
ensures that the team focuses on
delivering the most critical and
valuable features early in the
development process
Importance of Prioritization
• Customer Value Focus
• Early Delivery of Value
• Adaptability to Change
• Resource Optimization
• Time-to-Market Reduction
• Efficient Sprint Planning
• Continuous Learning and
Improvement
~Mohit Budhiraja

3. Types of User story Prioritizing techniques
MoSCoW Method
Kano Model
High, Medium, Low (HML)
Relative Prioritization
Bubble Sort
Story Mapping
Business Value and Complexity (BVAC)
Impact vs. Effort Matrix
Risk-Based Prioritization
Cost of Delay (CoD)
Weighted Shortest Job First (WSJF)
Buy a Feature
~Mohit Budhiraja

4. MoSCoW Method
• The MoSCoW method is a prioritization technique commonly used in Agile project management to categorize and prioritize
requirements or user stories. The name "MoSCoW" is an acronym derived from the initial letters of four prioritization categories: Must-
Have, Should-Have, Could-Have, and Won't-Have. Each category represents a different level of priority and importance for features or
requirements.
• User Story 1: (Must-Have)
As a customer, I must be able to log in to the system using my
username and password to access personalized content.
• User Story 2: (Must-Have)
As a customer, I must be able to browse the product catalog, view
product details, and add items to my shopping cart.
• User Story 3: (Should-Have)
As a customer, I should receive an email confirmation after
successfully placing an order, including order details and an estimated
delivery date.
• User Story 4: (Should-Have)
As an administrator, I should have access to a dashboard displaying
real-time analytics of customer activities and order trends.
• User Story 5: (Could-Have)
As a customer, I could have the option to customize my user profile by
adding a profile picture and updating personal information.
• User Story 6: (Could-Have)
As a customer, I could receive personalized product recommendations
based on my purchase history and browsing behavior.
• User Story 7: (Won't-Have)
As a customer, the system won't display social media integration features
on the product pages.
• User Story 8: (Won't-Have)
As an administrator, the system won't include a feature for sending push
notifications to customers.
~Mohit Budhiraja

5. Kano Method
The Kano Model is used to prioritize features based on customer satisfaction and their level of expectation.
• User Story 1: (Basic Needs)
As a customer, I want a search functionality that allows me to
quickly find products based on keywords and filters.
• User Story 2: (Basic Needs)
As a customer, I want a secure and seamless checkout process to
ensure my transactions are safe and straightforward.
• User Story 3: (Performance Needs)
As a customer, I want the website to load quickly, providing a
smooth and responsive browsing experience.
• User Story 4: (Performance Needs)
As a customer, I want an intuitive navigation system that helps me
easily explore different product categories.
• User Story 5: (Excitement Needs)
As a customer, I would love a personalized dashboard that
recommends products based on my preferences and purchase
history.
• User Story 6: (Excitement Needs)
As a customer, I would appreciate a loyalty program that rewards me
for frequent purchases and provides exclusive offers.
• User Story 7: (Indifferent Needs)
As a customer, I'm indifferent to having an animated welcome page
when I log in; it doesn't significantly impact my experience.
• User Story 8: (Reverse Needs)
As a customer, I don't want intrusive pop-up ads that disrupt my
browsing experience.
~Mohit Budhiraja

6. High, Medium & Low(HML)
The High, Medium, Low (HML) prioritization technique is a simple method where user stories are categorized
based on their priority.
• User Story 1: (High Priority)
As a customer, I want a responsive mobile interface to easily
browse and make purchases from my smartphone.
• User Story 2: (High Priority)
As a customer, I want a secure payment gateway integrated into
the checkout process for safe transactions.
• User Story 3: (Medium Priority)
As a customer, I want an option to save items to my wishlist for
future purchases.
• User Story 4: (Medium Priority)
As a customer, I want to receive email notifications for order
confirmations and shipping updates.
• User Story 5: (Low Priority)
As a customer, I want a virtual assistant for real-time product
recommendations while browsing the website.
• User Story 6: (Low Priority)
As a customer, I want the option to customize the color theme of the
website for a personalized experience.
~Mohit Budhiraja

7. Relative Prioritization Technique
Relative prioritization involves comparing user stories against each other to determine their relative importance. In this method,
the team assigns a priority order based on the perceived importance of one user story compared to another.
• User Story 1:
As a user, I want a search functionality to quickly find products on
the website.
• User Story 2:
As a user, I want a user-friendly checkout process for a seamless
purchasing experience.
• User Story 3:
As a user, I want a personalized recommendation system to
discover new products based on my preferences.
• User Story 4:
As a user, I want the option to track my order and receive real-time
updates on its status.
• User Story 5:
As a user, I want a comprehensive user profile to manage my account
information and preferences.
~Mohit Budhiraja

8. Bubble Sort Technique
Bubble sort is a simple sorting algorithm that repeatedly steps through the list, compares adjacent elements, and swaps them if
they are in the wrong order. In the context of user story prioritization using bubble sort, the team iteratively compares pairs of
user stories and swaps their positions based on priority.
• User Story 1:
As a user, I want a search functionality to quickly find products on
the website.
• User Story 2:
As a user, I want a user-friendly checkout process for a seamless
purchasing experience.
• User Story 3:
As a user, I want a personalized recommendation system to
discover new products based on my preferences.
• User Story 4:
As a user, I want the option to track my order and receive real-time
updates on its status.
• User Story 5:
As a user, I want a comprehensive user profile to manage my account
information and preferences.
~Mohit Budhiraja

9. Story MappingTechnique
Story mapping is a technique used to visualize and prioritize user stories based on their importance and
dependencies. It helps create a holistic view of the product backlog.
• Goal: Create a user-friendly e-commerce platform for online shopping.
• Backlog Items:
1. Header Section: As a user, I want a navigation menu for easy
access to product categories., As a user, I want a search
bar to quickly find products.
2. Product Browsing: As a user, I want to see featured products on the
homepage., As a user, I want to filter products by category., As a user,
I want to sort products based on price.
3. Product Details: As a user, I want to view detailed product
descriptions., As a user, I want to see product reviews and ratings.
4. Shopping Cart: As a user, I want to add products to my shopping cart.,
As a user, I want to view and edit my shopping cart.
5. Checkout: As a user, I want a secure and easy-to-use checkout
process., As a user, I want to choose different payment options.
6. User Account: As a user, I want to create an account for personalized
recommendations. As a user, I want to track my order history.
• Story Mapping:
1. Top Horizontal Axis (Activities): Header Section, Product Browsing,
Product Details, Shopping Cart, Checkout, User Account
2. Left Vertical Axis (User Journey):
• Step 1: Homepage Navigation, Navigation menu, Search bar
• Step 2: Exploring Products , Featured products, Category filters, Price
sorting,
• Step 3: Product Details , Detailed descriptions, Reviews and ratings
• Step 4: Shopping , Add to cart, View/edit cart
• Step 5: Checkout ,Secure checkout, Payment options
• Step 6: User Account: Account creation, Order history tracking
~Mohit Budhiraja

10. Business Value and Complexity (BVAC)
technique
The Business Value and Complexity (BVAC) technique is a prioritization method that considers both the
business value of a user story and its complexity to implement.
• Feature: Search Bar :
• User Story 1: Basic Search : Business Value: 8 , Complexity: 5
• User Story 2: Advanced Filters: Business Value: 5, Complexity: 8
• Feature: Product Recommendations
• User Story 3: Personalized Recommendations: Business Value: 9,
Complexity: 7
• User Story 4: Trending Products: Business Value: 6, Complexity: 4
• Feature: Secure Checkout
• User Story 5: Multi-step Checkout Process: Business Value: 8,Complexity: 6
• User Story 6: Two-Factor Authentication: Business Value: 7, Complexity: 9
• Feature: User Account Management
• User Story 7: Order History Tracking: Business Value: 8, Complexity: 5
• User Story 8: Social Media Login Integration” Business Value: 6, Complexity:
7
~Mohit Budhiraja

11. Impact vs effort matrix technique
The Business Value and Complexity (BVAC) technique is a prioritization method that considers both the
business value of a user story and its complexity to implement.
• Feature: Search Bar
• User Story 1: Basic Search: Impact: Medium, Effort: Low
• User Story 2: Advanced Filters: Impact: High, Effort: Medium
• Feature: Product Recommendations
• User Story 3: Personalized Recommendations: Impact: High, Effort: Medium
• User Story 4: Trending Products: Impact: Medium, Effort: Low
• Feature: Secure Checkout
• User Story 5: Multi-step Checkout Process: Impact: High, Effort: High
• User Story 6: Two-Factor Authentication: Impact: Medium, Effort: Medium
• Feature: User Account Management
• User Story 7: Order History Tracking: Impact: Medium, Effort: Low
• User Story 8: Social Media Login Integration: Impact: Low, Effort: Low
~Mohit Budhiraja

12. Risk Based Prioritization Tenique
Risk-based prioritization involves assessing user stories based on potential risks and prioritizing them
accordingly. Here's an example for a software development project:
1. Feature: Payment Gateway Integration
1. User Story 1: Integration with New Payment Provider
1. Risk: High (due to lack of experience with the new provider)
2. User Story 2: Upgrade Existing Payment Integration
1. Risk: Medium (existing integration may have dependencies)
2. Feature: User Authentication
1. User Story 3: Implement Two-Factor Authentication (2FA)
1. Risk: High (security implications)
2. User Story 4: Password Recovery Mechanism
1. Risk: Low (commonly implemented, less complexity)
3. Feature: Data Migration
1. User Story 5: Migrate User Data to a New Database
1. Risk: High (potential data loss or corruption)
2. User Story 6: Data Validation and Integrity Checks
1. Risk: Medium (ensuring data accuracy during migration)
4. Feature: Reporting Module
1. User Story 7: Generate Custom Reports
1. Risk: Medium (complexity in report generation logic)
2. User Story 8: Export Reports to Various Formats
1. Risk: Low (standard functionality)
• Risk-Based Prioritization:
• High Risk User Stories (Priority 1):
• User Story 1: Integration with New Payment Provider
• User Story 3: Implement Two-Factor Authentication (2FA)
• User Story 5: Migrate User Data to a New Database
• Medium Risk User Stories (Priority 2):
• User Story 2: Upgrade Existing Payment Integration
• User Story 4: Password Recovery Mechanism
• User Story 6: Data Validation and Integrity Checks
• User Story 7: Generate Custom Reports
• Low Risk User Stories (Priority 3):
• User Story 8: Export Reports to Various Formats
~Mohit Budhiraja

13. Thank You!
~Mohit Budhiraja