EXtreme programming - prototyping as a task? Or reduce the tasks you perform?

Question

Should you, when you want a prototype of a set of tasks, pre-do a task and set aside time for this?

Or, on the other hand, should you reduce the number of tasks that you perform on this day / couple of days and inform at the front that you are prototyping, therefore, falling out at your speed?

I will roll on the second - the material that I have on XP did not mention this problem.

Thanks.

Answer 1

, - . Spike Solution. , .

"", . , , . . .

? Spike Solution.

Answer 2

, . , . / -, (), . , , . , , .

Answer 3

Just the way we do what I work, we tend to give him time. It seems to work well, as it does not account for the developer.