How does Atlassian do "dogfooding" for delivery workflow using Jira and Jira Plans?

[Harvindar Singh]

How does Atlassian use Jira and Jira Plans for delivery workflow? For a significant piece of delivery work that involves multiple teams, how is the workflow organised?

For example:

• Each team has its own Jira Project and Scrum board (assume the organisation aligns on sprint duration/dates)
• The program of work uses Jira Plans to tie it all together
• The program creates Epics that are product increments that deliver every quarter
• Each team plan out their work creating Jira issue types and link them to the program Epic (i.e. parent link)

[Stephen_Lugton · Accepted solution]

Hi @Harvindar Singh 

The Atlassian product suite allows you to use workflows how you want to use them, so the examples you've given are all a valid way of using Jira. You don't need to align on sprint duration/dates, in fact I run two teams that both use 2 week sprints that are offset by a week.

Using Plans also you to use custom hierarchy levels (https://support.atlassian.com/jira-software-cloud/docs/configure-custom-hierarchy-levels-in-advanced-roadmaps/) so we have 2 additional levels above epic; theme and initiative, so we tend to use initiatives for the product increments at the program level and epics (as children of the initiatives) at team level.

[Harvindar Singh]

Thanks @Stephen_Lugton 

I found below link in the Jira docs where its using Odyssey & Legend corresponding to Theme & Initiative in relation to your answer.

https://support.atlassian.com/jira-software-cloud/docs/how-veronica-uses-advanced-roadmaps-cross-project-planning/