Skip to content
Claim this template

Free course template · Global

Agile delivery, CI/CD and devops basics for software teams

A ready-made course, live deck and two surveys for developers. 40 minutes, 6 lessons. Last reviewed 21 October 2026; not legal advice.

Claim the templatePreview the courseDownload SCORM for your LMS

Free. No credit card. Edit everything.

Play a game from the course

Agile delivery, CI/CD and devops basics for software teams: try 3 questions

Three questions from this course. Pick an answer, then see why.

Play the game

Game not loading? Open it in a new tab (opens in a new tab)

Three pieces that work together

Learners sign in, so every finish and score is recorded. 7 fields to fill in with your details.

Claim the template
The Agile delivery, CI/CD and devops basics for software teams course as a learner first sees it

6 lessons, about 40 minutes

Minutes are an estimate.

  • Lesson 1: A release that had to be rolled back · 7 min

    Before you begin · The Friday release · What went wrong

  • Lesson 2: Agile ceremonies and who owns what · 7 min

    Events and owners · Who owns it? · Check

  • Lesson 3: Continuous integration and delivery · 7 min

    The pipeline · Order the steps · Broken build

  • Lesson 4: Feature flags and safe releases · 7 min

    Flag or branch? · A risky feature · Clean up

  • Lesson 5: Deployment, containers and rollback · 6 min

    Safe deployment · Rollback drill · Check

  • Lesson 6: Retrospective and final assessment · 6 min

    A blame-free retrospective · Raise it early · Practice

Claim the template

Inside this course

Taken from the course itself.

By the end, learners can

  • Describe who owns what in the Scrum events and artefacts
  • Explain continuous integration and delivery and order a release pipeline
  • Decide when a feature flag is safer than a long-lived branch
  • Describe a safe deployment with a tested rollback plan
  • Run a blame-free retrospective that produces one change

Sample questions, with answers

  1. What would best have prevented the long night?

    • Small, frequent, rehearsed releases
    • A bigger release once a quarter
    • Releasing later in the evening
    • Skipping the tests to save time

    Answer: Small, frequent, rehearsed releases. Small releases are easier to understand and to undo, and rehearsal removes surprises.

    Lesson 1: A release that had to be rolled back

  2. Why fix a red main branch first?

    • Every change after it is built on a broken base
    • Red builds are only a colour
    • Tests do not matter
    • It saves disk space

    Answer: Every change after it is built on a broken base. A broken base makes every later result untrustworthy.

    Lesson 3: Continuous integration and delivery

  3. What is the main benefit of merging behind a flag?

    • Small merges, and the feature can be switched off fast
    • The code never needs a review
    • No tests are needed
    • The flag never has to be removed

    Answer: Small merges, and the feature can be switched off fast. A flag separates deploying code from releasing a feature.

    Lesson 4: Feature flags and safe releases

A scenario from "Continuous integration and delivery"

The main branch is red and three people keep pushing.

Best response: Stop, fix or revert first.

Weaker responses: Push on; Disable the test; Ask for a day.

Common questions

Yes. Claiming the template and editing it are free.

Yes. The course is self-paced and online, and the live deck lets you add a live session in the room or online.

At team formation, and when a team adopts a delivery pipeline.

Developers, DevOps engineers and scrum masters; run by engineering managers with L&D.

Record completion in your own LMS or record system, so you can show who finished the course and when.

Your own details, each highlighted inside the course:
  • Link to the change management policy
  • Who to ask for help or to report a concern
  • Where completion is recorded
  • Link to the self-paced course
  • List of approved tools and versions
Then edit anything else you like: wording, scenarios, your logo.
Visit the help centre (opens in a new tab)