Easier to read with cream paper, a tint, more contrast or larger text? Choose your colours and text, once, for every page.

Preview

DI 2.21: DevOps: aims and benefits

This is the first page of the lesson. Read it and have a go at the activities. The rest is in the full lesson.

45 minutes

Fifty minutes, or ten

A team releases an update by hand. It takes fifty minutes of careful clicking, and once in a while someone makes a mistake.

Another team has a pipeline. The same release takes ten minutes, and nobody clicks anything.

Why would a company want the second way?

Key words

WordWhat it means
Agileworking in small steps, with regular feedback
Aimthe goal that a way of working is trying to reach
Benefita good result that comes from doing something
Buildturn the saved changes into a version that can run
Releaseput a version in front of its users
Productivityhow much useful work gets done in the time available
Scalabilitybeing able to grow to meet more demand
Automationgetting a computer to do a repeated job
Human errora mistake made by a person, such as a missed step

The cells students fill in are left blank in this preview.

By the end of this lesson

Note

I can state the two aims of DevOps and explain five benefits with examples.

Starter

Have a go

Starter

3 questions
Have a go: your answers are marked here and then forgotten. Sign in if you would like your score kept, and to pick up where you left off.Sign in to keep your score

Your answers are marked here and are not kept. A college account keeps every student’s marks.

The two aims

DevOps has two aims.

  1. Deliver in an agile way: small steps, regular releases and quick feedback, so the system keeps up with what people need.
  1. Build, test and release changes: do all three in a smooth, repeatable way, not as a rare scary event.

Five benefits

BenefitWhat it meansExample
Rapid deliveryNew things reach users sooner, helped by automationA fix goes live in an hour, not a month
Increased productivityPeople spend time on thinking, not on repeated clicksA technician writes one script, not forty manual changes
Better processes across teamsDevelopers and operations share steps and goalsOne shared checklist for releases
ScalabilityThe system can grow when demand growsServers are added by script before a sale
Fewer errorsAutomatic steps are the same every timeNo missed step at 2 am

The cells students fill in are left blank in this preview.

Check

Have a go

Check

4 questions
Have a go: your answers are marked here and then forgotten. Sign in if you would like your score kept, and to pick up where you left off.Sign in to keep your score

Your answers are marked here and are not kept. A college account keeps every student’s marks.

The lesson goes on

6 more parts of this lesson are in the full curriculum, with the tasks, the final check and the labs. A college account gives your students all of it.