Jira Project Definition

[Nikki Hylton]

Hi Atlassian Community!

Our team has decided to use projects to manage larger initiatives for better visibility on roadmaps/plans. If it's a smaller feature request with minimal LOE, we instead use an epic under a "container" project for ongoing maintenance/bugs/small initiatives.

The question frequently comes up - should this be created as a project or epic in Jira? 

We're trying to create a standard criteria to answer this question rather than having to discuss each request.  Maybe something like if we expect the request to take X development hours or more, it should be a new project; otherwise an epic in the existing container project.

Has anyone else run into this issue and how do you make the decision? We're hoping to standardize the decision making process rather than discussing each on a case-by-case basis.

Thanks in advance,

Nikki

[Dave Mathijs]

Hi @Nikki Hylton There is no right or wrong answer in my opinion.

More important is that you agree on a policy within your organization for the definition of a project.

A project does not necessarily equal a software/business project in Jira.

Some teams have a Jira software/business project and define their projects as Epics with Task/Story and Sub-task as breakdown.

It all comes down to the definition of a project that works for you/your team/your organization.

[Nikki Hylton]

Thank you @Dave Mathijs ! I agree - mostly curious if others in similar situations have set standards/criteria that might help us come to a decision. Appreciate your feedback!