In mid-February, my running goals crashed. A severe ankle sprain left me with a strict doctor’s order: zero weight-bearing activity for two weeks. With the Lake Placid Half Marathon looming on June 12th, panic set in. Traditional training plans are rigid—they assume a linear progression of building mileage. But when you are starting from a deficit, rigidity is a recipe for re-injury.
To make it to the starting line, I had to completely change my approach. I stopped thinking like a traditional runner and instead put on my professional hat as an Agile coach and Registered Scrum Trainer. I decided I would implement the Scrum framework in a “Scrum for one” situation to manage my recovery and training.
Not only did I cross the finish line in Lake Placid feeling incredible, but I actually crushed the stretch goal I had set for myself before the injury ever happened. Here is how Scrum, in my team-of-one setting, made the seemingly impossible happen.
The Training Backlog: Breaking Down the Scrum Framework
The Scrum Framework relies on iterative progress, transparency, and constant adaptation. By mapping the core Scrum events to my physical therapy and running schedule, I built a highly responsive feedback loop:
1. The 1-Week Sprint (Training Cycles)
Traditional half-marathon training plans usually lock you into an 11-week or 16-week macro-cycle and typically assume some level of base running as part of your starting point. Instead, I treated every week as a standalone Sprint. A one-week horizon kept me focused entirely on immediate, achievable progress without overextending an unstable joint.
2. Sunday Morning Sprint Planning
Every Sunday morning, I sat down with my coffee to plan the upcoming week’s cross-training and running adjustments. I evaluated what my body could handle and locked in a realistic “Sprint Goal”—whether that meant logging 40 minutes on a stationary bike or testing a 2-mile run on flat pavement.
3. The Daily Scrum (Morning Self-Check-Ins)
Every morning began with a personal Daily Scrum meeting. I evaluated three data points:
- How is the ankle looking (swelling)?
- How is it feeling (pain levels)?
- What is my range of motion today?
If the ankle was talking to me, I adjusted the daily plan immediately to remove that blocker.
4. Saturday Review & Reflect
Saturday afternoon was data night. During my Sprint Review, I audited the hard metrics: VO_2 max trends, resting heart rate, and total minutes spent biking or running. (Big shout out to my Venu 3S from Garmin – helped keep all my data right in front of me, including the super important stress metric, which clued me in when my body was still too stressed in recovery to begin training in earnest. Nope, not an affiliate, just an avid user.)
5. Retrospective
Immediately following the data review, I ran a Sprint Retrospective to look at the qualitative side of training. I asked myself three simple questions:
1 – What went well this week?
2 – What didn’t go so well?
3 – What is one thing I could try that might make things better next week?
The answers directly informed how I could optimize my recovery, sleep, or pacing strategies for the following week.
Inspection and Adaptation Wins Races
I already knew from some previous injuries (especially my torn Achilles nearly 10 years ago!) that when you are recovering from a major injury, your physical capacity changes daily. By using Scrum, I didn’t stress about the workouts I missed in February; I only focused on optimizing the block of time directly in front of me. This iterative adaptation allowed me to safely ramp up my conditioning, pivot heavily into low-impact cycling when needed, and protect my joint health.
This picture is one I took while out on my very first run of the post-injury weeks. It had been months of patient healing and training. I knew ready was a state of mind more than a feeling, but in my Daily Scrums I hadn’t felt “right” yet. Then it was 70 and sunny mid-April when I was in St. Louis to keynote a conference, and rather than walk the course I’d set out for myself, I found myself jogging a few tentative steps. Then a few more, and then, practically leaping for joy for a mile before I reminded myself to focus on my small incremental goals.
If you are facing a massive setback on your own journey, whether fitness-related or something in the workplace, stop looking at the distant finish line. Break your goals down, inspect your progress daily, adapt your plan weekly, and trust the framework. You might just surprise yourself with what you can achieve.
And if you are wondering, “Why Scrum?” In professional settings, like in your nonprofit, you’ll want to check out this FREE recording from my team.
Key Takeaways
- Traditional, rigid training plans can be counterproductive during injury recovery; using 1-week “Sprints” allows for more responsive, safer adjustments.
- Adapting the Scrum framework for a “team of one” enables personal goal management through structured ceremonies like Sprint Planning, Daily Scrums, and Retrospectives.
- Daily check-ins, such as evaluating swelling and range of motion, act as a vital feedback loop to remove physical “blockers” before they cause further injury.
- Using a Sprint Review to audit hard metrics—such as VO2 max trends and stress levels—allows for data-driven decisions on when to push intensity versus when to prioritize rest.
- The core philosophy of “inspect and adapt” transforms the recovery process from a source of stress into an iterative, data-backed journey that can help you exceed original performance goals.