How to organize web and app development when it has duplicate tasks

[Rafael Alencar]

Hi!

We have a team for web and mobile development. Sometimes both teams needs to perform the same tasks and we end up duplicating epics, stories and tasks to achieve this.

Is there a recommended strategy to do this kind of organization? It feels wrong and not productive to duplicate tasks.

Example:

[EPIC] Buyer Web

[Story] Add products to cart

[EPIC] Buyer Mobile

[Story] Add products to cart

Even if we had a single Epic and Story we'd need to duplicate tasks.

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

I think there is a slight mistake in your thinking here.  You don't have "duplicate tasks", you have two different tasks that are similar, and probably linked, but because they are for two teams, they are not duplicates.

In your case, you seem to be misusing Epics - why is there one for Web and one for Mobile?  Sure you've just got:

[Epic] Buyer

[Story] Web team needs to add something

[Story] Mobile team needs to add something

[Rafael Alencar]

Hi, Nic.

Thanks for your answer.

I agree with you about this way of seeing.
About the misuse of Epics, we follow this way because we needed to track the progress of web and app separately. Is there a better way?

[Nic Brough -Adaptavist-]

If you need to track them separately, why are you grouping them together?

Are your Epics truly Epics?  If the work is to be tracked separately, then why are you using something intended to group together everything that gets you to a specific objective?

In this case, there's a really simple answer though - do your tracking at the story level.  You've got one bucket for web and another for app, so just look at them, the Epic is irrelevant for tracking individual bits of the objective.

[G subramanyam]

Hi @Rafael Alencar welcome to the Atlassian community.

[Rafael Alencar]

Hi @G subramanyam

Thanks.