My passion is helping companies bringing people, processes and technology together so that they can deliver continuously value to their customers.
I graduated in 2001 as a computer scientist at FHNW. In the 19 years where I worked as a software developer, software architect and consultant for Zühlke, I was able to build up a comprehensive knowledge of software development, architecture and processes. I have worked with a variety of platforms and technologies, consulting in the sectors of financial, insurance, cyber security, electricity, medical, and aviation. Software development is a young profession, and we are still learning the techniques and building the tools to do it effectively. That's why my passion is helping companies bringing people, processes and technology together so that they can deliver continuously value to their customers.
Experience & Intrests
You face the challenge of enhancing efficiency while lowering costs. And approved changes to a product often take too long to reach customers in the marketplace. I use DevOps to shorten feedback loops and speed up throughput – from the initial concept to delivering the product to the customer.
Software architectures and systems can be very complex. I provide easy-to-understand, fact-oriented recommendations for action. These give you the security you need for pioneering and strategic decisions.
Insufficient stability and a lack of flexibility when it comes to adapting existing IT systems and business applications can impair the performance of companies. Due to my experience of completing many complex and successful modernisation projects, I'm perfectly equipped to accompany you through your transformation.
Every speach will be customized for your event. I will work closely with you to ensure that the speach meets your goals.
Here are some of my greatest hits:
Empowerment through DevOps
Today, companies are confronted with the challenge of necessary cost reductions while simultaneously increasing efficiency. Changes to products often take far too long to reach the end customers in the market. A consistent DevOps approach can provide a remedy.
DevOps is a software engineering culture and practice that aims to unite software development (Dev) and software operations (Ops) in order to continuously improve a software product and create added value.
DevOps is not only about bringing together Dev and Ops, but all the people involved.
=> DevOps brings people, technologies and processes together to create continuous added value.
Performing a DevOps transformation is not magic. The important thing is to start small, choose the right people for the team and then constantly and continuously improve.
What is DevOps?
How to DevOps?
Impact of a DevOps Transformation
What is the business case for DevOps?
Everyone wants to do DevOps. But only few understand what DevOps is and what it does with your company. When you want to introduce DevOps in a company you need to convince decision makers that it is worth to invest money / time / resources into the DevOps transformation. They will ask you about the business case and the return on investment of DevOps. In this talk I will show you how to convince the decision maker about the business case and the return on investment of DevOps, so that you get the money / time and resources for your DevOps transformation.
How is value created?
Concept of time value of money
Return of investment with DevOps
Legacy Applications Modernisation
Old applications have a great value for the company. They were developed with a lot of passion and contain a great deal of knowledge about the company. This is often forgotten when the responsible persons have to face certain challenges like outdated technologies, technical debts, time pressure and completely new business wishes.
There are four strategies to transform a legacy application into something sustainable and a structured approach ensures that the modernization process is reliable and expedient.
Four strategies to transform a legacy application
Four step structured approach
How to deal with a legacy monolithic monster application
There are huge legacy monolithic monster applications out there. They're terrifying. They can and will eat you alive. How can you approach such a monster? How do you tame such a monster? How do you make such a monster fit for DevOps? I will show you how to turn a monster in a purring cat.
Types of mosters (legacy application)
10 Strategies to tame such a monster.