TDD – Trust Driven Development
summary
Claim: building everyday trust — shown as competence and character — lets teams remove manual approvals and shorten lead time. Uses Value Stream Mapping, DORA metrics (deployment frequency, lead time, MTTR, change failure rate), CI/CD, pair programming and feature flags as concrete tools. Gives concrete pain examples: two devs left 100 comments in a PR, product owners sitting on 100 tickets for manual approval. Shows practical wins: deploys to prod behind flags and faster releases once cognitive and emotional trust is established.
AI-written summary · about
chapters (14)
- 0:00Introduction to Trust Driven Development
- 1:07Trust in agile
- 3:37Trust pillars
- 6:11Cognitive and emotional intelligence
- 8:41Breaking silos
- 12:56Daily trust moments
- 15:05Trust in pair programming
- 18:22Trust in backlog & deployments
- 19:49Vulnerability and innovation
- 23:17Vulnerability in scrum
- 25:01Trust as a choice
- 26:29Metrics vs trust
- 30:26Secure environments
- 31:09Long-term trust benefits
related talks
47mTDD + BDD = TBD (Tests, Business, Development). A Triad of Engineering Culture
37mTDD - the why, the how and the when not
31mTDD: Are you sure about that?
21mHow TDD and CDD make your apps suck less
39mTDD as in Type-Driven Development
35mStrategic TDD
16mNot Really a TDD Person? Come Discover Canon TDD
45mTDD makes you a better everyday developer