Shifting into continuous delivery
summary
A product org shifts from a feature factory into cross-functional teams with living team charters, adopts dual-track agile and outcome-focused goals, and runs discovery on a separate Kanban with On Deck / In Progress / Learnings / Validated columns (snapshot: five validated, 23 learnings). Experiments run through Customer.io and Pendo, with a cadence to ideate/build/launch; one month produces seven experiments and beats the KPI target by 260% (example goal: lift poll creation to 3.27%).
AI-written summary · about
chapters (22)
- 0:00Introduction
- 6:25Breaking it up by quarters
- 6:42Product engineering organization
- 7:50Discovery work
- 8:49Pros and cons
- 9:44Team charters
- 10:55Product teams
- 12:06Collaboration dynamics
- 13:10Team charter
- 14:22Q1 outcomes
- 16:24Outcomefocused goals
- 21:05Discovery card template
- 23:04Outcome vs output goals
- 24:29Building metrics
- 28:05Lessons learned
- 32:21Design sprints
- 33:23Experiments
- 35:48Roles
- 38:06Experimentation
- 40:08Weekly cadence
- 43:19Summary
- 45:16Questions
related talks
59mThe continuous culture
44mDual-Track Agile for Discovery & Development
22mOptimizing Product Development: Balancing Speed, Quality, and Process
31mThe Continuous Culture
30mDelivering Features VS Delivering Impact
33mSoftware development practices for companies that want to make an impact
32mContinuous Product Discovery: how to systematically de-risk changes...
37mLeading the Transformation (Applying Agile & DevOps Principles at Scale)