Agile Evolution: Engineering Visionary Leadership
summary
Argues that engineers lose creativity when agile becomes rigid meetings and prescriptive backlogs and offers concrete fixes: every story in your backlog must state customer value not implementation, push back when it prescribes the how, teach engineers business value (commercial, customer, efficiency, future), involve engineers in early customer planning and use double-loop learning in sprint reviews/retrospectives so teams surface assumptions, change goals, and restore ownership and measurable customer impact.
AI-written summary · about
chapters (16)
- 0:00Agile leadership challenges
- 5:11Engineers as creators
- 7:16Waterfall’s lost passion
- 8:44Agile’s unfulfilled promises
- 12:00Developer disconnection today
- 14:12Backlogs with ‘how’ not ‘why’
- 16:21Teaching business value
- 17:23Purpose in agile events
- 18:28Standups and impostor syndrome
- 19:35Double-loop learning in reviews
- 21:19Retrospectives lacking improvement
- 22:06Evolving agile beyond frameworks
- 23:29Engineers pushing back on stories
- 24:37Engineers from the start
- 25:43Connecting tech and creativity
- 27:53Q&A
related talks
24mBorn Agile: Why Engineers Resist What Comes Naturally
36mAgile Leadership: 3 Keys to Success
40mRegain Benefits from Agile Software Development
13mAgile Architecture: Enabling Innovation in a Rapidly Changing World
01h 01mHow Agile Screwed Up Product Ownership and 5 Things You Can Do to Fix It
01mAgile needs systems thinking
34mAgile-battle
43mAgile Outside Technology