STAGE 08 / CHAPTER 23

Take over and improve the product

Transfer usable knowledge and responsibility. Feed operating evidence into the next release.

Can the receiving team run it without its original author?

Take over and improve the product: input, work and result
Open the diagram for a larger view.

THE WORK TO DO

  1. 01

    Have a capable receiving operator start and restore the product using the handoff package and their own authorized access.

  2. 02

    Assign recurring technical and studio work. Keep support instructions available when the application is down.

  3. 03

    Review observed use and unfinished work. Choose the next outcome, update its rules, and repeat the affected design and checks.

The operating knowledge needs to stay when its author leaves.
The operating knowledge needs to stay when its author leaves.

WHAT YOU LEAVE WITH

A working handoff, acknowledged support coverage, current restrictions, and a prioritized next release.

BEFORE MOVING FORWARD

The receiving side can operate the product without relying on the original developer's memory.

AT THE STUDIOS

The handoff succeeds when another operator can follow it and recover the identified state. A folder of files alone does not establish that result.

Read with the bookChapter 23

WHO DOES WHAT / STAGE 08

Keep the service usable and learn from it.

THE HANDOFF

Observed use + incidents → prioritized work → another checked change

Support and operating observations become owned changes. New changes return through the relevant rule, design, build, and test steps before release.

Work with: Tech Lead, Backend Developer, Frontend Developer, Tester, Security Engineer.

Additional expertise when the work needs it: Site Reliability Engineer, Product Analyst, Product Manager, Data and Database Specialist.

See the team across all eight stages →