Creating user stories can be challenging and time-consuming. I found out that ChatGPT if appropriately used, can generate some good content and save up a lot of time.
It works best if you provide enough information, like putting in the product description document and asking to generate user stories out of it with acceptance criteria.
Another option is to put in the user experience journey steps and ask to generate the user stories.
If you have the epics, list them too; it will provide much better content.
Example:
"The project is a development of an online shop. The high-level features(user activities) include products, Orders, shipping, tracking, and recommendations. User personas are Customer, Product Manager, and Shipper. Now I have defined these user tasks: the Customer should be able to search for a product, order product, receive product, return product; the Product manager should be able to manage inventory and order inventory; the Shipper should be able to receive order, ship order, receive returns. Based on this information, can you create epics from the user tasks and create user stories with acceptance criteria out of those epics?"
Here are the epics
Epic1 - Customer searching for a product, Epic 2 - product manager managing the products on the website (adding/deleting, etc.), epic 3 - Customer ordering and buying products, epic 4 - product manager ordering inventory, epic 5 - Shipper receiving the order, epic 6- Shipper shipping the order, epic 7 - Customer receiving the product, epic 8 - Customer returning the product, epic 9 - Shipper receiving returns, epic 10 - Customer getting recommendations on products |
And here is the result:
Epic 1: Customer Searching for Product
User Story 1: Basic Product Search As a Customer, I want to search for a product by its name or description so that I can find the product I want easily. Acceptance Criteria: The system should allow me to enter search terms in a search bar. The system should display a list of products matching the search terms. The system should allow me to filter the results by price, category, or rating. The system should allow me to sort the results by relevance, price, or rating.
User Story 2: Advanced Product Search As a Customer, I want to search for a product using advanced filters like color, size, material, brand, etc., so that I can find the exact product I want. Acceptance Criteria: The system should allow me to select advanced search options like color, size, material, brand, etc. The system should display a list of products matching the selected search options. The system should allow me to further refine the search by price, category, or rating. The system should allow me to sort the results by relevance, price, or rating.
Epic 2: Product Manager Managing the Products on the Website
User Story 1: Add New Product As a Product Manager, I want to add a new product to the website, so that it can be available for purchase. Acceptance Criteria: The system should allow me to enter product details like name, description, category, price, etc. The system should allow me to upload product images and videos. The system should verify that all required fields are filled in. The system should display the new product on the website.
User Story 2: Delete Product As a Product Manager, I want to delete a product from the website, so that it is no longer available for purchase. Acceptance Criteria: The system should allow me to select the product that I want to delete. The system should confirm that I want to delete the product. The system should remove the product from the website.
Epic 3: Customer Ordering and Buying Product
User Story 1: Place Order
As a Customer, I want to place an order for a product, so that I can see my ordered products in my shopping basket. Acceptance Criteria: The system should allow me to add products to my shopping basket User should be able to place multiple orders at once. The products should show up in the basket with name, description, price, quantity. The system should calculate the total price, including taxes and shipping fees. The system should allow me to delete a product from the basket.
User Story 2: Buy Product Using Single Payment Option As a Customer, I want to buy a product using a single payment option like credit card, so that I can complete my purchase quickly and easily. Acceptance Criteria: The system should allow me to add a product to my cart. The system should allow me to select the payment option at checkout. The system should display the total cost, including any taxes and shipping fees. The system should process the payment securely and notify me of the successful transaction. The system should update the order status to "Processing" and provide an estimated delivery date.
User Story 3: Buy Product Using Multiple Payment Options As a Customer, I want to buy a product using multiple payment options like PayPal, Stripe, American Express, Google Pay, Apple Pay, etc., so that I can choose the option that is most convenient for me. Acceptance Criteria: The system should allow me to add a product to my cart. The system should display a list of available payment options at checkout. The system should allow me to select the payment option that I want to use. The system should display the total cost, including any taxes and shipping fees. The system should redirect me to the selected payment option's website or interface for payment processing. The system should process the payment securely and notify me of the successful transaction. The system should update the order status to "Processing" and provide an estimated delivery date.
User Story 4: Track Order Status
As a Customer, I want to track the status of my order, so that I know when to expect delivery. Acceptance Criteria: The system should display the current status of my order (e.g., Processing, Shipped, Delivered, Returned). The system should provide an estimated delivery date. The system should allow me to view the order details like product name, quantity, price, shipping address, etc. The system should update the status and estimated delivery date as the order progresses.
Epic 4: Product Manager Ordering Inventory
User Story 1: Order Inventory As a Product Manager, I want to order inventory for a product, so that it is available for purchase. Acceptance Criteria: The system should allow me to select the product for which I want to order inventory. The system should allow me to enter the quantity of inventory that I want to order. The system should display the cost of the inventory order. The system should process the payment for the inventory order securely and notify me of the successful transaction. The system should update the inventory status for the selected product.
User Story 2: View Inventory Status As a Product Manager, I want to view the inventory status for a product, so that I can manage the inventory effectively. Acceptance Criteria: The system should display the current inventory level for the product. The system should allow me to set a minimum and maximum inventory level for the product. The system should alert me if the inventory level falls below the minimum level. The system should provide a report of inventory levels for all products.
Epic 5: Shipper Receiving the Order
User Story 1: Receive Order Details As a Shipper, I want to receive the details of an order, so that I can prepare it for shipment. Acceptance Criteria: The system should display the order details like product name, quantity, price, shipping address, etc. The system should provide a packing slip for the order. The system should allow me to mark the order as ready for shipment.
User Story 2: View Order History As a Shipper, I want to view the history of orders that I have shipped, so that I can track my performance. Acceptance Criteria: The system should display a list of all orders that I have shipped. The system should show the order details like product name, quantity, price, shipping address, etc. The system should provide the delivery date and time for the orders. The system should allow me to export the order history as a report.
Epic 6: Shipper Shipping the Order
User Story 1: Ship Order As a Shipper, I want to ship an order, so that it is delivered to the Customer on time. Acceptance Criteria: The system should display the order details like product name, quantity, price, shipping address, etc. The system should allow me to select a shipping carrier and method. The system should provide the shipping label and tracking number for the order. The system should notify the Customer of the shipment and provide the tracking information.
User Story 2: Update Order Status As a Shipper, I want to update the status of an order, so that the Customer can track its progress. Acceptance Criteria: The system should allow me to update the order status (e.g., Shipped, Out for Delivery, Delivered, Returned). The system should notify the Customer of the updated status and estimated delivery date. The system should allow the Customer to view the updated status and tracking information.
Epic 7: Customer Receiving Product
User Story 1: Receive Product As a Customer, I want to receive the product that I ordered, so that I can use it. Acceptance Criteria: The system should notify me when the product is shipped and provide the tracking information. The system should provide an estimated delivery date. The system should notify me when the product is delivered. The system should allow me to confirm receipt of the product and provide feedback.
User Story 2: View Order History As a Customer, I want to view my order history, so that I can track my purchases. Acceptance Criteria: The system should display a list of all orders that I have placed. The system should show the order details like product name, quantity, price, shipping address, etc. The system should provide the delivery date and time for the orders. The system should allow me to export the order history as a report.
Epic 8: Customer Returning the Product
User Story 1: Request Product Return As a Customer, I want to request a return for a product, so that I can receive a refund or exchange. Acceptance Criteria: The system should allow me to select the reason for the return (e.g., damaged, wrong product, not satisfied). The system should provide a return shipping label and instructions. The system should notify the Shipper of the return request.
User Story 2: Track Return Status As a Customer, I want to track the status of my product return, so that I can know when to expect my refund or exchange. Acceptance Criteria: The system should display the status of the return (e.g., Return Requested, Return Shipped, Refund Processed, Exchange Processed). The system should provide an estimated date for the refund or exchange. The system should notify me when the refund or exchange is processed.
Epic 9: Shipper Receiving Returns
User Story 1: Receive Return Details As a Shipper, I want to receive the details of a return, so that I can process it. Acceptance Criteria: The system should display the return details like product name, quantity, reason for return, etc. The system should allow me to update the return status (e.g., Return Received, Refund Processed, Exchange Processed). The system should notify the Customer of the updated status.
User Story 2: View Return History As a Shipper, I want to view the history of returns that I have processed, so that I can track my performance. Acceptance Criteria: The system should display a list of all returns that I have processed. The system should show the return details like product name, quantity, reason for return, etc. The system should provide the refund or exchange date and time for the returns. The system should allow me to export the return history as a report.
Epic 10: Customer Getting Recommendations on Products
User Story 1: View Recommended Products As a Customer, I want to view products recommended by the website, so that I can discover new products. Acceptance Criteria: The system should display a list of recommended products based on my purchase history, search history, and other data. The system should show the product details like name, price, and image. The system should allow me to filter the recommended products by category, price range, and other criteria.
User Story 2: Rate Recommended Products As a Customer, I want to rate the recommended products, so that the website can improve its recommendations. Acceptance Criteria: The system should allow me to rate the recommended products on a scale of 1 to 5 stars. The system should use my ratings to improve the recommendations for me and other customers. |
This is not 100% accurate or complete, but it can help you to experiment, learn, and gain new perspectives.
Some people say that it takes a lot of time to optimize those user stories afterward, and it is much faster to write those themselves. That is true for experienced people who have been doing this for years.
Still, we want to make our lives easier, right? I found out that if you write your request correctly to the ChatGPT, it provides great help and support.
Remember:
We should never move away from customers, and should never replace it with anything else. That's the core of success and agility!
I am just looking and experimenting with these tools to see where they can accelerate or support us in our way.
Look at it as a side tool, not a main resource.
Don't share confidential or sensitive info.
Even when you get the info from customers usually you need to write it in a comprehensive way with acceptance criterias in your Backlog. Use it for experimenting, testing and learning.
Contexts are always different. Be open.
That's where I found it useful. That's it, that's all. We should be open trying different tools and making our choices.
Use it wisely, and it will serve you for good.
I hope you found it helpful!
===
Whenever you're ready, there are 4 other ways I can help you:
1. Follow me on Linkedin to get daily tips on #agile, #team coaching, #scrum master growth, #agile leadership, #agilecoaching #culture
2. 💥Join our free community to taste our recipes to help you grow as an agilist and help your teams improve performance!
3. Join the Ultimate Team Performance Toolkit: a compound collection of 30 exercises, templates and strategies to measure and improve team dynamics and performance.
4. Join the Agile Team Coaching Program: A targeted coaching- facilitation system to help Scrum Masters and Agile Leaders to identify team hidden obstacles and turn those into a growth plan in 30-60 days.