The EOS Group has long managed the requirements management of its collection processing via a requirements database. By using Jira, catworkx was able to transfer the implementation requirements into Jira and optimize and simplify application lifecycle management.
The result was improved interaction between the business and IT departments, as well as automatic generation of projects and processes during state transitions with data synchronization.
EOS Technology
The EOS Group uses a system for debt collection processing that was implemented by EOS IT Services GmbH and is further developed in fixed release cycles. The departments used to enter their implementation requirements for EOS IT Services in a shared requirements database. This database supported the entire lifecycle of the collection solution – from the requirement to going live. However, it did not provide enough transparency to show the connection between all processes. In addition, a user-friendly search function and flexible dashboard functionalities were missing. As a proprietary in-house development, further development and support were increasingly no longer guaranteed.
EOS IT Services GmbH therefore decided to replace this system. The EOS Group had already selected Jira as its tool before catworkx was commissioned to implement application life cycle management.
The departments enter their requirements in a separate Jira project as processes. Based on a configurable calculation function, they are automatically prioritized after sufficient concretization. Requirements for implementation are roughly classified into three types in consultation with IT:
With this classification, an order is placed via an automatic process copy with a link to an IT Jira project. Here, the requirement is refined and, if necessary, the classification is reassessed. On closer analysis, for example, the initially estimated effort for a minor change may prove to be higher, so that the requirement has to be implemented as a project.
Thanks to the Jira solution, we can optimally fulfill our tasks. We benefit from the very clear presentation of the application lifecycle management and from the high transparency when viewing the relationships between the individual processes, from the requirement to going live. The Jira apps from catworkx, which were added to the solution, also provide us with significant support.
Projects are collected as activities in a special portfolio project. Special filter views represent the project lists typical for portfolio meetings. A dedicated workflow for the project, with corresponding release levels, automatically creates a Jira project at a certain point in time, via a right-restricted state transition. In this project, the development tracks all project-related tasks.
The release management is attached to a version process that significantly extends the standard version functionality of a project. As part of the version workflow, the tasks necessary for a new version are tracked for code, merge, integration, and regression testing (including bug fixing). This is done via automatically generated subtasks for each completed partial result, which are referenced to corresponding minor changes or project processes.
In the Jira system, the application lifecycle manifests itself as a sequence of different processes of different types, across various projects with defined responsibilities. All related processes are linked together. This makes it possible to trace the path a development task has taken from the initial request to its incorporation into a version.
The integration of Atlassian tools and self-developed apps created a homogenous platform:
We advise you on the entire Atlassian ecosystem and are happy to support you in optimizing license models and costs.
