Team transformation to accelerate value delivery
summary
Six-person remote product team formed in 2021 reduces sprint carryover by changing the definition of done to split work into implementation story with points plus a zero-point PR tracker task, runs story-points training and retrospectives every four weeks, and experiments (one-card commit) that move velocity from committed 43 to delivered 30 then to committed 29 delivered 34. Uses Scrum cadence, Slack for async coordination and two weekly one‑hour syncs; result is steadier capacity, fewer blocked PRs, and movement from norming toward performing with more predictable, sustainable delivery.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:06Change and transformation phases
- 4:38Foundations for success
- 7:50Agile principles and culture
- 9:13Team structure and remote challenges
- 10:16Team development and performance
- 12:26Key challenges
- 17:04Capacity planning and workflow
- 19:57From guidance to self-driven
- 21:01Operational realities and pace
- 23:15Lessons learned
- 25:23Building high-performing teams
- 26:24Q&A
related talks
22mOptimizing Product Development: Balancing Speed, Quality, and Process
44mScaling Agile With a Super-Effective Global Delivery Machine
45mSoftware delivery with skills-based, self organising teams
18mAgile leadership and technical mastery, a harmonious alliance
45mFrom 5 to 100 in Product Development team in just 5 years
51mSabotaging a Transformation
52mShifting into continuous delivery
35mBuilding and Growing an Agile Team