We have recently started using Agile methodology implemented with Jira. We are struggling to decide how best to arrange Sprints, Epics, Stories, etc when working across different departments.

For example, let's say we're going to make 'Feature A'.

At a basic level, sufficient for this question, 'Feature A' needs to go through four departments/stages:

1. UX & Wireframing
2. Design
3. Back-end Development
4. Front-end Development

We are a small company working on a single Saas Product, with 2 or 3 individuals in each of the above teams.

What are the best practices for organising this in Jira / Sprint Planning?

Do we give the 4 stages their own epics, or do we give them their own stories/tasks within shared epic, or something else (like separate themes, initiatives, or even projects)?

I know there is element of "It depends" and subjective preference, but am hoping there are some opiniated "default" suggestions that might guide us on what is going to work best for most situations.

One motivation for making this decision early is generating informative product roadmaps for stakeholders that show UX, Design, and Development all in one place, that can be generated from Jira, rather than manipulated separately.

I'd really appreciate your comments and suggestions. Let me know if you need any clarification.

We have recently started using Agile methodology implemented with Jira. We are struggling to decide how best to arrange Sprints, Epics, Stories, etc when working across different departments.

For example, let's say we're going to make 'Feature A'.

At a basic level, sufficient for this question, 'Feature A' needs to go through four departments/stages:

1. UX & Wireframing
2. Design
3. Back-end Development
4. Front-end Development

We are a small company working on a single Saas Product, with 2 or 3 individuals in each of the above teams.

Do we give the 4 stages their own epics, or do we give them their own stories/tasks within shared epic, or something else (like separate themes, initiatives, or even projects)?

I know there is element of "It depends" and subjective preference, but am hoping there are some opiniated "default" suggestions that might guide us on what is going to work best for most situations.

One motivation for making this decision early is generating informative product roadmaps for stakeholders that show UX, Design, and Development all in one place, that can be generated from Jira, rather than manipulated separately.

I'd really appreciate your comments and suggestions. Let me know if you need any clarification.

We have recently started using Agile methodology implemented with Jira. We are struggling to decide how best to arrange Sprints, Epics, Stories, etc when working across different departments.

For example, let's say we're going to make 'Feature A'.

At a basic level, sufficient for this question, 'Feature A' needs to go through four departments/stages:

1. UX & Wireframing
2. Design
3. Back-end Development
4. Front-end Development

We are a small company working on a single Saas Product, with 2 or 3 individuals in each of the above teams.

What are the best practices for organising this in Jira / Sprint Planning?

Do we give the 4 stages their own epics, or do we give them their own stories/tasks within shared epic, or something else (like separate themes, initiatives, or even projects)?

I know there is element of "It depends" and subjective preference, but am hoping there are some opiniated "default" suggestions that might guide us on what is going to work best for most situations.

I'd really appreciate your comments and suggestions. Let me know if you need any clarification.

We have recently started using Agile methodology implemented with Jira. We are struggling to decide how best to arrange Sprints, Epics, Stories, etc when working across different departments.

For example, let's say we're going to make 'Feature A'.

At a basic level, sufficient for this question, 'Feature A' needs to go through four departments/stages:

1. UX & Wireframing
2. Design
3. Back-end Development
4. Front-end Development

We are a small company working on a single Saas Product, with 2 or 3 individuals in each of the above teams.

What are the best practices for organising this in Jira / Sprint Planning?

Do we give the 4 stages their own epics, or do we give them their own stories/tasks within shared epic, or something else (like separate themes, initiatives, or even projects)?

I know there is element of "It depends" and subjective preference, but am hoping there are some opiniated "default" suggestions that might guide us on what is going to work best for most situations.

One motivation for making this decision early is generating informative product roadmaps for stakeholders that show UX, Design, and Development all in one place, that can be generated from Jira, rather than manipulated separately.

I'd really appreciate your comments and suggestions. Let me know if you need any clarification.