Best suggestion to set up methodology

Dave W_px0rxp

Greetings Brains Trust,

Our team are currently documenting the design requirements for how we will be using Jira Core for our business team task management and I was wanting to get some suggestions or feedback on the best way to structure our config?

Background:

We're a business improvement team that is also responsible for the Document QA system. We have BAU tasks such as document reviews and updates and well as GRC tasks for the department and managing the staff encouragement program.. On top of this we also have a large portion in working on business and process improvement projects/initiatives. We need to be able to report on the following;

• Details or tasks outstanding/inflight.
• Visibility on current and upcoming workload (based on estimates/sizes etc) for each team member
• Time of flight
• # of high level Requests from each area. (identified through a custom field)
• Number of lower level tasks (identified through a custom field)

My main question is, based on the reporting we require, which of the following hierarchies would you suggest? 

Option 1) Each top level area, is a separate project, with the Epics as the next level of reporting for each task? (this would entail custom reports which we don't have expert support to create)

or

Option 2) Having just one Project for the whole team, and then using Epics as the top level of task subject with each request being a task with it's sub-tasks?

 

Any suggestions or insight into what others have done would be greatly appreciated.

 

Petter Gonçalves

Hello @Dave W

Welcome to the Atlassian Community!

Taking a look at all the 5 features you would like to implement to achieve your goals, I believe that a Classic business project would be enough, supposing the "Time of flight" will also be added as a custom field.

About the hierarchy options you'll be using, the best way to determine the best approach would be by defining how you would like to report your results and progress on those issues. Explaining better:

1 - If you're planning to use different projects, you will be able to configure a single report for each top-level area, splitting the estimations of your team for each area you have separately.

2 - If you decide to group all issues together in the same project, you can have a global report considering all the issues of your team (all top-level areas). Additionally, you could define each top area you have based on the component field, although the report will consider a single global estimation for your team:

Organize work with components 

Let us know if you have any questions.