✊ Join the DEV-olution: A Culture of Empowered Developers
summary
Argues that developer culture improves when teams get measurable autonomy and simple rituals: use Compass scorecards and an opportunity score to spot wait time (31% name it top issue), run 10% time for improvement vs 55% building and max 35% “keep the lights on,” and run demo videos (goal 5,000 in 2024, +50% engagement) via Loom and Atlas. Introduces a feature lead plus buddy, a DAISY decision page (driver/approver/informed/contributors), and reports a 27% bump in team connectedness after intentional togetherness.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:27From waterfall to agile
- 6:45The problem with over-standardization
- 8:10Empower developers to act
- 10:57Top developer challenges
- 13:04Measuring developer experience
- 15:55Building a culture of improvement
- 19:06Product engineers bridge gap
- 22:59Feature lead process explained
- 28:17Cross-team collaboration
- 30:02Demo culture and async feedback
- 36:04Decision-making with DAISY
- 40:19One-page meetings
- 44:12Team cohesion and connection
- 47:44Celebrating team wins
- 51:37Healthy team values
- 56:09Balancing autonomy and standards
- 58:59Call to action
related talks
45mDeveloper Joy – How great teams get s%*t done
44mDeveloper Joy – How great teams get s%*t done
34mBuilding a Culture For Developer Productivity
50mDeveloper Joy – How great teams get s%*t done ( Closing Keynote)
48mDeveloper Joy – How Great Teams Get s%*t Done
02h 23mDeveloper First: A New Leadership Mindset
33mMeasuring Developer Productivity: the good, the bad and the data
25mDeveloper Joy – How great teams get s%*t done