How do I maintain project velocity when restarting a project that has been on hold, paused, or stalled for a number of iterations?
If several iterations pass where little or no work is done on a project, and then you resume work, you will want to use your velocity from the last iterations in which you actually performed work. You can do this by combining the features of iteration length override and team strength override: • Locate the iteration where the project was first “paused”, and zero- or low-velocity iterations began. • Change the length of this iteration to include all of your paused, zero- or low-velocity iterations. • Set the team strength for this custom-length iteration to zero or the correct reduced strength for the period of time. Now, the custom-length iteration with overridden team strength will only be counted as a single iteration in your running velocity calculation, and the last iterations in which you actually performed work will be included in the calculation.
