Should development team estimate every activity in sprint?

Last post 01:30 pm October 17, 2019
by Harshal Rathee
2 replies
Author
Messages
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?

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?

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 ?