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 9: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 8:51 PM
User is offline Kimbo
438 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 7: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 10: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

Digvijaybook
Digvijaybook
Analytics is the future of the business industry. Businesses and organizations today run on data and its interpretation. Its correct evaluation is the fundamental key to success. And business analysts are the guides to it. It is a very prosperous industry and has a lot of potential for talented people. To even qualify, you require more than just...
1 Responses
Samuel02
Samuel02
With the advent of modern-day cloud infrastructure, many business-critical applications like databases, ERPs, Marketing applications have all moved to the cloud. With this, most of the business-critical data now reside in the cloud. Now that all the business data resides on the cloud, companies need a data warehouse that can seamlessly store the da...
0 Responses
BPM_online
BPM_online
Bpm'online, a global business software company leading in the space of low-code, process automation, and CRM, will be soon announcing their new company name. The new name will be launched in the sky via a breathtaking skydiving performance involving 160 bpm’online employees, including the CEO. The new name of bpm’online is to be fo...
0 Responses




Latest Articles

Copyright 2006-2019 by Modern Analyst Media LLC