Software Development Cross Solution - Index of - Free

spike tests
Spike test to estimate
30% of the tests you wrote are failing, but you really have no idea if a
single line of code would fix most of that, or if even passing one more
test could take new classes and hundreds of lines of code. There’s no
way to know how big a problem those 13 test failures really represent.
So what if we take a little time to work on the code, see what we can get
done, and then extrapolate out from that?
This is called spike testing: you’re doing one burst of activity, seeing
what you get done, and using that to estimate how much time it will take
to get everything else done.
1
400 Chapter 11
Take a week to conduct your spike test
Get the customer to give you five working days to work on
your problem. That’s not a ton of time, and at the end, you
should be able to supply a reasonable estimate.
When the customer gives his
OK, you can block out a week
to do your spike testing.
Look, my patience is wearing thin. You
better have a solid estimate at the end
of this week, or we’re going to have a
real serious talk, OK?
Download at WoweBook.Com
The customer’s probably
impatient by now, but you’ll
only make things worse if
you give them a completely
made-up estimate.