Client
O2 is the largest integrated telecommunications provider in the Czech Republic. As of today, it operates nearly eight million mobile and fixed lines, maintaining a long-standing position among the leading providers of fully convergent services in Europe.
O2 offers the most comprehensive range of voice and data services in the Czech Republic, with a particular focus on leveraging growth potential, particularly in the ICT sector. Its access to data centers covering 7,300 square meters places it among the largest players in hosting and cloud services. O2 is also the largest operator of internet TV broadcasting in the Czech Republic, with O2 TV focused on sports broadcasts of global events.
Objectives and benefits of the project
Atlassian JIRA and Confluence have been used at O2 for several years. Following positive feedback from users across O2, a decision was made in 2014 to expand the use of these systems.
One of the main reasons was to increase the transparency of the IT change implementation process, which had been growing in volume, alongside an increase in the number of application vendors involved. Managing approvals and implementation of requests in a corporate environment is highly challenging, especially in coordinating the change owners. JIRA provides an ideal tool for communication and coordination among all involved roles.
Repetitive configuration changes can be processed quickly in the tool thanks to the ability to accept them within JIRA.
The structure of the change request allows JIRA to store data that could not previously be handed off for further processing.
Users make use of customized dashboards that provide quick overviews without the need to contact the change manager or business partner responsible for the change. JIRA is not only a tool for implementing changes but also a valuable environment for collecting ideas that will not progress to the creation phase.
Project implementation
Despite the extensive processes within the operator’s environment, the standard features of JIRA were sufficient for implementation (request types, extensive workflows, and approval processes). O2’s specific requirements were implemented using several independent plugins, which created an added layer of detail for the change requests in JIRA. This detail was extended with several specific areas and new attributes.
To ensure that the operation of other projects in JIRA is not disrupted, all new plugins are fully configurable to affect only the desired projects and parts of the JIRA system.
The entire implementation is carried out at the client’s headquarters. The input and acceptance of individual components occur on a daily basis. This approach to development is highly productive and reduces the risk of misdefined requirements. Representatives from all user departments are involved in the implementation process. Together, they discuss the processes, with the discussion being led by a JIRA Atlassian consultant to ensure that the proposed solution aligns with the product’s philosophy.
