Techniques to Estimate Spike

Last post 01:53 pm November 4, 2019 by Harshal Rathee

2 replies

12:53 pm November 2, 2019

Hello All,

I knew estimation for user stories is given by dev team,

But I would lie to confirm as a scrum master do i need to support dev team by using any estimating techniques for spikes ?

If so what estimation technique or tool can I use it.

Ian Mitchell

05:28 pm November 2, 2019

I knew estimation for user stories is given by dev team,
But I would lie to confirm as a scrum master do i need to support dev team by using any estimating techniques for spikes ?

Shouldn’t the Development Team be wholly responsible for whatever they choose to estimate, and however they choose to do it?

Do they wish to estimate “spikes” at all? Might they prefer to time-box them instead, for example?

Harshal Rathee

01:53 pm November 4, 2019

But I would lie to confirm as a scrum master do i need to support dev team by using any estimating techniques for spikes ?

How does your team do it now ? are there any issues your team have with current technique they use ?

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.