How to stop the weaponizing of Agility practices in the workplace
summary
Claims that agile language is used as a weapon: "that's not agile" to shut stakeholders, MVP abused to justify cutting due diligence, and planning poker/story points split to create silos rather than collaboration. Evidence: daily standups become micromanagement, velocity is used as a whip, teams are moved constantly so IP and learning vanish. Prescriptions: favour sticky long-lived product teams, stabilise velocity not maximize it, apply theory of constraints, run real retrospectives, coach so consultants become redundant and build T‑shaped teaming skills.
AI-written summary · about
chapters (9)
- 0:00Start
- 10:18The Agile Manifesto
- 12:15The Basics around Agility
- 12:31The Principles behind the Agile Manifesto
- 17:02Product Teams Rather than Projects
- 19:53Estimates
- 34:16How To Measure Teams Efficiency and Maturity How To Create a Healthy Competitive Environment
- 34:31How To Create a Healthy Competitive Environment
- 39:16Elements of Agility
related talks
32mLack of curiosity: The silent killer of agile
15mA Case for Agility
49mNavigating Politics in Agile Lean Initiatives
25mAgile: The Bad Parts - Matt Parker, Martina Hodges-Schell
37mNavigating Politics in Agile or Lean Initiatives
33mEffective Agile Processes: It’s All About People
01h 03mAgility ≠ Speed
05mLightning talk: How to survive in agile world