Topic
Onboarding & Teamwork
21 articles about Onboarding & Teamwork, newest first.
Browse the complete article archive →Acceptance Criteria vs. Definition of Done: Agree on What Finished Means
Compare acceptance criteria with a shared Definition of Done. Follow one feature through branch checks, integrated evidence, and a separate release decision.
An On-Call Shift Handoff: Transfer Current Risks, Open Incidents, and Next Actions
Transfer an on-call shift with open risks, mitigation expiry, and explicit acceptance. Follow a filled handoff and coverage repair while an incident stays open.
Create a Team Charter That Resolves Purpose and Boundaries
Build a team charter with clear purpose, scope, capacity, and decision rights. Follow a complete platform-team example and three neighboring request decisions.
Create Team Working Agreements for Response Times, Focus Work, and Escalations
Set working agreements for response times, focus blocks, and escalation coverage. See a full agreement and a two-week trial that reveals a real staffing gap.
Cross-Time-Zone Handoffs: Leave Enough Context for the Next Team to Continue
Build a cross-time-zone handoff with context, failed branches, and access limits. Follow a three-region example with scoped receipts and an unresolved case.
Hand Over a Project You Are Leaving Without Losing Decisions or Ownership
Hand over a continuing project with decisions, access routes, risks, and owner acceptance. Use a completed transfer package and four-week walkthrough example.
How to Use an Onboarding Buddy Without Making Them Your Only Source of Help
Use an onboarding buddy for routines and connections. See a question map, bounded buddy agreement, and follow-up that keeps access and technical limits clear.
Interview Internal Users Before Building the Workflow They Asked For
Interview workflow users about recent tasks, exceptions, and workarounds. Use a fictional guide and evidence map before committing to the requested build.
Joining an Unfamiliar Codebase: Build a System Map Before Reading Everything
Trace one codebase journey from entry to output. Use a completed system map and four local fixture runs to separate source relationships, behavior and unknowns.
Map Cross-Team Dependencies Before You Commit to a Delivery Date
Map provider artifacts, interfaces, accepted dates, and capacity before promising delivery. Compare two migration plans and a bounded review commitment.
Pair Programming with a New Teammate: Agree on Roles, Pace, and Learning Goals
Agree on pair-programming roles, pace, pauses and learning goals. Use a session and debrief to distinguish independent understanding from prompted work.
Prepare a PTO Handoff That Lets You Disconnect
Build a PTO handoff with accepted coverage, deferred work, access checks and a clear contact boundary. Follow a full absence plan, rehearsal and return record.











