Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Agile Analysis ...  Best practices for writing user stories that extend a product
Previous Previous
 
Next Next
New Post 12/7/2017 7:28 AM
User is offline JJonas
4 posts
No Ranking


Best practices for writing user stories that extend a product 
Hello,

I recently created a few epics for a new project that is about extending one of our product for the needs of a customer.

The user stories I wrote explained what were the needs of the customer regardless whether they were already implemented or not in our product. Then I get some complaints from the developers as they were expecting the user stories to only contain what they need to implement.

My point was that it is important to capture all the expectations from the customer, and we still need to confirm to the customer that the product is working as expected, including the features that are supposed to be already implemented, so these already implemented features should be tested as well, to make sure there is e.g. no performance issues that happen with the particular use case of the customer.

As I am new to both business analyst and agile workflow, I would like to receive some feedback: what would be the best practices for this case, according to you?

Cheers,
Jonas
 
New Post 12/9/2017 6:51 PM
User is offline Kimbo
456 posts
5th Level Poster


Re: Best practices for writing user stories that extend a product 

Hi Jonas,

 

The existing features should already have been documented and included in regression testing. I'm with the developers on this, just create stories for the new features. 

 

If you want to create stories to document existing product features, do it as a separate exercise.

 

Kimbo

 
New Post 12/19/2017 5:17 AM
User is offline JJonas
4 posts
No Ranking


Re: Best practices for writing user stories that extend a product 

Hi Kimbo,

Thank you for your answer. I believe I will create user stories only for the new features as you suggested, while also describe in general terms what are the needs of the customer, so that the persons reading the epic can have an overview of the whole process, while having a good clarity about what the work to be done is about.

Jonas

 
New Post 4/9/2018 8:21 AM
User is offline Carolcz
3 posts
No Ranking


Re: Best practices for writing user stories that extend a product 
You can always refer back to previous information in the acceptance criteria... such as User must be able to perform previous functionality as per User story or Test Script ###.
 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Agile Analysis ...  Best practices for writing user stories that extend a product

Community Blog - Latest Posts

I have always loved cooking. I learned from my Grandma June and her kitchen was her sanctuary, a small, warm sunlit space filled with jars of spices, stacks of cookbooks, and the comforting smell of something always on the stove or baking in the oven. Grandma June was as great a cook as she was a teacher to me. She never followed a recipe “to...
Now, I know, I don’t know what kind of new intro BPO may require, but at least I can promise you upfront that I have something different to say about Business Process Outsourcing or simply BPO. What is it? This hasn't been a call center job or a sales job as we all think. It is a mammoth profile, and firms are grappling to ge...
Leveraging Blockchain Technology for Enhanced Data Security in Business Operations
In an age where data breaches and cyberattacks are becoming more frequent and sophisticated, businesses are searching for robust solutions to safeguard their data. Blockchain technology has emerged as a promising tool in this quest, offering a way to secure data with unparalleled reliability. Although initially known for powering cryptocurrencies l...

 






 

Copyright 2006-2025 by Modern Analyst Media LLC