specimens
Well, yes there is. I'm bookmarking it here for my next argument on the subject.
Too cute, I know. Made pancakes for Poopsik this morning (as she does demand them on Saturdays).
From: http://www.ftc.gov/bcp/conline/pubs/alerts/optoutalrt.htm
Credit Bureaus
The credit bureaus offer a toll-free number that enables you to "opt-out" of having pre-approved credit offers sent to you for two years. Call 1-888-5-OPTOUT (567-8688) for more information. When you call, you'll be asked for personal information, including your home telephone number, your name and your Social Security number. The information you provide is confidential and will be used only to process your request to opt out of receiving pre-screened offers of credit.
I figured out what the XPlanner problem is wrt metrics and accuracy.
When you blow an estimate, it prompts you to change the estimate by adding
the delta to the estimate field. DO NOT ACCEPT XPlanner's prompted
estimate, simply put the original estimate back in the text field. It will
allow you to continue.
This is non-intuitive because the screen flow leads you to believe that
you cannot enter an estimate that is less than the time spent. This is not
true at all: you may elect to ignore the prompt to change the estimate
entirely.
I think the reason the screen flow is as such is typically for iteration
planning purposes. The only reason you would change this in development is
if your customer and you renegotiated stories mid-iteration and you are
now changing all your estimates and the time spent on the tasks at the
same time: not to mention you don't care about analyzing your estimating
accuracy.
A simple fix would be to always prompt with the original estimate instead
of trying to be helpful by prompting with the aggregate time spent as the
original estimate.
http://sourceforge.net/forum/forum.php?thread_id=1350686&forum_id=161119
Turns out, "starting" an iteration is an important user action. I believe it takes a snapshot of the current story estimate, whatever that may be, whether made up of its tasks or not, and saves that as the estimate that will be used to calculate velocity during and at the end of the iteration.
Again, I am guessing, but I believe that means that if you "close" and re-"start" an iteration, you will potentially mess up any iteration velocity statistics you were hoping to get . . . since that will take a new "snapshot" of the story estimates, based on whatever they are right now . . .