Best Practice Jira Governance in a company-managed project

[Snorre Strand Asbjørnsen]

I have been asked to create a Jira Governance project for an agile software development project using company-managed teams and tied to 2 plans consisting of over 25 projects.

Goal of Jira Governance Project is to have project with project owners to evaluate general Jira functionality utilized across teams, evaluation of product integration such as Atlassian Compass, Documentation for new processes, defining approval processes, defining and configuring access requirements etc etc.

To be honest I am not entirely sure how to best approach this so any resources is welcomed, insightful videos are also welcomed. Essentially I am asking:

What are the best practices on how to approach this type of project?

What kind of project should it be (business, software, product discovery project)?

Should one use a Kanban or Scrum board (Both types are used in the relevant projects)?

[Martin Runge]

Hi @Snorre Strand Asbjørnsen

I recommend setting it up as a company-managed project using a Kanban board. Since governance work comes in at different times, a queue might work better than sprints. You can use Confluence for the official rules and keep the project focus on requests and decisions.

Two official Atlassian reads that cover most of your questions:

• The human side to scaling Jira: https://www.atlassian.com/blog/development/human-side-scaling-jira-software-governance-custom-fields-admins
• Jira custom fields governance on Success Central: https://success.atlassian.com/solution-resources/agile-and-devops-ado/agile-at-scale-practices/jira-custom-fields-governance

Is this still relevant to you, or have you already landed on a setup?

Cheers, Martin