Well, we often do employ great Atlassian administrators... but we don’t always have the correct answer for every situation. Our products and processes can be complex, from the way they are implemented to the purchases we have to make. I think of it like raising a kid. Have you ever heard the saying “it takes a village?” Well think of your Atlassian products as your kid. It takes a village to keep it a float.
I will be giving you a number of tips and tricks when organizing a Jira Guild in your organization. For this article, let’s start with the foundation. Before implementing anything, we need to plan. Sit down with your team and answer the following questions:
- What is the purpose of the Jira Guild in your organization?
- What is the Jira Guild’s vision?
- Who is part of the Jira Guild?
- How will we set expectations for the members of the Jira Guild?
- How often and where will the guild meet?
- Where will the Jira Guild’s decisions, processes and procedures live?
- What types of discussions will the Jira Guild have?
- Who will record the discussions during the Jira Guild?
- How will users communicate and propose changes to the Jira Guild?
- How will we measure the effectiveness of the Jira Guild?
While these are very high level questions, they’re essential to nail down before contacting potential Jira guild members and introducing the Jira Guild to your organization.
Stay tuned for next steps on building your Jira guild.