in Blog, More, Services

Agile, DevOps, Continuous Delivery

What is this, how does it affect me as a customer?

In this blog post I would like to follow up on our webinar “Agile, DevOps, Continuous Delivery: Was ist das und wie betrifft es mich als Kunde?” (currently only available in German) where I talked about the underlying methods of Agile, DevOps and Continuous Delivery using two different perspectives. First, how your development team can be more agile, flexible and efficient in their work with the help of modern methods – in order to be able to deliver new functions and updates faster to production. On the other hand, how you as a user of a software, can use the same methods to ensure optimal benefit of the shorter product cycles of the software vendors. Access the slides to this webinar on SlideShare.

What does DevOps mean?

DevOps is a software engineering culture and practice that aims at unifying software development (Dev) and software operations (Ops). This suggests that it is not enough to just use modern tools. It is even more important to initiate a cultural change that includes better collaboration and more flexible and efficient teamwork. DevOps is also not a single task.  It is much more a term which is used instead of a long list of different practices – Agile, Continuous Delivery, Shift left, Infrastructure as Code to only mention some of them. Furthermore, it is important to understand that DevOps isn’t a project – it is a continuous process of learning and improvement.

Agile, DevOps, Continuous Delivery - The Pros of DevOps

How does DevOps affect me as a customer?

An increasing amount of software vendors decide to use Continuous Integration to deliver features and updates on an ongoing basis. Unlike a managed solution, you have to take care of feature roll-outs and security updates yourself. You have to build and provide your own Continuous Delivery strategy to be able to act at the same speed as your software vendor does. This can be achieved by using and executing the same practices that development teams are using. In addition, you also benefit from increasing your agility, efficiency and flexibility.

Start your DevOps Journey

As mentioned above, the implementation of a DevOps culture and practices cannot be treated as a project – it is a continues process. The following steps will help you to start your own DevOps journey:

Agile, DevOps, Continuous Delivery
Agile, DevOps, Continuous Delivery - Define processes
Agile, DevOps, Continuous Delivery - Continuous Improvement

Agile, DevOps, Continuous Delivery - Assembly Line

panagenda can help you by…

Building your Private Cloud Infrastructure

You want to build your environment based on microservices, Kubernetes and other related technologies, but also host them on-premises instead of operating your services in a public cloud? Our consultants can help you design and build a production-ready private cloud environment according to your needs.

Automating your Infrastructure Processes

Do you already automate common processes in your IT landscape? Save time and money by automating recurring processes such as virtual machine or software deployments. We help you identify possible changes and improve your processes like virtual machine or software deployment by using our automation best-practices.

Automating your Software Development

To deliver new software features and updates in the fastest and most agile way possible, you need a fully automated pipeline that includes various build, test and deployment stages. Our consultants can help you establish and improve your build pipeline by using common CI/CD and DevOps toolsets.

Transforming your existing Applications to Microservices

You want to migrate your existing applications to a new technology stack based on microservices? We support your development as well as operation team in the transformation process by using the twelve-factor app approach.

Implementing a DevOps Culture

DevOps is not only about tools but about cultural change. We can support your organization moving forward and become more agile as well as adopting common methodologies which help you implementing a DevOps culture in your team.

panagenda Consulting

Related Posts


Showing 3 comments
  • Patrick Kwinten
    Reply

    what tools do you recommend to set up a CI/CD pipeline for Domino development?

    • Nico Meisenzahl
      Reply

      Hi Patrick,

      thank you for your comment.
      We have already contacted you by email to get more details about what you would like to achieve or improve. Of course, we will share the results here as soon as possible to allow everyone else to participate.

      Greets Nico

    • Nico Meisenzahl
      Reply

      I had a quick chat with Patrick about CI/CD with Domino and would like to share the outcomes we had so far:

      1. Managing code using Git: Managing, versioning can be done using the on-disk project function in Domino Designer (https://www.ibm.com/support/knowledgecenter/en/SSVRGU_10.0.0/user/wpd_srcecontrol_feature_setup.html). It will synchronize your code between your repository and your Domino project.
      2. Building the artifacts (templates): In my opinion, this is the most complex part. I’m not aware of any scripted solutions to build the code without manually using the Domino Designer. That doesn’t mean there aren’t any, but I don’t know any features which would help neither any third-party projects. It would be possible to use CI methods for building part of the code like Java sub-projects or similar. Also automatically testing your code (excluding pure web applications) will get really hard.
      3. Deployment: Deploying new versions should be straightforward with some scripting. Distributing new generates templates to all required servers and either wait for the designer task or manually refresh the design via command line.

      If anyone else is interested in participating in this conversation, please let me know.

Leave a Comment

Start typing and press Enter to search

File ForensicsMoving to cloud and hybrid