Iterative Story

[Manu Sekhar S]

We have stories which are iteratively refined over multiple sprints. How can we handle it in JIRA.

Scenario:

Developer completed story demonstrated to customer

Customer review the product and share review feedback on same story.

Developer continue work on same story to include review feedback received on the story. 

This process of refinement continuing in multiple sprint as iterative refinement for a story. 

How can we we handle such story in JIRA, Is it a spike or EPIC

[Mac S]

Hi @Manu Sekhar S ,

It will be considered as a Story (not Epic) only and each of the task mentioned e.g. dev completion, customer feedback, story update etc. should be handled using task or sub-task linked to the story. While sub-tasks can be created within story, Task will have to be created independently and linked with the story.

In order to manage development of Story, you will have to add the task/sub-tasks (not Story itself) in different Sprints as per your priority. Story will be closed only when all sub-tasks will get completed.

Hope it will help.

Regards.

[Bill Sheboy]

Hi @Manu Sekhar S  -- Welcome to the Atlassian Community!

What problem are you trying to solve with your request?

Rather than figure out ways to carry work over, sprint to sprint, I wonder:

• How might the team split down valuable stories so each can be started and completed in a sprint?
• How might the team improve refinement (before the sprint starts) and improve feedback with customers (after the sprint starts) to finish within the sprint time-frame?
• If the above ideas don't help, how well does Scrum fit the way your team works, and might Kanban be a better fit?

Please consider discussing these ideas with your team and customers.  Thanks!

Best regards,

Bill