Development & IT · Day 1 of 2
RESPAWN games.

Six weeks, too many tickets.

Pixel Quest 2 launches in six weeks, and the developers have more work than hours. Today you plan the week with Kai and look at a tool that promises to help.

Kai
KaiLead developer · Respawn Games · direct message
Today
Kai
Kai · Development & IT

Morning, and welcome to Development & IT! I'm Kai, the lead developer at Respawn Games.

Kai
Kai · Development & IT

Pixel Quest 2 launches in six weeks, and our ticket board is much too full. I need someone with a clear head who helps me plan this week and looks at a tool I want to try.

Kai
Kai · Development & IT

Let's start: download your workbook, then go to Step 1. Everything you write goes into your workbook, in the part for Day 1.

Your workbook

Open your workbook for Development & IT and go to Day 1. Keep this page open next to it.

Download your workbook for Development & IT

This file is for your internship in Development & IT, with one part for Day 1 and one part for Day 2. Download it once and use it on both days. The file lands in your Downloads folder.

Step 1 of 3

Two emails in the inbox

Read the two emails in the team inbox in M1. Kai wants to try a new tool, and Emre, the youngest developer, answers him. Find out what problem Kai wants to solve and what Emre is worried about.

M1

Monday, 8:30 a.m.

Two emails in the team inbox
Inbox · dev-team@respawn-games
From
Kai (lead developer)
To
Development & IT team; Jan (Management)
Subject
Six weeks to launch: let's try AutoDev
Sent
Monday, 08:12

Hi team,

we have six weeks until Pixel Quest 2 goes live, and our ticket board is full. This week alone, the open tickets need 51 h of work, and we have 40 h.

I have a trial offer for AutoDev, an AI assistant that writes code for us. It costs €39 per developer per month. The company behind it says that routine tickets get done 30% faster. I would like to start on Wednesday with all three developers. Any objections?

Kai

Inbox · dev-team@respawn-games
From
Emre (developer)
To
Development & IT team
Subject
Re: Six weeks to launch: let's try AutoDev
Sent
Monday, 08:27

Hi Kai,

I have two worries. First, I started here in April, and I learned most of what I know by fixing small bugs. If AutoDev does all the small tickets, which tickets are left for me to learn on? Second, who checks the code that AutoDev writes? Lena, our tester, already works until late at night.

Emre

In your workbook · Day 1 · Step 1
  • Write two sentences. Sentence 1: What problem does Kai want to solve with AutoDev? Use a number from Kai's email. Sentence 2: What are Emre's two worries? Name both.
    Help: “Kai wants to use AutoDev because the tickets need ... hours, but ... Emre worries that ... and that ...”
Step 2 of 3

Plan the week

Kai needs a plan for this week. Read the team's rule in M2 and the ticket board in M3. First read all parts of this step. Then plan the week with the rule from M2 and your decision about T-106 in b). The tickets you choose must fit into 40 h.

Words for this internship
ticket
Aufgabenkarte: one job for the team, written down with all details
bug
Programmfehler: something in the game works in the wrong way
feature
Funktion: something new the game can do
priority
Priorität: what the team does first
estimate
Schätzung: how many hours a ticket will probably take
routine task
Routineaufgabe: a task that many people have solved before in a similar way
code review
Code-Prüfung: a developer reads and tests code before it goes into the game
data protection
Datenschutz: rules that protect the personal data of people
M2

How Development & IT plans its week

The rule of the team

Development & IT builds the game and runs the servers. The team writes every job into a ticket: a bug to fix, a feature to build. There are always more tickets than hours, so the team sets a priority (Priorität). The rule at Respawn: crashes first, then bugs that many players see, then new features. Each ticket has an estimate in hours.

M3

The ticket board

