Back to Forum

Technique to estimate Spikes

Last post 04:41 pm October 28, 2019 by Timothy Baffa
1 reply
Siddiq Mohammad
05:18 pm October 26, 2019

Dear All,

  • I knew the story points for user stories will be given by dev team,

    But as a scrum master do I need to support them to pick particular technique
  • Or do I need to take a charge and use any technique to estimate the Spike before we onboard into sprint
Timothy Baffa
04:41 pm October 28, 2019

do I need to support them to pick particular technique

As their Scrum Master, you are responsible for helping the Development Team understand the need and benefit for their estimation, and to help them identify a method that supports both their ability to plan and the PO's ability to forecast.

do I need to take a charge and use any technique to estimate the Spike before we onboard into sprint

It is a common practice, and one that I encourage with my teams, to time box spikes in hours/days, and to not relatively estimate them (points).   This way, a spike can be treated as a time-boxed event that affects team capacity for the sprint.   When the time box expires, then the spike is over, and the team should document and discuss their findings.

Be sure though that the spike doesn't reference deferred refinement, instead supporting analysis and investigation to guide the content and design of future PBI's.

 

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.