ICCT logo

Internal academy

ICCT Training Library

Systems & Infrastructure

Cloud and DevOps Delivery

Cover cloud service thinking, deployment pipelines, environment management, and observability so students understand how software moves from laptop to running service.

Intermediate 3 credits 50+ guided hours 5 weeks Modules: 3 Projects: 2

Easy Interactive curriculum

Ops Lab for short, easy-to-digest learning

This course breaks big systems & infrastructure ideas into short missions, plain-language definitions, and interactive practice rounds. Cover cloud service thinking, deployment pipelines, environment management, and observability so students understand how software moves from laptop to running service.

Class missions: 3 10 minutes per topic Lab + quiz + homework + game

Class mission

Cloud service thinking

Minutes: 20

Big idea: Understand the building blocks before you automate them. We keep it simple, hands-on, and easy to explain back.

10 min

Compute, storage, networking, and identity

Identity means the proof of who a user is in a system In this topic we use it for the service layers most teams touch first.

Quick picture: imagine using this in internal app deployment.

Mission: use Identity to practice the service layers most teams touch first.

Identity Cloud DevOps Compute, Storage,
10 min

Environment separation and configuration

Test means a check that proves a feature works the way it should In this topic we use it for dev, test, and production boundaries.

Quick picture: imagine using this in release rehearsal.

Mission: use Test to practice dev, test, and production boundaries.

Test Cloud DevOps Environment Separation

Word wall

Terms made easy

Identity

the proof of who a user is in a system

Cloud

computers and services you use over the internet instead of your own machine

DevOps

the teamwork habits that help code move safely from build to release

Compute, Storage,

one part of the lesson that helps students notice what the tool, page, or process is doing

Lab mission

Lab Mission

Map the cloud services needed for a small student-facing application and explain each choice.

  1. Look at one example from internal app deployment and point to where Identity shows up.
  2. Build one tiny version that uses Identity and Cloud in the right place.
  3. Tell a teacher or partner what you changed, what worked, and what you would improve next.
Homework

Homework: teach Identity in your own words, then create pipeline map with one example, one picture, or one tiny screenshot.

Quick quiz

Check understanding in a friendly way

Game mode

Term Match Sprint

Matches: 0 / 4

Match each word to the right meaning as fast as you can.

Words
Meanings

Pick a word, then pick the matching meaning.

Outcomes

What students should leave with

  • Explain the roles of environments, pipelines, infrastructure services, and monitoring.
  • Map a simple CI/CD flow from change submission through deployment and rollback awareness.
  • Use cloud and DevOps vocabulary accurately when planning or reviewing delivery work.

Reference map

Core topics to cover

Cloud service layers Environments CI/CD Containers awareness Infrastructure as code mindset Observability Rollback planning

Module sequence

ICCT lesson flow

Module 1

Cloud service thinking

Lessons: 2

Understand the building blocks before you automate them.

Compute, storage, networking, and identity

the service layers most teams touch first

Environment separation and configuration

dev, test, and production boundaries

Checkpoint lab

Map the cloud services needed for a small student-facing application and explain each choice.

Module 2

Delivery pipelines

Lessons: 2

Learn the release path from code change to running service.

Build, test, and deploy stages

what each stage protects and why sequencing matters

Release approvals and rollback thinking

shipping safely when changes go wrong

Checkpoint lab

Draft a CI/CD flow for an internal portal update with checkpoints and rollback notes.

Module 3

Running services well

Lessons: 2

Operational work starts after deployment, not before.

Monitoring, logs, and incident signals

how teams know whether a service is healthy

Reliability habits and on-call awareness

response expectations and service ownership

Checkpoint lab

Create a simple operational runbook for launch-day checks and first-hour monitoring.

Capstone prompts

Projects students can actually ship

Release Pipeline Blueprint

Design a delivery workflow for a training portal update, including build, review, deploy, and rollback stages.

Environment Readiness Checklist

Define what must be true before an app can move from testing into production.