This is a question regarding the way how we organise our teams and products.
Current scenario:
We have multiple teams, and each one of those teams has multiple products (ranges from 1 to 20, depending on the team size). There's one Jira project per team, and each product is created as a "component". This eases the process (time-saving) and allows the use of Roadmaps, but it represents several difficulties when a product changes from one team to another, or a team is extinct and the product is inherited by another team.
The documentation ends up getting scattered throughout multiple projects with different teams.
Proposal:
The proposal is for each product to have its own Jira Project. This way, all documentation (stories, tasks, bugs, defects, etc.) would stay in this sole project. Each team would need to use one Jira project that would have filters to catch and display the issues from those products assigned to that specific team.
That said, the projects for the products would be merely repositories, and the sprint workflow/schemes/columns/states would be a copy of the main management board.
Each team would have multiple boards but would manage issues on only 1 board, maintaining all needed metrics (sprint reports, velocity, etc.).
Questions:
- Does this proposal make sense?
- How does the Atlassian team manage this?
(I also thought of a scenario where each product is a board inside one project, but would it be possible and easy to move one board + issues ownership from one project to another?)
P.S. - we have company-managed projects
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.