A FAST Way To Scale
summary
FAST organizes large product groups into a single collective that meets twice weekly in a 10–20 minute fast meeting where product priorities are stated, team stewards commit to specific “valuable increments,” and people self-select and steward teams. Work lives on a Miro “team room” with task maps (one‑ to two‑day user stories, hour‑long tasks, icons showing who’s working). Results: delivery moves from every 2–3 months to weekly, adoption of the meeting takes 2–4 weeks, collective ownership 2–5 months; a 300‑person org can need ~42 small teams unless teams scale vertically.
AI-written summary · about
chapters (14)
- 0:00Scaling software orgs
- 1:49Component teams problems
- 2:54Feature teams limits
- 4:18Team topologies challenges
- 6:08Vertical vs horizontal scaling
- 8:19Why vertical scaling works
- 9:43How FAST meetings work
- 12:31FAST in action
- 18:47Q&A on FAST logistics
- 27:32Release planning in FAST
- 31:44Teamwork challenges in FAST
- 38:24Q&A on teamwork & timelines
- 41:36Results & FAST adoption
- 45:27Conclusion & call to action
