Developer productivity 2.0
summary
A survey of engineering teams (75 detailed responses, ~100 pages of notes) finds concrete patterns not slogans: small teams with clear goals outperform process-heavy ones, Skype’s Xbox client ships under tight deadlines and hits one million users day one, WhatsApp succeeds without Scrum, and vendor dashboards that score commits often backfire. Actionable moves are ask teams what blocks them, remove biggest timewasters, invest in platform leverage and iterate continuously.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:23Developer productivity 2.0
- 2:55Three stories on developer productivity
- 11:06What makes productive teams? A survey.
- 16:28slack
- 19:10Why is developer productivity such a hard topic?
- 26:06What are things that DO work?
- 29:59Take your team on the journey with you
related talks
34mBuilding a Culture For Developer Productivity
27mDevelopers Expose What's Breaking Productivity in Their Companies
13mDeveloper Satisfaction = Better Code | Here's Why
33mMeasuring Developer Productivity: the good, the bad and the data
52mDeveloper Joy – How great teams get s%*t done
58mDeveloper Joy – How Great Teams Get S%*t Done
26mDeveloper Joy – How Great Teams Get s%*t Done
48mDeveloper Joy – How Great Teams Get s%*t Done