Moving Beyond Agile? Modern Methodologies for Technology Development
summary
Panel argues that moving beyond Agile means applying concrete practices not dogma: teams replace fortnightly Sprints with continuous weekly check‑ins when delivery flow improves, one case shows two‑thirds of backlog never ships, and scaling lessons come from growing 70 to 2,000 people. Essentials: mandatory retrospectives with one to three actions per iteration, a custodian for Jira/Notion to delete stale tickets, and prefer outcome‑based OKRs over feature contracts.
AI-written summary · about
chapters (16)
- 0:00Introduction and welcome
- 1:06Panelist introductions
- 2:49Agile in startups and scale-ups
- 5:43Dogmatic agile ceremonies
- 8:31Common pitfalls of agile adoption
- 10:54What to avoid in agile
- 13:01Time to master agile practices
- 15:31Retrospectives done right
- 17:00Psychological safety in retrospectives
- 22:39Beyond scrum and kanban
- 25:10Agile in contractual environments
- 28:03Diversity and agile inclusivity
- 30:51Agile for introverts and diverse teams
- 35:26Tyranny of tools like Jira
- 39:40Are we beyond agile yet?
- 43:35Closing and Q&A invitation
related talks
57mModern Agile e o Futuro do Desenvolvimento de Software
43mAgile Outside Technology
25mAgile: The Bad Parts - Matt Parker, Martina Hodges-Schell
51mKeynote: Modern Agile
33mEffective Agile Processes: It’s All About People
40mRegain Benefits from Agile Software Development
34mBeyond Agile: Preparing for Digitalization
01h 22mAgile - The Road Towards Organizational Agility - Progress & Challenges Examined