How Agile broke peace in steady Casino Business
summary
Company switches from waterfall to scrum and aims to release every two weeks even though tech and automation lag, so teams prepare but cannot actually ship that fast. Iterations deliver finished features with a stricter definition of done = done done done, giving earlier market feedback and more even workload. Certification is split so a big game’s launch window drops from seven to three weeks by shipping parts. Pain points: fake-scrum habits, resistance to role changes, and slow T-shaped skill growth.
AI-written summary · about
chapters (7)
- 0:00Casino industry and Agile
- 3:19Casino industry and video slots
- 17:38Traditional vs Agile methods
- 23:35Agile roles and team structure
- 30:32Transition to Scrum
- 35:41Agile adoption challenges
- 42:34Q&A
related talks
05mFrAgile - lessons from a failed agile transformation
39mScrum at Scale
26mAgile Version 2016
44mCan you be agile and compliant?
40mAgile is Broken & It’s the Product Manager’s Fault
47mAgile experience in changing environments and the challenges faced
37mFrom Waterfall to Agile
40mAgile Software Development: Practice and Analytics
