nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Multiple developers team. Who owns a story during coding? Best practice or experience needed.

Raymond Barnell

I have three teams working together. Each team has 3 (front, back, DB) developers, 1 QA.

Who owns a story during development, given 3 developers are all domain-specific and they cannot influence on other developers work priority.

Your experience or suggestions, please.

Thanks in advance!

Accepted answers

Peter DeWitt

@Raymond Barnell , a few ideas:

1. Think about bumping the story to an Epic (if able) and then creating stories for each piece of work.

2. You could also just have three separate stories, use issue linking to build the relatability and then tie them all together through a version.

3. Maybe even a single story (owned by the product manager or left blank) and then each team could hang a subtask or two off the story for their specific body/s of work.

Experiment a little with different approaches and see what work with for you. gl. -pjd

All comments

Peter DeWitt

@Raymond Barnell , a few ideas:

1. Think about bumping the story to an Epic (if able) and then creating stories for each piece of work.

2. You could also just have three separate stories, use issue linking to build the relatability and then tie them all together through a version.

3. Maybe even a single story (owned by the product manager or left blank) and then each team could hang a subtask or two off the story for their specific body/s of work.

Experiment a little with different approaches and see what work with for you. gl. -pjd

John Funk

Hi Raymond - Welcome to the Atlassian Community!

Are there multiple developers working on a single story at the same time? If so, then maybe the story is too big and needs to be broken up into individual tasks or individual stories. You could then group them together in one of the ways that Peter suggests.

If they are not working on the same card at the same time, then you might want to create additional statuses in your workflow to show the card has moved from one activity to the next. Each movement gets the card assigned to a new user.

Raymond Barnell

Thinking about PO ownership as well. Will give a try, thanks!

Raymond Barnell

thanks, John! Will consider workflow change as well.

John Funk

Let me know your final solution - would be interested in how you implemented it. :-)

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server

story