How to get it right by being wrong all the time
summary
Neo is a small product built inside Sab to test a new BaaS and recruit younger customers; the team implements trunk-based development (Bitrise for mobile builds), automated CI/CD into GCP with Terraform, contract testing and a pre-push hook after a broken-main incident, and replaces a long backlog with concrete user stories and paired work. The claim: iterate quickly, expect to be wrong, and improve the system — results so far are pilot customers, spreading practices across Sab and a planned second team.
AI-written summary · about
chapters (26)
- 0:00Introduction
- 1:07About Sab Neo
- 2:22The challenge
- 3:54Mission statement
- 4:36Product manager
- 4:54ISB
- 5:14Help others improve
- 5:31Change the organizational structure
- 5:48Show the numbers
- 6:19The only way
- 6:51Agile Manifesto
- 12:13How to form an autonomous team
- 14:48Risk compliance
- 16:02McDonalds principle
- 17:51Being wrong
- 18:40Trunkbased development
- 21:40Constant improvement
- 22:09User stories
- 22:26Backlog
- 22:47Requirements
- 23:47User Story
- 25:13Storytelling
- 26:47Kinemen Framework
- 30:16The story of Neo
- 32:42Questions
- 40:13Overpromising
related talks
20mDoing the wrong things in the right way
18mAgile leadership and technical mastery, a harmonious alliance
01h 03mBeyond the innovator’s dilemma
27mFinding balance
20mDoing Things the Hard Way
15mThe agile leadership mindset: Embracing continuous change as a leader
52mLessons learned hiring as a teamwork
25mAgile: The Bad Parts - Matt Parker, Martina Hodges-Schell