Project Selection For Teams

[muneet.bakshi]

As we start planning our move from RALLY into JIRA we need some input on selecting the type of projects we will need. Classic or NexGen? Here are the considerations:

1. Approximately 15 to 20 teams - Should we house everything in one project or have one per team.
2. If each team has a separate NEXT GEN project are we able to pull a report that incorporates data from all 15 to 20 projects? Key metrics that we are going to need are: Clycle Time, Work In Progress, and Throughput. Can we even do this in Net Gen projects? I only saw two reporting options.
3. Will we be able to move stories/EPICS from one NEXT GEN project to another?

[Emre Toptancı _OBSS_]

Hello @muneet.bakshi ,

Having all work in a single project is a big "NO NO NO".

I suggest you define your projects based on products, not teams. For your current case, the two options might look the same but it is important to make the distinction.

I personally define a software product as something that has its own codebase and is deployed separately. It might be as big as an entire ERP system or as small as a single .dll or .jar file, based on how you do things. Looking from this perspective, each of your teams might have many products, hence many Jira projects.

"Jira projects based on products" approach is an invesment for future since it accumulates the whole history of the product in a single Jira project and makes it possible to combine teams, break teams down or take product responsibility from one team to another.

Having said this, you can use classic or Next-Gen projects. I personally prefer classic projects as I feel like they give me greater control over what is going on.

The Kanban Board and Control Chart will give you some of the metrics you will need. The control chart is very useful but it does not allow you to work on individual issues.

If you are interested in a ready solution for better reporting and more control over the reports, our team at OBSS built Timepiece - Time in Status for Jira app for this need. The app produces reports much more detailed than the control chart and gives you much more control over the reports. It is available for Jira Server, Cloud and Data Center.

It also allows you to export your data or access it via REST.

Below are a few use case articles that explain how to calculate metrics like Lead Time, Cycle Time and Throughput, using Time in Status by OBSS.

https://dev.obss.com.tr/confluence/pages/viewpage.action?pageId=294982438

https://dev.obss.com.tr/confluence/pages/viewpage.action?pageId=303795348

EmreT

[muneet.bakshi]

I think I have figured out #3 which is a YES. Any takers for #1 and #2?

Thanks,