How would a BA or Product Owner write up a spike? The cocky answer is to say “make your tech lead enter it”. If it’s larger than that, you should enter it into your backlog. If the spike only takes, say, an hour or two, maybe we don’t need to track it in our ALM tool. The Product Owner allocates a little bit of the team’s capacity now, ahead of when the story needs to be delivered, so that when the story comes into the sprint, the team knows what to do. You can call them research spikes, or architectural spikes, or refactoring spikes if you wish.Ī spike as an investment the Product Owner makes to figure out what needs to be built and how the team is going to build it - in advance of actually building it.
#Spike meaning in sprint software
Do an experiment with some other library or software package. We might want to look into something for a day. In these cases, we might want to build a functional or technical experiment to figure it out. Perhaps we’re unsure if we’ll be able to complete the story due to some potential blocker. Perhaps the implementation or a 3rd party tool or library is poorly understood. Sometimes a story is too large or overly complex. What’s a Spike? Who should create it? And what should it look like in VersionOne? (Or in Agile Central, Pivotal Tracker, HP AGM, Jira, or your ALM tool.)Įxcellent questions! I thought I’d share my thoughts on the topic: What’s a Spike?
0 kommentar(er)
