Partnership regio iT | Seibert Solutions

regio iT and Seibert Solutions

Why regio iT switched from Jira On-Prem to the Atlassian Cloud and what changed as a result in operations, structure and collaboration.

Learn more Get in touch

”The biggest advantage is actually that we have built a homogenized structure where everyone can find their way around.”

Alexander Cools | Chief Digital & Information Officer | regio iT

In Brief

regio iT

The move to the cloud took operational responsibility for the system off regio iT’s plate. The cloud replaces their own server, database and patching tasks with secure standard operations without ongoing update and plugin overhead. At the same time, the Jira structure was rebuilt so that it is consistent and easier to use across all projects.

Industry: IT
Headquarters: Aachen, Germany
Employees: approx. 750

Products in use:

Jira
Confluence
Templating.app
Awesome Custom Fields

A strong Atlassian partner

Our approach

The move to the cloud was deliberately used by regio iT to question existing structures. First, the current situation was analyzed and requirements from existing usage were collected. On this basis, a new Jira setup was developed in workshops and through exchange with stakeholders – deliberately not carrying over historical legacy structures. The goal was a consistent structure that works for all teams in their daily work and facilitates cross-project collaboration.

Interesting Fact

regio iT deliberately chose a greenfield approach: learning from existing experience without carrying over grown structures, fields or workflows to the cloud.

Joint results we’re proud of

The move to the cloud has noticeably relieved regio iT in operations and at the same time created the basis for a consistently standardized way of working across projects. Instead of their own server, database and patching topics, Jira now runs in secure standard operations. The greenfield approach was used to deliberately avoid carrying over historical legacy and to build a structure that is understandable for all teams and clearly regulates collaboration with external partners.

Operations

Operational responsibility no longer lies with in-house operations. Maintenance, updates and dependencies on plugins and scripts are eliminated, significantly simplifying day-to-day operations.

Team organization

The Jira structure is homogenized across all projects. Consistent fields, statuses and workflows provide familiarity, so every person can quickly orient themselves regardless of the project.

Collaboration with externals

External service providers and customers can be integrated more easily. Defined security levels control which issues remain internal and which are visible externally.