@Garden16_ It all depends on what your process is for managing projects, how your team works on projects, how you define a project, etc.
An example one of my current teams works on enhancements and operational support for a single application. They receive requests through a JSM service desk and then catalog approved requests in a single project and use a Kanban board to organize their work. This allows them to track all the work that they have in their backlog and prioritize what will be worked on next. Since they just continually work to close requests out a Kanban works for this team as well as a single Jira Software Project.
I recently completed a large ERP implementation that had multiple teams that I was over. We ran 5 different Jira projects to organize work for the different teams and used all the projects to monitor and control work.
One of my other areas works on implementations and we run a separate project for each implementation. The teams for each implementation could share resources but the team members only have access to the projects that they are on. We are constantly closing out projects and creating new projects to move the work forward.
I also have a team that maintains multiple applications and supports implementations in their area. They have a single project for maintenance and operational work. They create new projects for each implementation and projects for large yearly maintenance exercises. This allows them to more easily track their work and understand where everything is at.
In all cases, the teams are always growing and improving their processes. Jira allows them to do this and they are able to structure the application to meet their needs.
If you would like to share how your team works, what they work on, and how you run your team I would love to provide some insights. Hopefully, the examples are helpful.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.