Untitled Quiz

ITIL Evolution

• ITIL 3 defined Problem Management as a function within IT Service Management (ITSM)
• In ITIL 4, this function evolved into "Problem Management Practice"
• The objective of Problem Management Practice in ITIL 4 is to deliver problem management outputs effectively
• The change in ITIL 4 focuses on collaboration and value delivery efficiency

ITIL Principles

• There are seven guiding ITIL principles.
• Focus on Value: Organizations should ensure all actions deliver value to stakeholders, especially customers.
• Start Where You Are: Utilize existing systems and processes as a foundation for improvement.
• Progress Iteratively with Feedback: Break down tasks into smaller, manageable steps and gather feedback after each step.
• Collaborate and Promote Visibility: Foster an environment of collaboration and transparency within the IT team.

DevOps Concepts

• Represents a set of principles and practices that aim to streamline software development and deployment.
• The DevOps methodology emphasizes collaboration, automation, and continuous improvement.

Three Central Elements of DevOps

• People: A DevOps team consists of diverse professionals who contribute to all stages of the software lifecycle.

  • Product Owner: Responsible for the product backlog.
  • Developer: Creates code and performs unit testing.
  • Tester: Develops and executes test scripts.
  • Architect: Designs software architecture.
  • IT Security: Manages IT security aspects.

• Process: The DevOps process revolves around a Continuous Integration and Continuous Delivery (CI/CD) pipeline, composed of:

  • Continuous Integration (CI): Automates code integration, testing, and builds, minimizing errors.
  • Continuous Delivery (CD): Automates deployment to the test environment, requiring human intervention for production deployment.
  • Continuous Deployment (CD): Automates deployment to production, building upon Continuous Delivery principles, with a complete end-to-end automated approach.

• Technology:

  • Choice of tools is crucial for success.
  • Tools can vary depending on the technology stack and specific needs of the organization.
  • Examples of widely used source code repositories include Git and Subversion.
  • Git is a Distributed Version Control System (DVCS), allowing developers to work on the entire codebase independently.
  • Subversion is a Central Version Control System (CVCS), requiring developers to check out, modify, and check in code to a central server.

DevOps Principles (CALMS)

• Culture: Fosters a blameless culture where everyone takes responsibility for the product as a whole.

  • Encourage taking ownership beyond individual tasks.
  • Promote innovation and stepping outside comfort zones.
  • Emphasize communication, collaboration, and teamwork.
  • Value experimentation and learning from mistakes.

• Automation: Automates repetitive tasks for increased efficiency and speed.

  • Aims to reduce manual intervention and errors.
  • Cloud infrastructure provides faster server creation through code.

• Lean: Adopts the Lean philosophy to streamline processes and eliminate waste.

  • Focus on simplicity and straightforward approaches.
  • Reduce waste through optimizing processes and eliminating defects.

• Measurement: Emphasizes data-driven decision-making and continuous improvement through monitoring and feedback.

  • Use metrics to track progress, identify areas for improvement, and measure the effectiveness of changes.
  • Implement monitoring tools to track application and infrastructure performance, alerting on warnings or exceptions.

• Sharing: Promotes collaboration, knowledge-sharing and a culture of learning.

  • Encourages sharing knowledge, experience, ideas, and best practices.
  • Fosters collaboration and teamwork among team members.
  • Reduces silos and promotes a sense of shared understanding.