Do you know what your team's sustainable pace is? Do you believe it is equal to their Velocity? Let's try to answer that question. Scrum tells us that we should be Sprinting toward the goal of delivering working software. But then it tells us that we should work at a pace that is sustainable over the long haul. Is that an oxymoron? Or is that Zen? Velocity is the rate at which the team is delivering valuable-working-tested software to the customer. If that velocity is at a steady state then it is the sustainable pace for that team - right? I'll agree to that - if that velocity is relatively steady state over 2 years of time. Then there is a high likely hood that the velocity accounts for vacation, holiday, sickness, team member changes, and growth of the scope of the definition of done for a sprint. So how do you get a team working on a project to a steady state for two years? In this industry - you don't! But that doesn't mean we can approximate