Highway Three Solutions

Case Study: Traction Guest’s Friction Free Conversion to Jira

#Case Study#Cloud Migration#Confluence#Jira Cloud

Traction Guest Enjoys High-Speed, Friction-Free Conversion to JIRA and Confluence

Traction Guest is an industry leader in enterprise visitor management, making on-site experiences for employees and guests safe, secure, and effortless. With offices in Vancouver, Seattle, and Dublin, they needed a cohesive cloud platform with the ability to keep up with their agile development process.

Al Henry joined Traction Guest in 2019 and was tasked with enhancing the agile approach for their development team, featuring scrums, ceremonies, and sprints. He’d had experience with Jira in a previous organization, but Traction Guest was using a modified version of another work management platform. After realizing that the promised benefits of the current platform didn’t balance out the workarounds necessary to make it effective in an agile environment, and aggravated by a lack of visibility and reporting capacity, Al recommended an upgrade to Atlassian Cloud to take advantage of the power of Jira and Confluence.

Imminent Deadline

During the decision phase, the team discovered that the incumbent platform’s licensing was due for renewal in three weeks. As Al had a proposal in place with Highway Three Solutions, he reached out to them to see if they could implement the conversion on a highly compressed timeline: he’d need a week to prepare for the migration, leaving only two weeks to install, update, and test the Atlassian cloud installation.

Highway Three Solutions responded by having two of their key professionals construct a project plan to convert before the end of the month. Traction Guest approved the plan, opting for a cloud solution to eliminate any on-prem performance concerns, and began the migration preparation process.

During the migration, the Traction Guest team discovered that despite having admin access through the previous PM resource, they couldn’t actually see all of their projects, resulting in a few being skipped in the data mapping process. With Highway Three’s help, Al and his team were able to recalibrate and resynchronize, getting access to the previously unseen data without losing essential components.

“We did have one glitch during the migration, and the Highway Three team took care of it for us,” explained Al. “They contacted Atlassian, submitted and managed the ticket, and helped us recover from the issue. They were very effective in resolving our issues!”

The Highway Three team implemented the plan, converted the database, integrated with Aha!, and the Traction Guest team was up and running with Jira on the first of the month.

Highway Three Solutions professionalism and attention to detail was evident as the teams worked together to deliver the project on time. Our experience with Highway Three Solutions is a beneficial one as we work together to maintain the new Jira system and look to continuously improve our processes with their assistance.

Moving Forward

Traction Guest’s primary focus was getting Jira up and working, integrating it into the development process. “We haven’t made full use of Confluence yet,” shared Al, “but our support structure is now using it to house our runbooks and support documentation for triaging incidents, and our strike teams are using Confluence to house documentation about new-feature implementations.” Confluence provides a central repository, which is much easier to use and manage than Traction Guest’s previous model that relied on Google Docs, Quip worksheets, and local storage. “The searching capability of Confluence makes it a powerful tool for our teams,” said Al, “and we’re working on some training sessions to help everyone get up to speed with it.”

With six months of experience on the new platform, Al and his team are very pleased with the support, training, and advice from the Highway Three team, sharing “they’re a great consulting team, and I appreciate that it feels like we work together on things, as opposed to us reaching out and merely contracting them to do the work.”

Challenges:

  • Multiple workarounds to make incumbent project management tool fit desired agile process
  • Poor visibility into projects and reports
  • Various versions and locations of essential documentation
  • Highly compressed window to implement transition to Jira

Solutions:

  • Implemented a complete migration to Atlassian Cloud, including Jira, Confluence, and JSM
  • Migration completed in less than two weeks with maximum communications
  • Implemented standardized scrum processes to provide planning and tracking across teams
  • Capitalized on Jira’s reporting capabilities to communicate planning and status to management team

Results

  • Jira dashboards, filters, and formats to provide a customized view of current projects
  • Effective isolation between different strike teams
  • Consolidated, searchable repository for all documentation via Confluence
  • Seamless integration with Aha! Roadmaps and collaboration tools
  • Strong relationship with Highway Three Solutions for training and support for Atlassian products