Case study: The CIP4 Organization’s new Atlassian infrastructure

Atlassian tools help companies advance and simplify, systematize and integrate processes. We support our customers with customized solutions to help them work better and use Atlassian software to solve their unique challenges. Here is a new case study of our customer CIP4 Organization.

The customer

CIP4 Organization is a non-profit organization with around 235 member companies from the graphics industry. CIP4 stands for "International Cooperation for Integration of Processes in Prepress, Press, and Postpress." The CIP4 Organization’s main objective is the promotion of development and implementation of process automation in the graphics industry. This is done by developing standards, offering seminars and providing tools.

Starting point

  • Using a MoinMoin wiki
  • Task management using their own solution and tables
  • Centralized development with SVN and Jenkins

Customer requirements

  • Creating a professional, high-quality, end-to-end solution for development, task management and documentation
  • Better system integration
  • Structured development process instead of "ad hoc hacking"
  • Establishing uniform Atlassian tools in all companies of the consortium
  • Offering the use of standard solutions, portability, hosting options and service-provider independence

The project

A workshop kicked off the project where the customer communicated their challenges, expectations and requirements. These were broken down into individual projects and requirements.

Over the course of the project, infrastructure based on Atlassian systems was set up according to the following scheme:


During software development, the Bamboo integration server and Git repository management solution Stash were used. The development process was migrated from a central to a distributed version control system (Git). Confluence with Confluence Questions and Confluence Team Calendars was used for documentation. Workflows and the structuring of projects were handled with Jira and Jira Agile. Discussions were conducted in Jira Issues and Confluence.

Benefits from the customer's point of view

Along with the newly structured and integrated infrastructure for software development, the customer appreciated the improved ability to track decisions. Jira and Confluence contributed significantly to greater visibility. Decisions that up until then had been hard to understand were suddenly more transparent (and public).

Particularities of working together

The new customer infrastructure immediately proved to be successful when the customer and implementation team discussed the project. Using a custom Jira workflow on a digital board made it possible to collaborate, coordinate and approve the provision of services with little bureaucracy (Discussion -> Estimation -> Approve -> Ready -> In Progress -> Closed). This process ensures short routes and a lean organization and also prevents project management overhead.


We are happy about the successful run of this project and look forward to future projects with CIP4 Organization.

Diesen Post auf Deutsch lesen.

Additional customers and references
Leading Atlassian employees on //SEIBERT/MEDIA
Atlassian-Software - Consultation, Licenses, Training, Support, Configuration

Our blog articles reflect the situation at the time of writing and are not updated. It is therefore possible that the contents are outdated and no longer correspond to the latest developments. We do not accept any liability for this.
Forget Less and Ensure Quality with didit Checklists for Atlassian Cloud Forget Less and Ensure Quality with didit Checklists for Atlassian Cloud Forget Less and Ensure Quality with didit Checklists for Atlassian Cloud

Leave a Reply