?????? How Endurance Training Taught Me Agile

It was Thanksgiving week, marking the start of my triathlon off-season. Scrolling through my training team’s chat, I noticed many teammates planning their training for Ironman 70.3 Galveston—and they were nudging me to join.

At first, I wasn’t interested. But then, Black Friday hit—and suddenly, my social media feeds were flooded with ads for the race. In a moment of impulse, I registered.

With the support of my teammates, I started training for the 1.2-mile swim, 56-mile bike ride, and half-marathon run. Endurance training demands structured, progressive improvement, so I incorporated interval training—alternating between high and low intensity.

Then, around week three, my Agile mindset kicked in. I started spotting parallels between endurance training and managing a Scrum project. Here are seven key lessons I discovered:

?? 1. Sustainable Pace Over Speed

In my first triathlon, I went all-out from the start—and burned out fast. Agile teams must balance velocity and sustainability to avoid exhaustion and maintain long-term success.

?? 2. Incremental Progress Leads to Big Wins

Triathlon training follows a structured, gradual improvement plan. Similarly, Agile thrives on small, iterative releases, leading to continuous improvement and greater impact.

?? 3. Adaptability is Key

Race conditions are unpredictable—weather shifts, mechanical issues arise, and energy fluctuates. Agile teams face the same uncertainty. Success comes from adjusting strategies and embracing change.

?? 4. Retrospectives Are Essential

After each race, I analyze nutrition, pacing, and transitions to determine what worked and what didn’t. Agile teams do the same through retrospectives, process refinement, and waste elimination.

?? 5. Mindset Determines Outcomes

Endurance sports are as mental as they are physical. Staying resilient during tough moments makes all the difference. Agile teams thrive with a growth mindset, tackling challenges head-on.

?? 6. Measure What Matters

I don’t just track miles—I measure pace, heart rate, power output, and recovery time. Agile teams should focus on cycle time, lead time, team velocity, and defect rates, not just story points.

?? 7. Never Try Something New on Race Day

I tested nutrition, pacing, and gear during training, never on race day. Agile teams should experiment in sprints, prototypes, and beta releases, not in production when stakes are high.

?? What about you? Have you ever applied lessons from sports or endurance training to your work? Let’s discuss it! ??

?