Business Analyst Community & Resources | Modern Analyst

Career Forums

Modern Analyst Forums Business and Sy... Agile Analysis ... Best practices for writing user stories that extend a product

12/7/2017 9:28 AM

	JJonas
4 posts

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

12/9/2017 8:51 PM

	Kimbo
456 posts

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

12/19/2017 7:17 AM

	JJonas
4 posts

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

4/9/2018 10:21 AM

	Carolcz
3 posts

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 ###.