DevOps / ITSM project management crash course

In this lecture, we're considering the importance of SLAs and legal documentation in DevOps and ITSM project management. It emphasizes the relationship between DevOps and ITSM and suggests that SLAs or Statements of Work (SOW) should be used to formalize the client-manager relationship. Key topics covered in these documents include Service Scope, Requests Priority, Reaction time, team roles, etc. It encourages building SLAs using templates and examples and advises regular consultation with customers to address any gaps or changes. Additionally, it emphasizes the importance of starting with a simple SLA, seeking feedback, and continually improving the document to adapt to unforeseen circumstances.

We are talking about different ITSM/support service levels: L1 (Service Desk, which serves as the initial point of contact for users), L2 (Specialized IT Support, which comprises skilled IT experts), and L3 (Development Team, which addresses intricate issues involving code changes and functional enhancements)

In our upcoming lecture, we will explore the dynamic landscape of IT Service Management (ITSM) with a special focus on various types of requests, events, and incidents that play pivotal roles in maintaining seamless IT operations. These processes are fundamental in ensuring the uninterrupted delivery of services and aligning IT with business objectives.

In our next lecture, we dive into Event Management—a vital component of IT Service Management. As an ITSM PM, you'll discover the art of tracking and analyzing events to create efficient workflows for proactive responses.

Event Management revolves around the meticulous management of events tracked within your monitoring system. These events encompass triggered alerts and received notifications, all pivotal in maintaining system health.

Our lecture will provide invaluable Event Management tips, including optimizing your monitoring system for maximum coverage of crucial parameters.

Join us for this lecture and elevate your ITSM skills.

This lecture will establish a foundational understanding of Incident Management—an integral aspect of IT Service Management. This theoretical session sets the stage for practical implementation in later discussions, particularly in the Incident Management flow analysis.

Incident Management centers on swiftly restoring normal service operations and minimizing the impact of outages on customers and users. The primary goal is to ensure impeccable service quality.

We'll delve into the concept of workarounds—temporary actions to tackle incidents or problems. When a known workaround exists, immediate incident resolution becomes feasible.

In the upcoming lecture, we delve into Problem Management—an essential component of IT Service Management. This process is dedicated to preventing incidents from occurring and ensuring their non-recurrence, fostering long-term system stability.

Central to Problem Management is root cause analysis (RCA). We explore how identifying the underlying cause of incidents serves as the cornerstone of this process. By addressing the root cause, you not only resolve the immediate issue but also create a stable foundation for future operations.

In this topic we'll talk about Change Management, which is a crucial process for businesses aiming to implement changes smoothly and efficiently, minimizing disruptions and ensuring operational continuity. Its primary objective is to establish standardized procedures that prevent unintended interruptions during change implementation. We will discuss several key stages, including change assessment, planning, and approval.

This lesson introduces Jira Service Management, presents a practical workflow for managing changes, highlights various ticket statuses, and provides helpful change management recommendations, including tracking, testing, scheduling, and documentation.

Here we are speaking about Request Fulfillment, which involves resolving customer service requests and managing their lifecycle. The service desk focuses on responding to requests while maintaining high service quality. Some quick tips are shared as well.

In this lecture we are providing information about project planning and management within the context of DevOps using tools like Jira or Azure DevOps Board. In the realm of Project Management, particularly in the context of DevOps, tools like Jira or Azure DevOps Board are commonly utilized. These tools aid in managing and planning teamwork efficiently. When planning a DevOps project using Jira, several key tips can enhance the process.

In this lesson, we will explore a range of commonly used tools and services within the realm of DevOps and IT Service Management (ITSM) project management. These tools serve various purposes across different stages of development and operations, promoting efficiency and collaboration (Monitoring Tools, Source control tools, Tracking systems, etc)

In this lesson, we delve into the provisioning of infrastructure and resources within a DevOps project management context. The process involves setting up various environments – such as Development, QA, UAT, and Production – and ensuring they closely resemble the Production environment. Keeping environments consistent with Production is crucial for effective testing and problem diagnosis. Even if using sample data, maintaining consistency aids in accurate testing.

