Jira implementation - but confused about projects.

[Jack Black]

We don’t have the budget to hire a partner or anyone for the implementation.

Here’s our setup. 45 scrum teams with 10-day sprints. We build an enterprise product using scrum, and release about 100 features (epics) every month. Our portfolio hierarchy will be Theme->Epic. And work items will be Story->Sub-tasks, and Defect->Sub-tasks. Epics, stories and defects have the monthly release version number assigned to it so it’s clear when they are delivered to customers. While an epic will be owned by one team, stories under it can be assigned to different teams.

Looking for recommendations on how to define Jira company-managed project(s) for my setup. Should the projects be scrum teams? Or monthly releases? Or epics? Or themes? What would be the pros and cons?

We would like to see status of an entire monthly release that should show all the epics and their progress. Also, teams would like to see how they are doing within a sprint. We want to be able to monitor, report and analyze an entire monthly release or an individual epic or a team or a sprint.

[Sunny Ape]

Hello @Jack Black 

There are no absolute, specific solutions or answers to such broad, open scope, highly subjective questions, only countless opinions, each of which will be different to the other.

Honestly, if your company has 45 scrum teams, you are more than big enough to either:

1. Engage an Atlassian partner as a consultant to evaluate your company's requirements and to advise on the best solution; or
2. Hire a permanent Agile Practice Manager / Scrum Master with extensive Jira management and configuration skills.

Configuring Jira to meet an organisation's business requirements and align with their work practices isn't an expense, it's an investment.