Agile Panel
summary
Scrum often fails because organizations install rituals without changing roles, coaches generate dependencies and middle managers resist being flattened; measure cycle time, customer happiness and employee morale before and after change instead of blaming the method. SAFe works as a bulky transition tool — SAFe as transitional methadone — but is not the same as agility. No‑code is largely drag‑and‑drop programming that shifts work toward platform builders — no-code is drag-and-drop coding — and planning under deep uncertainty relies on goal‑based targets and faster, smaller launches.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:55Why is agile development so difficult to implement?
- 8:00What's the point of DevOps?
- 13:18Misconceptions about SAFe
- 27:00Impact of No-Code/Low-Code
- 31:31How to approach planning in uncertainty
- 34:35How to know if an organization is agile
- 40:50Does agile development work in all SW companies?
- 42:12Diversity in teams
- 50:05Are Certified Scrummaster trainings still legit today?
- 51:55Why is agile not scalable?
- 57:37Outro
related talks
49mAgile is a Dirty Word
26mAgile Transformations are not about software
51mDon't Kill Agility with Agile Processes
01h 04mIs Agile Still the Answer? Lessons from Real World Agility
48mAgile is STILL a Dirty Word!
34mAgile-battle
01h 33mPanel - Predictability and Productivity...Does Agile Help?
43m#NoFrameworks: How We Can Take Agile Back!