I know that in my Critical Chain world, we have range estimates (of duration and/or iteration) and their derivative buffers to help deal with the idea of iterations (either the old-fashioned test-fix-test-fix kind, or the evolving stories or scrums of those new-fangled agile approaches).
I'm curious about how others deal with allowing time in the project for variable iteration situations, yet still provide for credible and trackable project promises. Saving Changes...
Anonymous
We tend to include a "most likely" view of iterations, but are almost never in line with that expectation. Saving Changes...