How Engineering Teams can Plan Remotely
summary
Argues teams plan asynchronously by writing decisions into shared artifacts, keeping everything editable and assigning one DRI for execution; contrasts fixed time sprints with fixed scope (use kanban for MVPs). Recommends a demo scorecard that scores end-to-end workflow steps over dates and feeds burn‑up charts, tracks merge request rate as throughput, defines priority/severity with SLAs, sets budgets for bugs versus features, and runs monthly releases (22nd) instead of cooldowns.
AI-written summary · about
chapters (10)
- 0:00Intro
- 1:52Design asynchronous workflows
- 2:41Fixed time vs fixed scope
- 5:18Demo scorecard
- 8:48Optimizing for predictability
- 10:53Setting budgets
- 11:52QA
- 13:28Silos
- 15:09Standups
- 16:11Challenges
related talks
13mHow remote engineering teams stay agile
36mHow YOUR scrum team can excel in a remote setting
50mScaling Teams Through Remote Work
44mEnhancing the Performance of Engineering Teams
23mManaging diverse engineers for high-impact deliveries
40mThe Joys of Managing Engineering Teams
46mLeadership for Engineering Teams in Remote Work Era | Panel Discussion
43mScaling Yourself for Managing Distributed Teams...