ITIL Q3 Reviewer

Advanced deployment strategies

Safety First, Rollback Capability, Velocity

Safety first

Without breaking user trust

Rollback Capability

Revert a change instantly

Velocity

Enable speed while preserving stability

Blue Green Deployment

Two identical versions. Blue (Live) and Green (Staging)

Canary Deployment

Deploy to a percentage of users.

Intentional debt

Conscious choice to skip perfect code to meet a strategic deadline

Unintentional debt

Results from poor design, lack of standards, or accidental complexity

Liability

When interest exceeds innovation time, the technical practice is in danger of bankruptcy.

80/20 Impact rule

20% of technical debt causes 80% of stability issues

Infrastructure as a Code

No longer pets, they are cattle. Everything is defined in YAML or JSON files.

Architecture Management

Microservices Technicalities. Instead of one big application, we manage 50 small ones.

Tooling

Kubernetes(KBs) is the industry standard Technical Management engine for these architectures.

SRE Motto

Hope is not a strategy. Use engineering tools to solve what was traditionally operations work

AIOps

Using machine learning to detect anomalies in infrastructure before they become incidents

Error Budgets

Amount of unreliability we are allowed to have before we must stop all new deployments and fix the system

Safety First

Moving code without breaking user trust

Rollback Capability

Ability to revert a change instantly if telemetry shows failure

Velocity

Enable speed while preserving stability

Blue-Green Deployment

Zero-downtime transition

Zero-downtime Transition

Once green is ready, the router flips traffic instantly

Canary Releases

Phased Rollout

Phased Rollout

Deploy to a percentage of users

Service Value System (SVS)

How all components and activities work together to enable value creation

Input

Opportunity and Demand

Opportunity

Possibilities to add value

Demand

Desire from internal/external customers

Output

Value

Value

Perceived benefits, always co-created

5 Core Components of the SVS

Guiding Principles, Governance, Service Value Chain, Practices, Continual Improvement

Guiding Principles

Recommendations that guide an organization in all circumstances

Governance

The means by which an organization is directed and controlled

Service Value Chain

A set of interconnected activities performed to deliver a valuable product. Outlines the key activities.

Practices

Sets of organizational resources designed for performing work

Continual Improvement

A recurring organizational activity performed at all levels to ensure performance meets expectations

6 SVC Activities (PIEDOD)

Plan, Improve, Engage, Design & Transition, Obtain / Build, Deliver & Support

Plan

Strategic Alignment, Ensured a shared understanding of the vision, current status, and improvement direction for all four dimensions

Improve

Never Stand Still, Ensure continual improvement of products across all value chain activities

Engage

The Stakeholder Interface, Provide a good understanding of stakeholder needs and good relationships with all stakeholders

Design & Transition

Readying for live, ensuring that products continually meet stakeholder expectations

Obtain / Build

Sourcing the Components, ensuring components are available

Obtain

Buying hardware and software

Build

Developers writing custom Python code for an internal app.

Deliver & Support

Live Operations, ensure services are delivered and supported accdg. To agreed specifications and expectations

Value streams

Specific combinations of activities and practices designed for a particular scenario.

Non-Linear Navigation

Value streams are non linear. Processed at any order and can be repeated multiple times.

Agile Workflows

SVC is non linear, so supports modern Agile and DevOps Methodologies

SVC Format

Step, SVC Activity, Action Example