In order to preserve their competitive advantage, software producers need to deliver products and new features to customers as fast as they can. It is generally accepted that important problems in software delivery are rooted, among other aspects, in the disconnections among software development activities, causing delays in software delivery (Fitzgerald & Stol, 2017). This lack of connection lies not only on the technical side, where human aspects and knowledge management facets are some of the main areas to be improved. Continuous software engineering permits software features delivery at rates which a few years ago would have been considered unachieveable (ColomoPalacios, Fernandes, Soto-Acosta, & Sabbagh, 2011, p. 4; O’Connor, Elger, & Clarke, 2017). This approach is based heavily on applying automation to the overall software development process (including code collaboration tools, verification, version control system, deployment and release management…) by using several tools. These tools act as structures in which different types of knowledge are coded and shared among software practitioners. Like any other approach, continuous deployment presents benefits but also caveats. On the benefits side, the literature reports: Increased customer satisfaction, shorter time-to-market, higher developer productivity and efficiency, continuous rapid feedback and, finally, higher quality and reliability. With regard to the challenges, researchers found the wide panoply of tools available and their integration, organizational culture to be a hindrance to the transformation process and increased quality assurance efforts. The continuous approach goes beyond the borders of traditional software development to reach the operational side as well. In this scenario, DevOps stands for a continuous integration between software development (Dev) and its operational deployment (Ops).