How to Write Spikes
For User Stories - User stories are a way to describe the desired functionality of product backlog items. High-priority user stories tend to be more detailed; low-priority user stories tend to be less detailed. Teams add details as stories rise in priority, either by creating acceptance criteria or by splitting big stories into smaller pieces (or both).
For Spikes - Spikes represent activities such as exploration, architecture, infrastructure, research, design, and prototyping. Their purpose is to gain the knowledge necessary to reduce the risk of a technical approach, better understand a requirement, or increase the reliability of a story estimate.
User Story Template – This will help the developer or anyone that views the user story the following:
- Purpose
- What needs to be done, and
- Who it might affect
“As a [role], I [want to], [so that].”
Best Practices:
- Review any potential documents/resources in Wiki that can help with the research
- ALWAYS DOCUMENT!
- Work with Pod Lead/ PM/ and SM in creating tickets (if need be) that will be assigned to an upcoming sprint.
