User stories management

[Satpal Kaur]

The scenario is something like this. A user story goes through various stages like

• Analysis and writing user story details
• Designing solution for implementation
• Coding (and there could be various parts of coding which could be big pieces of work which may not be completed in one sprint and requires to be run in sequence tasks
• Manual Testing
• Automation Testing etc.

In ideal scenarios, all these activities should be defined as Tasks in Jira as part of user story. But if we implement them as tasks, a user story may not get finished in one sprint and spill over subsequent sprints. If we let user story spill over multiple sprints, we may  loose sprint velocity by having incomplete / spilled over user stories. Currently team is defining multiple user stories for same piece of user value to be delivered to the user. Keeping this in mind, there are different user stories for coding, testing, designing for same piece of "User Value" being delivered. To put it in different words, there are number of user stories pertaining each tasks in user story life cycle. Therefore there may be multiple user stories for same piece of user requirement.

[Satpal Kaur]

I would like to know if this is right implementation of user stories in Jira, to have multiple user stories for same user value.

[Jakub Pierzchała]

And your question is?