By understanding these practices and considerations, you, as a Project Manager, can facilitate effective infrastructure provisioning, create consistency among environments, optimize costs, and ensure that your DevOps team operates in alignment with best practices. This approach fosters a reliable and efficient environment setup for successful project outcomes.

This section provides insights into the importance of monitoring and logging systems in DevOps projects, highlighting the need for effective collaboration, clear client communication, and a pragmatic approach to setting up monitoring tools.

The section emphasizes the importance of aligning the monitoring system with client requirements, creating an effective alert system, and establishing a comprehensive monitoring dashboard. This content covering Monitoring System Vision and alert scheme for Azure-based projects.

By the end of the lecture, students will have gained practical knowledge on how to design and implement a comprehensive monitoring system vision within an AWS environment. They will be able to set up alarms for various scenarios, enabling timely alerts and proactive response to potential issues. This example serves as a practical illustration of how monitoring and alerting strategies can be effectively applied to ensure the stability and performance of systems in a cloud-based infrastructure.

By the end of the lecture, students will have a comprehensive understanding of how to implement a more sophisticated telemetry metrics system. This approach allows them to monitor various layers of the project, from infrastructure to business outcomes. It highlights the importance of gathering diverse metrics to ensure a holistic view of the project's performance, user experience, and overall success. This lecture prepares students to handle larger and more complex projects with a data-driven approach to monitoring and improvement.

By the end of the lecture, students will have a comprehensive understanding of how to implement a more sophisticated telemetry metrics system. This approach allows them to monitor various layers of the project, from infrastructure to business outcomes. It highlights the importance of gathering diverse metrics to ensure a holistic view of the project's performance, user experience, and overall success. This lecture prepares students to handle larger and more complex projects with a data-driven approach to monitoring and improvement.

As long as you set up alerts and dashboards, you need to create a protocol, or formal Incident management flow, which helps the team know how to proceed with alerts. So we will take a look at some main steps of Incident management

The lesson introduces a real-life incident management flow document that will be explored in detail. This document serves as an instruction for ITSM/support team members on how to process incidents and submit tickets.

The lesson is about a Root Cause Analysis (RCA) report template and the process of conducting a root cause analysis for an incident. The lesson emphasizes the importance of maintaining an Incident Knowledge database to store information about incidents and their resolutions. A real-life example is provided to illustrate the application of RCA in identifying the root cause of a function failure and proposing solutions to prevent future occurrences.

This lesson is about matching priorities and severities when working on incidents. Different tools have different names for priorities, so it's important to match them correctly. The lesson provides a table that shows the matching priorities between the contract, Jira ticket priorities, and Azure alert severities. The lesson also includes instructions on how to submit information about an incident, including what details to include in the request.

This lesson provides a brief overview of the basic steps involved in implementing a CI/CD (Continuous Integration/Continuous Deployment) pipeline. The lesson also provides additional considerations for implementation, such as protecting data and configuration files, implementing an effective backup strategy, and periodically verifying backups.

In this lecture, we discuss the release and build management flow for CI/CD (Continuous Integration/Continuous Development) in a DevOps environment. The lecture emphasizes the importance of working with developers to ensure code changes are delivered frequently, in small batches, and reliably. The lecturer then provides a real-life example of a release and build management flow, covering various environments such as Dev, QA, UAT, Sandbox, and Production.

The lecture concludes by mentioning the importance of having a rollback procedure for database migrations and suggests creating a release flow diagram as a visual representation of the process.

In this lesson on Release and Build Management, some tips are provided. They are related to business approvers, maintenance windows and releasing on Friday nights.

The lecture discusses the importance of having a backup and recovery plan in order to protect the integrity of business-critical data and swiftly restore operations in the event of data loss. It explains that backup and recovery involves backing up data to ensure it exists elsewhere in case of loss and setting up systems that allow for data recovery. The lecture also mentions that organizations can opt for different backup and recovery models. The lecture outlines the steps involved in setting up a backup process. Additionally, the lecture highlights the components that a comprehensive backup and recovery plan should include.

The lecture discusses the roles and responsibilities involved in crafting a backup and recovery strategy. It emphasizes that backup and recovery management goes beyond just establishing a method for taking backups. The lecture also highlights the importance of backing up all necessary data to ensure availability in case of data loss or downtime.

