Erin Sardo LeadDev West Coast 2023
summary
Claims a clear operational role: a Release Captain owns engineering milestones, rollout and rollback plans, and aggregates feature owners rather than doing every task. Concrete tools and practices include project health dashboards, spreadsheets, feature flags (strategies: consolidate flags, pre‑launch, or tie flags), on‑call paging for flag logic, and staged QA environments. Surprising specifics: launches can accumulate ~50 flags, require ~50% of the captain’s time for ~two months (planning often starts nine months out), and need explicit percentage ramp‑up and go/no‑go health checks to avoid catastrophe.
AI-written summary · about
related talks
18mLeading High-Impact Engineering Launches
59mTech leadership, one year after
33mAn Engineering Team Where Everyone is a Leader
34mAn Engineering Team Where Everyone is a Leader
27mLead Lead and Not Lead Follow
23mManaging diverse engineers for high-impact deliveries
23mExtreme Ownership for Global Teams
27mDEVOPS DAYS MTL 2018 - Jesse Hurkens