Regain Benefits from Agile Software Development
summary
Agile benefits erode when processes and tools replace team collaboration: common failures are every sprint fails, bloated ceremonies, rising technical debt and product owners who can’t say no. Practical fixes shown: use retrospectives that produce concrete experiments, run a “how to make it worse” session to reveal levers, stop treating velocity as productivity and use story points only to trigger conversation, and rebuild mutual support and rapid feedback loops so transparency actually leads to improvement.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 0:40Benefits of Agile
- 3:31Problems with Agile
- 10:38Processes and tools
- 12:33More meetings
- 13:49Not a team
- 16:28Unclear priorities
- 22:04Prioritization
- 23:43Sprint Fails
- 24:30Talk No Action
- 26:09We Dont Have Time
- 27:02We Are Too Busy
- 27:32Velocity as Productivity
- 30:59Measure the Wrong Thing
- 31:57Outcome vs Output
- 33:09Quantity vs Value
- 33:41Agile Manifesto
- 34:43Transparency
- 35:52Tools Processes
related talks
34mFor effectiveness, Agile was never the answer
51mDon't Kill Agility with Agile Processes
25mHow to get your derailed agile transformation back on track
48mAgile is STILL a Dirty Word!
26mOrganizational Dysfunctions - Agile to the Rescue
33mEffective Agile Processes: It’s All About People
01h 01mHow Agile Screwed Up Product Ownership and 5 Things You Can Do to Fix It
36mYou Can't Be Agile If Your Testing Practices Suck