DevOps was first coined in 2009 by Patrick Debois when he created the community devopsdays. In the subsequent years, a revolution started changing how the developers and the operation team interact. This revolution brought many new techniques, new concepts, and new tools to bring value quicker to the product's end-user. Those concepts are applied in industries such as the web industry, the automobile industry, and the manufacturing industry, to name a few. Although the word DevOps is often associated with containers and deployment pipelines, it is much more than that. For an industrial project of three months, I embarked on this journey of continuous learning with a consulting company named Pragmaflow in Montréal, Québec. This industrial project started on sprint one and ended on sprint six of a new contract. We went through different solutions during this project while constantly learning and improving the processes to provide quick and reliable service to the customer. In this journey, we went through the first way of DevOps and the second way of DevOps. This journey allowed us to reduce our deployment time from two hours to fifteen minutes. The company in question is a small consulting company with around ten employees. As a consulting company, once the product or software is delivered, they do not have to worry about maintaining it. However, they encountered a new challenge when a contract asked to develop the software and the architecture on which the software would be hosted and delivered. This new contract brought different challenges such as a need for a highly available and self-healing architecture, a pipeline allowing fast integration, feedback, software delivery, and central logging to diagnose problems. We embarked on a journey from sprint one up to sprint six, where sprints lasted two weeks to tackle those challenges. The journey does not stop at sprint six or ever, but this industrial project was part of a course that lasted around three months.