how to build a sprint if Im using both stories and tasks

[‪gilad maharal‬‏]

hi there

Im, as the PM writing stories to the backlog

the CTO is breaking each story into tasks

what will be the right way to build the sprint? attaching only the related tasks? or attach the story as well?

Thank you

[Ollie Guan]

Hi @‪gilad maharal‬‏ ,

In Scrum, I think that all user stories, tasks, defects, etc. belong to the Backlog.

We need to consider the business priority, technical debt, complexity, market feedback and other factors to prioritize these Backlogs.

Put these backlog into a sprint according to the order of priority and the velocity of the scrum team.

[‪gilad maharal‬‏]

Hi

@Ollie Guan

, thanks

not sure I understand your answer

My problem is not prioritizing between the stories and the tasks, but to understand what to do with the stories - if all the tasks that break from this story is already related to the sprint

should I archive this story? 

[Jimmy Seddon]

Hi @‪gilad maharal‬‏,

How is your company organizing your sprint boards? By that I mean are you using Stories as Swimlanes?

That is how we have been organzing things so you would want the story included in the sprint, and then you are able to see at a glance how many task are in To Do, In Progress or Done on a per story basis which can help you more easily see how the team is doing as far as completing the sprint.

-James

[Ollie Guan]

Hi @‪gilad maharal‬‏ ,

I'm not sure if I understand what you mean correctly. As a PM, you are writing user stories and putting them into the Backlog.

And your CTO responsible for splitting these user stories into sub-tasks?

In Jira, subtasks belong to the user story. When you put the user story into a sprint, these subtasks will enter the sprint together.

Hope it helps.

[‪gilad maharal‬‏]

Thanks! that do explain the way to do so

Gilad