What is a SPIKE in AGILE SCRUM? SHOULD YOU ESTIMATE Spikes in Story Points? (SURPRISING...)

[@agilecoach]

I make $0.00 on this KZbin Channel. All I ask in return is a little flick on that LIKE button, and maybe SUBSCRIBE to the channel if you enjoyed the video. Thanks for your support 🙌 I want to hear from you. What topic do you want me to cover next?

[@maysahulme6190]

liked

[@markotolagano]

Nice video! Scrum and agile are based on empiricism. That said, we use story points to compare things we have experience with. For example, a reference story exercise helps us predict the complexity of the work, based on past experience. Also, spike means that we have entered in the domain of the unknown, therefore, we have nothing to compare with, and we have no clear idea how long it will take to fully comprehend all the details of a particular issue. Because of this, it makes more sense to set a timebox, and after the timebox expires, to evaluate the issue, and make a biz decision.

[@agilecoach]

Thanks for watching and the leaving this great comment Marko

[@poojajain2553]

What happens when the timebox expires and spike needs more research? Let’s say timebox for a spike is 2 weeks which is entire sprint. At the end of the sprint spike outcome is not yet comprehended. Should we take the same spike to next spring with new timebox or should we create a new spike for the left over research?

[@ihabyousif8776]

❤❤ well said buddy!

[@oliviar267]

Awesome video thanks 😊 I love how you give real examples that impact our daily lives as scrum masters 💜

[@agilecoach]

Thanks for always watching Olivia

[@joeyvillaceran6204]

One subscriber here, really helped me as a scrum team member and is new on scrum to understand spikes. Thank you very much sir!

[@agilecoach]

Thanks Joey

[@itaneh6200]

Your knowledge of Agile is just amazing. I wish you were my personal coach

[@agilecoach]

Thanks a lot for watching Ita

[@mayurmiths]

Loved the explanation of Spike… I googled it but couldn’t find better elaboration. Keep it up.

[@agilecoach]

Thanks a lot Mayur

[@mayank806]

Best spike explanation

[@agilecoach]

Thanks Mayank

[@rimworld3162]

Good video coach, love your channel

[@agilecoach]

Glad you enjoy it!

[@gouravrawat8190]

Ty for video on this topic ..

[@agilecoach]

Thanks a lot for watching Gourav

[@Charlie-zw2xu]

thanks for making this spike video that i request coach

[@agilecoach]

Hope you enjoyed it!

[@miles2code366]

I chose your video because you have chapters you can skip too. Great video!

[@agilecoach]

Thanks a lot for watching

[@redpill6772]

good explanation of spikes

[@agilecoach]

Glad it was helpful!

[@naveenvikrampmp7808]

We dont want to estimate the spike because its similar to backlog refinement as scrum rule says 10% of time dev team gas to spend on this backlog refining can you tell me maximum time a team can spent on spike say 1-2 hours right?? Actually i am from construction domain i am preparing for pmp your videos are really good

[@agilecoach]

Thanks a lot for watching. A spike typically takes around 1-3 hours but can also take up to one day depending on the complexity. I prefer keeping spikes in the 1-3 hours range though.

[@poojajain2553]

Also Spikes are invented from XP can we use them in Scrum?

[@agilecoach]

Yes, works with Scrum. Thanks for watching Pooja

[@maysahulme6190]

make a guide about self managed teams please

[@agilecoach]

Thanks Maysa

[@oliviar267]

We estimate spikes because we put effort into it and developers or others in the team need the ticket to log their hours to.

[@agilecoach]

Great approach Olivia

[@thefruitshop4345]

first to comment

[@agilecoach]

Congrats