Innovate or keep maintaining legacy
summary
Claims that reserving one day every two weeks or a dedicated IP iteration inside SAFe produces tangible results, not just ideas. Examples: teams build a proof of concept to enable live migrations during the week instead of weekend downtime and deploy it successfully with customers unaware. Practices used: retrospectives, problem‑solving workshops, a simple Kanban, notebooks, communities of practice and an internal innovation accelerator that this year funds ~€1,000,000. Management buy‑in shifts after a quarter of demos and measurable time and defect reductions.
AI-written summary · about
chapters (11)
- 0:00Introduction to innovation
- 2:30Legacy systems and barriers
- 5:24Team success with proof of concept
- 8:17Safe framework for innovation
- 10:20Tools for daily innovation
- 13:50Innovation accelerator programs
- 15:34Leadership buy-in for innovation
- 18:03Reflection and improvement cycles
- 20:54Hidden innovation success story
- 22:58Embracing failure for innovation
- 23:39Q&A and closing remarks
related talks
01h 00mBeyond the innovator’s dilemma
41mThree years with SAFe: this is what stands out
24mInnovating Beyond Hackathons
51mSabotaging a Transformation
43mMind the gap – incorporating the change agenda into scaled Agile.
44mMoving Beyond Agile? Modern Methodologies for Technology Development
53mOur SAFe journey to follow the sun
38mScaling Continuous Improvement mindset and making it stick