03_Handout_1(11).docx

**Information Technology Infrastructure Library (ITIL) (Advised Skills, 2023)** ITIL Processes ============== ITIL Functions ============== ITIL Practices ============== ITIL Principles =============== - **Focus on Value**: Everything the organization does must alway...

**Information Technology Infrastructure Library (ITIL) (Advised Skills, 2023)** ITIL Processes ============== ITIL Functions ============== ITIL Practices ============== ITIL Principles =============== - **Focus on Value**: Everything the organization does must always bring value to its stakeholders, specifically the customers. The services should be designed with a customer's satisfaction in mind. It is key to determine what the customers want to precisely match it with a value they will appreciate. But this is something that changes over time that can benefit an organization to grow with their customers. - **Start Where You Are**: This does not mean resetting everything from the start. This means focusing on what is already available and improving that existing system. Existing systems already have value on their own, so it is best to assess their strength and use that as the starting point. Focus on optimization and improvement as much as possible. - **Progress Iteratively with Feedback**: This reminds the people involved not to accomplish everything at once, as it can be overwhelming. Divide tasks into smaller parts and focus on each step to assess the value it can provide. Getting feedback after every step is also advised to ensure problems are solved, and oversights are reworked before it is too late. Progressing iteratively with sustained evaluation assures results are useful, tangible, and completed promptly. - **Collaborate and Promote Visibility**: This aims to take advantage of the different sets of strengths and weaknesses that each member of the IT team has through delivering collaborative efforts. It is best to prioritize honesty and visibility to collaborate effectively. Communicate each progress, whether good or bad and allow to be open to whatever feedback others might give. - **Think and Work Holistically**: To create the best service, it all must be connected, as no service, practice, process, or function stands alone. All activities should align with the same focus on the delivery of value. This is critical when working in a collaborative environment to ensure that the work does not affect any part of the organization and create any hindrance or disruption. - **Keep it Simple and Practical:** This is a reminder to not over-complicate anything to be done. Complicating any process increases the risks of going wrong and having more errors. Continuously assess the work and ensure that only the necessary steps are involved. Eliminate any process, step, or action that does not add value to the organization or the customer. - **Optimize and Automate**: Optimization makes things functional, so automation of any activity should be optimized first to utilize the resources to the best of their limits. Automation relieves the work on frequent and repetitive tasks. The human resources that could have been working on those tasks can be put into more complex tasks that contribute to the value. Elements of DevOps ================== 1. **People** -- the heart of DevOps, which is composed of a *DevOps team* consisting of a pool of tooling professionals. A DevOps team is built around an application; if an application is being developed, all the people responsible for its development and operations must be grouped to create a single team. For example, Application Z is an Internet banking program for individuals and small business owners. The possible DevOps team could be the following: - Product Owner -- the owner of the product and service backlog - Developer -- for coding and unit testing - Tester -- involved in developing test scripts - Architect -- designs the software and are shared across multiple DevOps teams - IT Security -- for managing aspects of IT security 2. **Process** -- The CI/CD pipeline consisting of Continuous Integration, Continuous Delivery, and Continuous Deployment is used for effective DevOps Methodology. This is a set of DevOps best practices to help teams deliver software faster and more efficiently. - **Continuous Integration** -- provides a central repository for developers to use throughout a project. This automates anything in the central repository to reduce errors and compile artifacts into organized builds to perform initial tests. - **Continuous Delivery** -- delivers the builds into the test environment and then needs human intervention to deploy the tested builds into production. It aims to get code changes like fixes or configuration changes into production faster and safely. - **Continuous Deployment** -- performs beyond Continuous Delivery and deploys automatically to production. This is viewed as a build on the established practices of Continuous Delivery, but this focuses more on a complete end-to-end automated approach, while Continuous Delivery requires human intervention. 3. **Technology** -- often regarded as the most important of processes. There are several tools that claim to support DevOps, see *Figure 1.* However, choosing the right tools is just as crucial since not all tools can be used for all technologies. DevOps Principles ================= - **Culture**: Culture cannot be changed in an instant as it is embedded into human behavior and would require an overhaul to do so. But there are some behavioral traits that DevOps seeks to change: - Taking responsibility for the entire product and not just the task performed - Stepping out of the comfort zone to innovate - Communication, collaborating, and developing an affinity with the teams - Experimenting as much as possible - **Automation** -- an enabler of faster delivery and crucial for providing rapid feedback. Repetitive tasks that do not require human intelligence are the kinds of activities that can be efficiently automated. For instance, building infrastructure before was a major task for hardware architects and administrators and building servers took a significant amount of time. Now, cloud infrastructures are much utilized, and servers can be created through coding. - **Lean**: DevOps borrowed from Lean technology which is about keeping things simple and not overcomplicating them. This allows the teams to focus and work on things that are easy to comprehend and simple to work with. The first part of the Lean principle addresses that the primary issue is not to bloat the way to do things, just do them straightforward and minimally. The second part is to reduce waste from the methodology such as defects and convoluted processes. Defects and convoluted processes delay the overall delivery, and it takes much more time and money to address and fix them. - **Measurement**: The only way to find out whether the outcome is favorable is by measuring it. This principle provides direction about the measures to implement and keep tabs to feel the reception of the overall software delivery. Feedback could be used as a measurement to automate processes. Measurements in monitoring such as in applications and infrastructure, can indicate when an event is a warning or an exception. - **Sharing**: This is the need for collaboration and knowledge sharing between people. The shared knowledge, experience, ideas, and thoughts can help others in making them better and more profound. This leads to collaboration instead of competition and skepticism. In DVCS, accessing, adding, combining, and delivering the code is faster compared to CVCS.  IT2312 ======