Setting up multiple projects for 1 team.

kalle_hmw67m

Hey, 

We have been working with Jira (+Confluence) for some time now in our product development teams, using Jira software. We are no in the process of starting using Jira in the rest of the organisation including our creative team. 

Our creative team works as an agency within the organisation, working on projects and ad-hoc tasks for other teams.

 

First 2 questions - Jira work /service management vs. Jira software:

- We believe that the best option for the creative team (and the rest of the "non-technical" teams in the organisation) is to work with Jira Work or Service management, instead of Jira software, as they are not working with development. Is there any good arguments against this or do you agree?

- We would like to set it up as team managed projects as we dont want to have a Jira admin that is responsible for administrating projects. Instead, we are working with self organised teams, and we want each team to be free and responsible for administrating their own project. Is this a good idea or is do you think its better to set it up as company managed projects?

Our need - How to set up the creative team with multiple projects:

1. Optimally we want be able to see all issues from all projects in 1 board view, so that they dont need to look at a different board for each project. Eg. The creative team,  are working on 10 issues in Project A, 10 issues in Project B, and 10 issues in Project C at the same time. They want to be able to see all of those issues in one board at the same time. 

2. We also need to be able to track time spent on each project for budget tracking purposes. 

Thanks in advance!

 

Jack Brickey

1. Generally JWM works well for non-technical teams and it is getting some nice features of late and more coming. Here are reasons to go with JSW: the team wants to use agile sprints, the team wants to leverage fully configurable boards. However, the last one seems to be of declining interest with the continued evolution of JWM. JSM only makes since if the team will be servicing a customer base where customers open tickets the need attended to. Examples of JSMm IT, HR, Facilities.
2. TMP vs. CMP... this is a tough one for me to be honest. I almost exclusively use CMP, partly because I am so comfortable with it but also because it is much more flexible and configurable. TMP has gotten much much better and provide some nice features. It feels like TMP will work well for your teams as you have played out. However, it is really hard for anyone to know for sure. If you feel comfortable TMP, go with it and if you need to consider CMP in the future, then you can either move the issues over into the new CMP project, or you can create a new project and archive the old TMP.
3. Well I might change my mind on #2 given you want a single board for multiple projects. While you can create a single kanban board and apply it to multiple TMP projects it can get messy. If this is an important requirement, I would really think about CNP personally.
4. Time tracking can be added to any project.