Lightning Talks

on YouTube ↗11m

" summary

Calls to question default practices lead with no estimates as a prompt to audit habits and assumptions, not just rename ceremonies. Multiple teams report three years of trying agile while losing technical depth, and a core banking example shows inability to deliver features incrementally — account opening, interest, reports arrive in separate releases — framing core banking release constraints. Advice centers on tying processes to engineering practices, avoiding copy‑paste adoption, and investing in high-performing teams plus leadership alignment for sprints to work.

AI-written summary · about

" chapters (13)

1. 0:00No Estimates assumptions
2. 0:47New skills for future
3. 1:29Agile speed vs technical depth
4. 2:12Agile transformation success
5. 2:54Engineering to agile execution
6. 3:14Agile India impact
7. 3:57Thoughtful agile application
8. 4:39Session scheduling challenges
9. 5:46Context-first agile approach
10. 6:50Behavioral change in agile
11. 7:12Educating business on agile
12. 8:16High-performing agile teams
13. 9:40Leadership for agile success

" related talks

• 43mWhy Agile transformation failStephen Marjot, Katrina Warren · Agile en Seine 2021
• 40mAgile Software Development: Practice and AnalyticsSzymon Kikla · GDG DevFest Gorky 2017
• 51mDon't Kill Agility with Agile ProcessesAino Vonge Corry, Troels Richter · GOTO Copenhagen 2014
• 38mPolyglot AgileAino Vonge Corry · GOTO Chicago 2018
• 32mA Tale of Two Cities - Early Adoption StoriesScott Duncan · Agile Roots 2010
• 39mSoftware CraftsmanshipSandro Mancuso · AgileByExample 2013
• 26mAgile Transformations are not about softwareTomasz Maj · Agile Swarming 2023
• 42mWhat your mother never told you about agile developmentAino Vonge Corry · Agile meets Architecture Berlin 2022