A 3rd party blog mentions my past posts on #agile #StorySpikes. It correctly quotes what I said, but contrasting it with @kentbeck drops context. My original #Scrum specific context aligns with Kent's.

Spikes provide for #ValidatedLearning & a smaller #ConeOfUncertainty. No #SprintBacklog item can exceed a single Sprint. Prefer time boxes ≤ 2-3 days, but spikes ≤ full team capacity for a single Sprint can be valid edge cases.

1. https://www.devopsonline.co.uk/the-spice-of-spike-in-an-agile-world/
2. https://www.linkedin.com/posts/todd-a-jacobs_the-spice-of-spike-in-an-agile-world-activity-7201328523322556417-U1Il