Having a definite and regular backup schedule is deemed essential.

The lecture discusses different types of backup methods, including full, differential, and incremental backups. Overall, the lecture highlights the advantages and considerations of each backup method, allowing for the selection of an appropriate strategy for creating backups.

The lecture discussed the options for storing backed-up data, including on-premises and in the cloud. It mentioned that both options have pros and cons, so organizations need to choose the best option for their needs. It also emphasized the importance of implementing and following a backup procedure, which should include creating backup copies, storing them in multiple sites, and regularly testing the backup environment.

In this lecture, we talk about the importance of defining recovery objectives for an efficient backup and recovery strategy. The two critical recovery objectives are the recovery point objective (RPO) and the recovery time objective (RTO). The RPO determines the maximum amount of data an organization can afford to lose following a data breach or outage. The RTO, on the other hand, sets the maximum time period for restoring normal operations after a data loss or outage.

The lecture discusses different types of recovery methods for different types of data. It mentions file/folder/object recovery, image recovery, virtual machine disk recovery, bare metal recovery, instant recovery, and replicas. Each method has its own purpose and is suited for specific data recovery needs.

This lecture discusses recovery procedures and the importance of testing and reviewing backup systems. It emphasizes the need for two types of backup: persistent data backup and system state backup. It suggests integrating the backup process directly into the CI/CD pipeline and mentions the availability of backup and restore capabilities provided by cloud providers like AWS and Azure.

The lecture discusses the importance of having a comprehensive checklist for a backup plan. It suggests creating a document for each service layer that includes an architecture diagram showing redundancy, SLAs, recovery objectives, backup and recovery procedures, and failure monitoring. It also emphasizes the need to identify when backups should be used and who the system experts are for emergencies. Additionally, the lecture recommends documenting cross-system dependencies, contact information, and dependency types. The lecture also highlights the importance of organization policies for annual testing, approved backup utilities, outage management, and communication standards.

This lecture provides tips to avoid common mistakes in backup in DevOps. The tips include testing backups regularly, keeping a backup strategy in place, securing backups, and minding the recovery time objective (RTO) and recovery point objective (RPO). Testing backups ensures they are working properly and data can be restored. Having a backup strategy is important as relying solely on DevOps practices may lead to data loss. Automating backup processes reduces the risk of errors. Securely storing backups protects against data theft. Lastly, considering RTO and RPO helps determine backup frequency and data recovery speed, preventing extended downtime and revenue loss.

This lecture discusses the differences between data backups, replications, and snapshots. A backup creates a replica of data and allows for restoring specific files to a previous point in time. Replication involves making copies of data and distributing them across different sites to ensure continuous operation of critical applications. Snapshots are metadata-based records that save the entire instance of a virtual app, disk, or system and can be used to restore servers and virtual machines in the event of data loss.

Tthe lecture discusses the main mission of a disaster recovery plan (DRP), which is to ensure a rapid restart of operations and backing up vital infrastructure. The DRP requires careful risk mapping, data redundancy, and specification notes to determine critical IT applications and backup systems. Regularly updated measures are also essential for an effective DRP. As well the difference between backup and disaster recovery is considered.

The lecture covers six big steps to create a great Disaster Recovery Plan. First, check official recommendations for activity recovery, especially for regulatory obligations like banks. Second, define responsibilities for plan implementation, with one person in charge. Third, conduct an audit of infrastructure, systems, and backups. Fourth, rank critical IT activities using risk management. Fifth, plan and estimate resources and time needed for implementation. Lastly, regularly test the DRP through real-life or simulation exercises. Netflix uses Chaos Monkey software for extreme testing.

The lecture covers big steps to create a great Disaster Recovery Plan. Fifth step, plan and estimate resources and time needed for implementation. Lastly, regularly test the DRP through real-life or simulation exercises. Netflix uses Chaos Monkey software for extreme testing.

In this lecture, we will go through a checklist for creating a DRP based on 14 topics that I recommend to consider.

The lecture focuses on the importance of a disaster recovery plan for businesses, especially small ones. The lecture emphasizes that creating a DRP is a resource-intensive endeavor, though it may vary depending on the size of the infrastructure. It also highlights the importance of keeping the plan simple.