Instilling a Culture of Craftsmanship
summary
Culture change focuses on concrete practices: start with code reviews start the change to teach patterns and mentorship, prioritize readable maintainable code over “correct but unreadable” shortcuts, and treat tests as a tool not a silver bullet—enforce require tests in every PR while not mandating TDD. Give teams 10-20% slack capacity for learning, read and fix vague backlogs, and align incentives so senior engineers are rewarded for growing team output rather than raw story count.
AI-written summary · about
chapters (15)
- 0:00Introduction and speaker intro
- 1:06Who I am and my background
- 2:52Agile founders and craftsmanship bridge
- 4:44Test driven development limitations
- 6:52Code reviews and craftsmanship foundations
- 8:17What is a software craftsman
- 10:02Clean code principles
- 12:51Testing and testable architecture
- 14:56Slack in agile and craftsmanship
- 16:28Organization and leadership in craftsmanship
- 17:32Vision and roadmaps for craftsmanship
- 18:55Scrum masters and product owners as team members
- 20:58Incentives for craftsmanship culture
- 23:46Backlog clarity and business alignment
- 25:12Craftsmanship manifesto overview
related talks
52mSecrets of a Strong Engineering Culture
21mEngineering Culture: A Shared Build
22mDo We Need Software Craftsmen?
38mBuilding a Strong Engineering Culture – Chuck Greb
42mBuilding a Strong Engineering Culture – Stacy Devino
46mLearning to Lead a Craft Team: Year One.
51mFed up with software craftsmanship
29mCreating a Code Review Culture