From Software to Product Developers
summary
The talk describes how Audiense transformed from a traditional development setup—long sprint plannings and handoff-style User Stories—to a unified Product Developer model where planning takes 15 minutes and development and product work as a single team. It explains the practices and team dynamics used to adopt that Product Developer philosophy in their product team.
AI-written summary · about
chapters (24)
- 0:00Welcome
- 3:32Product developer definition
- 5:20Delivery region: past and problems
- 8:55Delivery region: TDD and CI/CD improvements
- 12:49Definition and planning: early challenges
- 14:17Refinement with shirt sizing
- 18:42Abandoning estimates and learning culture
- 23:18Discovery region: user focus
- 24:22Product spikes and three amigos sessions
- 27:53Product vs software developer philosophy
- 28:37Validation and metrics with real users
- 31:04Journey summary and hiring
- 31:46Team structure changes
- 33:14Stop estimating: the key leap
- 34:37Manual testing and production validation
- 36:03Product development benefits
- 37:51Multidisciplinary profiles and knowledge
- 40:23Efficient refinement and flexible sessions
- 42:08Trunk based development and feature flags
- 44:35Mono repo and product architecture
- 46:09Evaluation and continuous improvement
- 48:14Q&A part 1
- 51:27Design team integration
- 52:57Team evolution and scalability
related talks
48mHAMMERS AND NAILS
34mBuilding a Culture For Developer Productivity
46mScaling Agile in your Organization with the Spotify Model
28mBoosting Developer Platform Teams with Product Thinking
45mFrom 5 to 100 in Product Development team in just 5 years
31mTransitioning from Project to Product: An Experience Report
43mPerspectives on Effective Product Development Culture
38mBreaking Down Silos Between Platform and Product Teams