Should development team estimate every activity in sprint?

Last post 01:30 pm October 17, 2019 by Harshal Rathee

2 replies

09:55 am October 17, 2019

We usually take 3-4 high-priority, rather big features into sprint. We estimate them in story points. During the sprint we also fix some urgent, not related to these features bugs. We estimate those as soon as they are dropped into sprint as well to measure "real velocity". Note, that those bugs are never in a sprint goal.

I'm thinking if it's a good practice. Or should we drop it and just measure velocity based on these high-priority features being done? Any thoughts?

Ian Mitchell

11:19 am October 17, 2019

I'm thinking if it's a good practice. Or should we drop it and just measure velocity based on these high-priority features being done?

Why would you want to reduce transparency over the amount of work the team believes it can take on?

Harshal Rathee

01:30 pm October 17, 2019

I'm thinking if it's a good practice.

Does this helps you better in forecasting work for sprints ?

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.