[latchkey]

PT automatically adjusts the number of stories that make it into a sprint. They don't really have a concept of sprint actually... it is just average velocity over time and the number of stories that can fit into that average.

If a PM wants to see how adding in just one more feature impacts the schedule, they can just drag the pointed story into the queue and see what gets pushed out to the next week.

If a developer goes on vacation, it is easy to see how that impacts the schedule cause you can subtract their average velocity.

Most people don't understand this killer feature of PT unless they've actually spent a bunch of time using it. It really enables you to do accurate project estimates, if you do it right.

Source: worked for cloudfoundry/pivotallabs