handoff
The point where work, a task or a role passes from one person, team or system to another.
In more detail
Every handoff adds a wait and a chance for context to be lost, which is why DevOps started as an effort to remove the handover between development and operations. Where a handoff is necessary, make it explicit by naming the boundary and what crosses it. During an incident, handing over a role such as incident command should be stated out loud and recorded in the timeline, so work does not disappear when attention moves elsewhere.
Related terms
- DevOps — A way of building and running software in which the people who change a system and the people who keep it running share one goal, removing the handover between them.
- wait time — Time a piece of work spends sitting in a queue, waiting for someone or something, with nobody working on it.
- stream-aligned team — A team organised around one valuable flow of work, such as a product journey, that can deliver it end to end.
- incident commander — The person who coordinates an incident response: assigning roles, making decisions and keeping the response moving, rather than debugging.
- on-call — Being the person responsible, for a set period, for responding when a production system raises an alert, often outside working hours.
Taught in
- Structured Output — AI Engineering: LLM Apps, RAG & Agents
- Grounded Answers With Citations — AI Engineering: LLM Apps, RAG & Agents
- Workflows Before Agents — AI Engineering: LLM Apps, RAG & Agents
- Eval-Driven Development — AI Engineering: LLM Apps, RAG & Agents
- Model-Graded Evals — AI Engineering: LLM Apps, RAG & Agents
- What DevOps Actually Is — DevOps & Site Reliability Engineering
- SDLC: From Request To Running Software — DevOps & Site Reliability Engineering
- On-Call And Incident Response — DevOps & Site Reliability Engineering
- Team Topologies: Stream Aligned And Platform Teams — DevOps & Site Reliability Engineering
- Infrastructure As Code Context — DevOps & Site Reliability Engineering
- Containers And Orchestration Context — DevOps & Site Reliability Engineering
- Pipelines And GitOps Context — DevOps & Site Reliability Engineering
- Observability Context — DevOps & Site Reliability Engineering
- On Call And Incident Command — Full-Stack Observability: Metrics, Tracing & Logging
References
- DORA capability: loosely coupled teams
- Team Topologies: key concepts
- Google SRE book: managing incidents