tualization Infrastructure continuous improvement, and it encourages rapid and flexible response to change. These principles support the definition and continuing evolution of many software development methods (28, n.d.). The collaborative nature of Agile can pay large dividends in a relatively short amount of time. It has been stated publicly that the closing of OpenStack operational gaps with custom extensions and automation was due in large part to the use of an Agile structure. 4.3.1.2 DevOps "A set of guiding principles which promotes software excellence throughout its life. Barriers between software delivery disciplines are broken down to provide seamless transitions accelerating time to market while improving quality." DevOps (a clipped compound of development and operations) is a culture, movement, or prac- tice that emphasizes the collaboration and communication of both software developers and other IT professionals while automating the process of software delivery and infrastructure changes (29, n.d.). The usage of DevOps allows for cross-functional collaboration between operational teams, developers, quality assurance, and management teams while prioritizing operational needs earlier in the scoping process. It also establishes an environment where building, testing, and releasing software happens rapidly, frequently, and more reliably, with operations providing new features' requirements approval to ensure that ample operational support is provided at the least cost. 4.3.1.3 Continuous Integration/Continuous Delivery Continuous integration/continuous delivery (CI/CD) is an amalgamation of two software engineer- ing practices that aim to automate the building, testing, and releasing of software. Together, they go a long way in creating a more agile service provider. The goal of CI is to provide rapid feedback SO that if a defect is introduced into the code base, it can be identified and corrected as soon as possible (30, n.d.). With CI, iterative software changes are imme- diately tested and added to th