Open tickets this week
TicketWhat happensTypePlayers affectedEstimate
T-101The game crashes in level 12 when a player opens the shop.Crashabout 40,00012 h
T-102The shop shows the wrong price for the “Gold Pack”: €0.99 instead of €1.99.Bugevery player who opens the shop3 h
T-103New feature: a dark mode for all menus.Featurenone yet10 h
T-104The achievement “Speedrunner” does not unlock.Bugabout 10,0004 h
T-105Players with very old phones cannot start the game at all.Crashabout 5,00016 h
T-106A log file (Protokolldatei: a list of what happens in the game) that goes to an advertising partner contains the email addresses of players.Bugnone see it6 h

This week, the three developers have 40 h for tickets together. The rest of their time goes to meetings, tests and the servers.

In your workbook · Day 1 · Step 2
  • Read a), b) and c) below first. Then decide for each ticket: does the team work on it this week, or later? Your tickets for this week must fit into 40 h. Tick one box for each ticket.
  • T-101 · CrashTick one box: This week · Later
  • T-102 · BugTick one box: This week · Later
  • T-103 · FeatureTick one box: This week · Later
  • T-104 · BugTick one box: This week · Later
  • T-105 · CrashTick one box: This week · Later
  • T-106 · BugTick one box: This week · Later
  • a) Write down your tickets for this week in the order the team should work on them, and add up their hours. Example of the form: T-100, T-200 = 10 h
  • b) T-106 is a difficult case: no player sees this bug. Explain in three sentences where T-106 belongs in your plan and why. Say what the rule from M2 does not cover. If T-106 is in this week, name the ticket that moves to “Later”.
    Help for b): “The rule only talks about ... T-106 is dangerous because ... So I put it ...”
  • c) Add one sentence to the team's rule so that the next case like T-106 is clear.
Step 3 of 3

How AutoDev works

Kai wants AutoDev to write code for the team. Before the team decides, find out how tools like this work. Read M4 and the real study in M5.

M4

How an AI coding assistant works

What AutoDev does

An AI coding assistant learned from millions of lines of public code. A developer describes a task, and the assistant suggests code. For routine tasks that many people have solved before, this code often works at once. It knows nothing about Respawn's game, and wrong code can look just as good as right code. So a developer checks every line in a code review.

M5

A real study: faster or slower?

What happened when experienced developers used AI

In 2025, the research group METR tested AI tools with 16 experienced developers. They worked on 246 real tasks in large projects they knew well. Before the test, they expected to be 24% faster with AI. In fact, they were 19% slower. After the test, they still believed that AI had made them 20% faster. Other studies measured big time savings on small, simple tasks.

Source: METR, study published in July 2025

In your workbook · Day 1 · Step 3
  • a) Use M4. Explain in two sentences why an AI coding assistant is often good at routine tasks. Use the term “routine task”.
  • b) Use M5. The developers believed they were faster, but they were slower. Give one possible reason for this. Use what M4 says about wrong code. Two sentences.
  • Kai writes to Jan: “The company says 30% faster. So we save 30% of all our hours. Easy.”
  • c) Use M1 (what the company promises), M3, M4 and M5. Give two reasons why Kai's calculation may be wrong. One or two sentences for each reason.
    Help for c): “First, the company promises 30% only for ... tickets, but tickets like the crashes T-101 and T-105 are ... Second, the study in M5 shows ...”
My notes

What I learned today

In your workbook · Day 1 · My notes

Write three sentences, one for each important thing you learned today, in your own words. For example: how the team decides what comes first, and what the study in M5 found.

Done for today

Check your workbook

  1. Save your workbook.
  2. Choose the file here.
  3. Does the page name a step? Then an answer is still missing or very short. Fill in that box, save the file and choose it here again.
  4. When all answers are there, Kai answers you and the solutions appear under every step.
  5. Compare the solutions with your answers. Is a number or a fact in your answer wrong? Write “Correction:” and the right answer in the same box, under your answer.
  6. Is the answer your own opinion or your own rule? Then more than one answer can be good. Write “Also:” and one idea from the solution that you did not have.
  7. Save your workbook again.