Development Operations

Continuous X

Development Operations, or DevOps for short, describes the approach via which development and operations teams understand and accept their mutual points of view and needs in order to achieve a shared objective: Agility.

Using this method you can publish several hundred releases per month instead of just one, large version update. Without dropping established quality standards. DevOps enables your releases to be continuously integrated by linking changes, builds, tests and deployment to one another in one automated pipeline.

Beginnen Sie Ihre Devops-Reise mit dem ersten Schritt

Die Beziehungen zwischen Softwareentwicklung und IT-Betrieb werden häufig als schwach und manchmal als sehr schlecht bezeichnet.


Ausgehend von der klassischen Trennung des IT-Betriebs von der Softwareentwicklung werden die Beziehungen zueinander häufig als schwach und manchmal als sehr schlecht bezeichnet. Doch es gibt Wege, die Sichtweise einander anzunähern.

Um die Auslieferung zu beschleunigen und das (agile) Geschäftspotential zu nutzen, müssen diese Wege vereinigt werden. Schon in diesem Jahr werden 40 % der Unternehmen mit Entwicklungsabteilungen gemeinsame Initiativen mit dem IT-Betrieb etabliert haben, die "Continuous Delivery" und ein einfaches Releasemanagement ermöglichen.

Gemeinsam für mehr Kundenzufriedenheit

2016 werden 40 % der Unternehmen mit Entwicklungsabteilungen gemeinsame Initiativen mit dem IT-Betrieb etabliert haben, die »Continuous Delivery« und ein einfaches Releasemanagement ermöglichen.


Schaffen Sie Metriken, die Ihre geschäftsrelevanten Prozesse und Bereiche unterstützen und helfen Sie Menschen, Ihre Zusammenarbeit zu verbessern. Als erfahrene Berater zeigen wir Ihnen, wie Sie DevOps-Methoden in Ihrem Unternehmen konzeptionieren und unter Berücksichtigung der geschäftspolitischen Strategie implementieren können.

In einem mehrstufigen Prozess identifizieren wir mit Ihnen gemeinsam die wichtigsten Stellschrauben und erarbeiten für Sie aufgrund unserer Best Practise-Erfahrungen eine konkrete Handlungsempfehlung.

Centralise the code base and builds

We can show you how to achieve continuous integration which, adjusted to suit your conditions and needs, may also be done step by step. In the first step, build processes are moved from the various developer workstations to one or more build servers. A key requirement for this is that your entire code base has a centralised version management system. When the developer also references any code modification to a requirement, it means the links between the requirement, task, code change and build can be tracked.

Automation

The build is supplemented by unit tests from the developer's perspective and standardised software distribution processes to the relevant development, testing, acceptance or production systems.
The latter requires the integration of the operations teams and the target platforms, architectures and systems. There is also a need for defined rollout processes for the build artifacts.

"Continuous Integration": the magic term

Increases in what is required of processes and technical infrastructure mean that new methods are needed. The principle of continuous integration is based on integrating new or modified source code with existing code, and building and testing it, on an ongoing basis and as often as possible.

You put the foundations for this in place by having a centralised version management system for your entire code base, so that you can see what the current state of development is whenever you wish. Ideally, the requirement, task, code modification and software build combine to form a single loop which, as a process in the continuous assembling of components, leads to an executable application - continuous integration!

Benefits

  • Changes are transparent
  • Link between requirement, code modification, build and deployment artifact
  • Fully automated unit tests, functional and performance tests within the pipeline
  • Staging functionality for software releases between testing, acceptance and production environments

Success factors

  • Continuous communication between the partners involved
  • Processes that support continuous development and deployment
  • Possible adjustments to service level agreements and contracts

Tools

There is a range of tools that touch directly or indirectly on the subject of DevOps. Based on our experience we can advise you, recommend a suitable tool, and integrate it into your system landscape. As well as offerings from leading manufacturers there are also, in particular, products from the open source sector which offer similar functionalities:

  • Maven, Ant, Junit
  • Jenkins
  • HP Continuous Delivery Automation
  • HP Application Lifecycle Intelligence als ALM Extension
  • Puppet
  • Chef

Your opinion matters!

Did you find what you were looking for?

What we do

Software Configuration Management

[Translate to English:] xxx

Design the CI pipeline

We analyse the current position, studying your processes and tool landscape in terms of integration options, tooling and interfaces, plus any issues relating to the application concerned.
Then, step by step, we develop potential solutions for your DevOps process.

Setup & configuration

When the plan is complete we implement the DevOps pipeline for your IT systems and provide support with integration into the tool landscape.

Training courses

Our consultants bring the practical skills they have acquired on client projects to our bespoke training courses. The courses are customised to suit our clients' requirements and are held either on-site or off-site.