What High-Level Tasks to Include in a Plan for New Jira/Confluence Implementation?

[JR]

Hi, my team is in the process of procuring, installing and configuring Jira/Confluence in our AWS environment (we're not currently able to use the cloud version due to the lack of FedRAMP compliance).

We currently use Zenhub for workflow management and a variety of tools for documentation/collaboration. We are going to start with a 90-day Atlassian pilot to "kick the tires" and make a go-forward decision after that. We've collected use cases and developed a strawman project plan for the pilot.

My question for the community is - for those who have gone through this process before, are there specific high-level tasks that you recommend to include in the plan? Thanks in advance.

[Petter Gonçalves]

Hello @JR

Welcome to Atlassian Community!

JIRA Application has a variety of features and ways to be used, like tracking of software developments or the management of business cases.

That being said, In order to confirm we are on the same page here and allow me to provide you with the useful features/tips for your specific scenario, I would like to hear from you how do you plan to use JIRA application. Could you provide us with more details about it?

For now, I would recommend you to check the core articles about JIRA permissions, workflows and Filters, since I know it will be useful to start setting your environment not mattering what you are planning to do:

- Permissions overview for JIRA Server

- Working with workflows

- Configuring filters

As far as we understand better what you want to achieve, we can provide you with more insights and tips to do it in the best way possible with JIRA. :)

[JR]

Thanks for getting back to me @Petter Gonçalves

I've used Jira and Confluence on a few projects in the past, but I would not call myself an expert :-). So, I'll definitely review the links you posted. Below are a few more characteristics that may give the community more insight into our objectives:

• Team of roughly 100-150 people
• Several disjointed teams that work on different (but related) products/workstreams and are spread throughout the US (and abroad for some team members)
• Primary objectives are three-fold: 1) create more cohesive workflows between these disparate teams to foster more collaboration when work is handed off (currently managed in Zenhub across dozens of Github repos), 2) stand up central repository to create/collaborate on all types of docs (currently done in Sharepoint for some artifacts. but not consistent across teams), 3) provide cross-team portfolio-level workstream and capacity reporting for leadership

We're in the process of procuring the Jira and Confluence to install/configure in our AWS instance. I have a high-level strawman project workplan, but am curious if the community can recommend other large chunks of work to consider as part of the 90-day pilot.

HTH and Thanks Again,

JR

[JR]

Another question I had for the community is - what success metrics (or feedback) did you use to inform your decision to move to Jira and Confluence?