The test driven development guys refer to a quick, exploratory, investigation that involves coding something up to see if it works, a spike.
Any ideas why they came up with that word?
Update: The coinage by Kent Beck looks like the 'original' one to me, although his usage of the word doesn't make much sense in my opinion. Coding up a quick test is 'putting a spike through the project'?
Interestingly, it seems he stopped using the term because it conjured up various meanings to different people - see below for evidence!