Tools and methods are killing your products
summary
Claims that tooling and methods often replace product judgment: teams chase Sprint goals and get trapped in a Scrum pendulum, product owner becomes a single point of failure, and teams never measure real outcomes (suggested metrics: a 4‑star App Store rating or reduced support calls). Issue trackers like Jira's hammer store tasks without context—uploader urges adding user research and future product sketches. Continuous delivery becomes a swamp of continuous delivery when pipelines force premature handoffs or desynchronized teams. Prototypes can mislead when unrealistic for budget or tech.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 5:33The 4 symptoms
- 7:06My story
- 10:00Scrum Pendulum
- 17:40Giras Hammer
- 24:57Swamp of Continuous Delivery
- 25:14Great Game
- 32:46Prototypes
- 34:32Relevance
related talks
51mDon't Kill Agility with Agile Processes
40mRegain Benefits from Agile Software Development
34mBuilding a Culture For Developer Productivity
59mHow to Fix Your Failed Agile Transformation
45mAccelerating Software Delivery: Why Your Team Is Slowing Down
52mUnderstanding UnHealthy Syndromes of Software Delivery
51mDeveloper productivity is waste
11mThe key to solving the conundrum of software estimation