Your IT projectneeds software.You already have it.

Almost every project in a business department needs a tool: for requests, approvals, reviews, documentation, reports. The reflex is to procure new software.

In most organizations, Jira and Confluence have long been in place, rolled out and approved. Building on them saves the entire procurement process. If know-how or capacity is short in-house, we step in.

Procuring new software means

Eight steps before the project begins.

Expensive, laborious, slow. Every one of these steps is mandatory when a new application comes into the organization. With Jira and Confluence, they are already done.

Align with the IT strategy

Does the new software fit the IT strategy, or does the strategy have to change? Coordination with the Head of IT before anything is procured.

Purchasing and vendor selection

Comparing quotes or issuing a tender, vendor assessment, contract negotiation. Purchasing has to be involved and has deadlines of its own.

Compliance assessment

Review against standards, legal requirements and the demands of your industry: data protection, information security, retention, evidence obligations.

Train admins and users

New interface, new terms, new roles. Administrators and users need training before the project delivers any value.

Develop an authorization concept

Who may see and change what? Roles, groups and approvals have to be designed, agreed and documented.

Integrate user management

Connection to the directory, single sign-on, joiners and leavers. Every additional application is one more connection that needs maintaining.

Additional update work

Release cycles, patches, compatibility with the rest of the landscape. One more system that has to be kept up to date permanently.

Backup and recovery

Set up backups, test restores, and do so regularly. A backup that has never been restored is only an assumption.

With Jira and Confluence

Already done.

The platform is rolled out, reviewed and in operation. Your project starts where it belongs: with the business requirements.

When know-how or capacity is missing

Then we step in.

Your IT remains the owner of the platform. We deliver the project together with them, from consulting to handover, and document it so that it stays auditable.

  1. Consulting
  2. Business analysis
  3. Design
  4. Implementation
  5. Testing
  6. Training
  7. Documentation
  8. Support

Use cases

What business departments build with Jira and Confluence.

Four examples from our project work. Each begins with the business task. Jira and Confluence only come into play at implementation.

  1. Use case 01 · Governance

    Document control for processes, policies and guidelines

    Starting point
    Processes, policies and guidelines had to be created, reviewed, approved and regularly updated in one central place. The business department needed a traceable approval process with clear responsibilities and documented versions. A custom solution built by internal IT would have meant additional development and operating effort.
    Implementation
    Document control was implemented in Confluence with Comala. Defined workflows with editing, review, approval and publication were set up for the different document types. Roles, approval steps and status transitions make it visible at all times which state a document is in and who has to act next.
    Result
    Today the business department manages its processes, policies and guidelines in Confluence on its own. Approvals and changes are traceable, while technical support and further development of the solution can be handled centrally.

  2. Use case 02 · Quality assurance

    Measuring equipment management and calibration

    Starting point
    Measuring equipment had to be recorded centrally and tracked across its entire life cycle. The key questions were: Where is a piece of equipment, who is currently using it, and when is the next calibration due? The existing systems did not offer a sufficiently flexible process for this.
    Implementation
    The measuring equipment was modeled as objects in Jira Assets, including serial number, location, responsible person, calibration status and next calibration date. Jira drives the associated processes, such as issuing and returning equipment and upcoming calibrations. Tickets and assets are linked directly to each other.
    Result
    The business department has an up-to-date overview of the inventory, use and calibration status of its measuring equipment at all times. Upcoming actions can be managed and documented systematically. The solution remains centrally administrable, while the business data is maintained by the department itself.

  3. Use case 03 · Project management

    Managing the project portfolio centrally

    Starting point
    Several projects were running in parallel but were largely planned and managed individually. Those responsible lacked a shared view of deadlines, progress, dependencies and critical projects. An additional portfolio management platform was to be avoided if possible.
    Implementation
    The existing Jira projects were brought together into an overarching portfolio view. With Jira Plans or roadmaps, projects, milestones and dependencies can be planned and monitored together. For more complex requirements, Structure can be added to build custom hierarchies, reports and portfolio views.
    Result
    Project and portfolio managers can steer several projects from one shared view and spot deviations early. The project teams keep working in their familiar Jira projects. The portfolio view is built from the same data.

  4. Use case 04 · Procurement

    Procurement with compliance review

    Starting point
    Procurement requests had to be reviewed by various parties before an order was placed. Depending on the purchase, managers, compliance officers and data protection officers had to be involved, for example. Coordinating by email led to follow-up questions, a lack of transparency and approvals that were hard to trace.
    Implementation
    The procurement process was implemented as a workflow in Jira. Employees submit their procurement request through a structured form. Depending on the details, the request automatically passes through the required review and approval steps, for example by the responsible lead, compliance and the data protection officer. Decisions, comments and approvals are documented directly on the ticket.
    Result
    Purchases run through a single, traceable process. Requesters can see the current status at any time, reviewers receive exactly the tickets relevant to them, and approvals are documented centrally. Changes to the process can be made through Jira configuration, without having to develop a dedicated application.

Next step

Tell us about your project. We will tell you how much of it Jira and Confluence can already do.

Have your project assessed

Your inquiry becomes a ticket with a number. We get back to you personally.