4 ms·
I see spikes as user stories that instead of a deliverable as their output, their output is the answer to a question.
by DubiousPusher 4y ago
I see spikes as user stories that instead of a deliverable as their output, their output is the answer to a question.
- sodapopcan 4y agoAbsolutely, that's a good way to put it. All feature spikes should have tickets defining what it's trying to validate. From a TDD standpoint, I also use the word "spike" to describe any quick experimental throw-away work done on a small slice of functionality before writing the first test. These should not have tickets as that would be a bit over-the-top (and you don't always know if you're going to do them).