Strength Training for RHEL Lightspeed: Building Agility, One Rep at a Time
summary
RHEL Lightspeed moves from Kanban to Scrum by phasing in practices: planning, refinement, estimation, then retros and demos, not all at once. Meetings are reduced by reclaiming calendars; no daily standups because Slack keeps work visible. Jira gets tailored with filters and automations — Jira optimizations — to serve the team. A major infrastructure outage forces a 10-day outage recovery with doubled effort for a week but the team ships the summit demo, gains consistent velocity, and starts a planned recovery week.
AI-written summary · about
chapters (17)
- 0:00Welcome
- 1:54Strength training and agile journeys
- 3:19Consistency in transformation
- 5:26Real Lightspeed team
- 6:50Building foundations
- 8:59From foundation to strength
- 11:08Trust and coaching
- 11:31Hyrox race training
- 14:31Race simulation training
- 17:25Race day preparation
- 18:30Final sprint to summit
- 21:02Infrastructure crisis
- 23:15Recovery after launch
- 25:00Retrospectives and growth
- 26:51Agile mindset
- 28:38Closing on discipline
- 30:04Q&A
related talks
32mHow Lean is your Scrum
11mLightning Talks
20mBuilding High-Productivity Teams Focused on Outcomes: Team Design and Collaboration Case Studies
11mLeading Agile Teams to Success: Lessons from the Trenches
16mLightning Talks
40mAgile Software Development: Practice and Analytics
20mRevealing Mechanisms to Create Resilient Teams and the Organizational Culture That Supports Them
15mAdvanced Scrum techniques for optimal delivery
