2iC

Background

2iC use Confluence extensively for communications between internal and external developers, and to provide product documentation and a knowledge base for customers. Security is critical and must ensure that information is only visible or editable to the correct users. 2iC had two separate instances of Confluence, one for internal users and one for customers, but this separation made moving information between the two cumbersome and time consuming.

Additionally, 2iC started using Atlassian Jira about 6 years ago and since that time the product has evolved considerably. In particular, the issue management workflows they were using came from the superseded GreenHopper product which has been replaced by Atlassian. 2iC wanted to switch to using the more modern Agile workflows from Jira Software to ensure that they are using the current best practices to support their immediate development efforts and form a solid foundation moving into the future. Also, over time they had set up a number of different Jira instances, one for internal use and others for working with partners, and wanted to consolidate to a single instance to simplify administration and avoiding copying issue contents across systems.

Solution

BDQ combined the two old instances and rationalised the number of spaces. Working closely with 2iC to understand their security requirements, a detailed security scheme based on groups was developed and documented. 2iC now has a way of securely sharing information through Confluence and the scheme configured by BDQ makes management of user access easier and more transparent. The process of developing documentation internally and then sharing it with customerslater is much easier, saving the users a considerable amount of time.

Also, BDQ developed a migration plan to combine 2iC's Jira instances and carried out a series of dry runs to ensure that when cutting over the work could be completed in a single day to minimise disruption and downtime for the users. To smooth adoption of the new issue management workflows, a training workshop was held with the developers to make them familiar with how the modern Agile workflows worked.

Outcome

“The new instances set up and configured by BDQ have delivered exactly what I wanted. We have confidence in how the permissions scheme has been configured in Confluence and the Jira workflow will support our development efforts going forward.

Our secondary objective was to form a relationship with an Atlassian Solution Partner who has the expertise available to help us going forward. BDQ understand our needs and we are comfortable they will be able to fill that need.”

Graham Booth, Chief Executive Officer and Co-founder, 2iC