The scenario is something like this. A user story goes through various stages like
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.
Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs