41:I[185,["/_next/static/chunks/08z4tkzvltetr.js","/_next/static/chunks/121~yigv24_j6.js","/_next/static/chunks/0jo3du-icy6v2.js","/_next/static/chunks/15cy49d~_zsjj.js","/_next/static/chunks/0..ktetnpeix7.js","/_next/static/chunks/08cz-ztcfuxe..js","/_next/static/chunks/0i6hzvr84kc1r.js"],"SendEmailButton"] 43:I[63625,["/_next/static/chunks/08z4tkzvltetr.js","/_next/static/chunks/121~yigv24_j6.js","/_next/static/chunks/0jo3du-icy6v2.js","/_next/static/chunks/15cy49d~_zsjj.js","/_next/static/chunks/0..ktetnpeix7.js","/_next/static/chunks/08cz-ztcfuxe..js","/_next/static/chunks/0i6hzvr84kc1r.js"],"AddToLibraryButton"] 44:I[29721,["/_next/static/chunks/08z4tkzvltetr.js","/_next/static/chunks/121~yigv24_j6.js","/_next/static/chunks/0jo3du-icy6v2.js","/_next/static/chunks/15cy49d~_zsjj.js","/_next/static/chunks/0..ktetnpeix7.js","/_next/static/chunks/08cz-ztcfuxe..js","/_next/static/chunks/0i6hzvr84kc1r.js"],"ShareButton"] 45:I[58016,["/_next/static/chunks/08z4tkzvltetr.js","/_next/static/chunks/121~yigv24_j6.js","/_next/static/chunks/0jo3du-icy6v2.js","/_next/static/chunks/15cy49d~_zsjj.js","/_next/static/chunks/0..ktetnpeix7.js","/_next/static/chunks/08cz-ztcfuxe..js","/_next/static/chunks/0i6hzvr84kc1r.js"],"ProcessEpisodeButton"] 46:I[45269,["/_next/static/chunks/08z4tkzvltetr.js","/_next/static/chunks/121~yigv24_j6.js","/_next/static/chunks/0jo3du-icy6v2.js","/_next/static/chunks/15cy49d~_zsjj.js","/_next/static/chunks/0..ktetnpeix7.js","/_next/static/chunks/08cz-ztcfuxe..js","/_next/static/chunks/0i6hzvr84kc1r.js"],"SignupCTA"] 3a:["$","span",null,{"aria-hidden":true,"children":"·"}] 3b:["$","span",null,{"children":"00:17:13"}] 42:T489,

Sprinting Without the Critical Path

Ever hit every sprint goal and still miss the deadline? This episode explains why.

Many teams think they're sprinting, but they're still trapped by hidden dependencies, approvals, and late integration work. It feels fast, but the results are slow. We cover what "moving fast" actually looks like when you're dealing with complex programs—and how to track progress without pretending you can predict everything upfront.

Agile vs. FTTM

Both want speed, but they solve different problems.

Agile is about learning as you go - small chunks, constant adaptation, delivering value piece by piece. It shines when requirements are fuzzy and you need to figure things out.

FTTM (Fast Time To Market) is about hitting a date - mapping dependencies, finding bottlenecks, and attacking them. It shines when you're coordinating multiple teams, suppliers, or hardware.

The simple version: Agile helps you build the right thing. FTTM helps you deliver it sooner. They work well together—Agile within teams, FTTM across the program.