Numbers, because metrics matter
summary
Company focuses on measurable changes: enforces 100% test coverage using SimpleCov + Travis CI, adds Code Climate to flag complexity, and raises velocity from about 15 to ~70 story points per week. Design feedback moves to Dribbble to get peer critique, Facebook success measures interactions not likes, and monthly goals assign one person responsibility so missed targets are visible. Pair programming cuts update time, feedback rounds drop toward zero, and the team treats awards as paid submissions rather than a true quality signal.
AI-written summary · about
chapters (17)
- 0:00Numbers, because metrics matter
- 1:27CONFERENCES MADE ME CRY
- 2:40WHATS IMPORTANT?
- 6:33AWARDS & BLOGS
- 7:28MEASURING QUALITY?
- 8:37SIMPLECOV
- 10:12TRAVIS CI
- 11:43CODE CLIMATE
- 12:10SCRUM
- 12:41DEFINITION OF DONE
- 14:00VELOCITY
- 14:50MEASURING BEAUTY?
- 17:11FEEDBACK ROUNDS
- 18:05USER FEEDBACK
- 23:21DEVELOPMENT
- 25:50SOCIAL
- 28:19EASY!
related talks
23mEvaluating your team's success as you grow
41mRethinking Measurement for High-Performing Teams
23mMeasure for change
44mHelp! My manager is asking me for KPIs !
18mAgile leadership and technical mastery, a harmonious alliance
39mDev Team Metrics that Matter
47mHow to win in software development with tighter feedback loops
26mEngineering metrics, minus the creepiness