Skip to main content

As per Guide - Product Backlog refinement is the act of adding detail, estimates, and order to items in the Product Backlog.

Last post 12:59 pm September 20, 2019 by Sander Dur
4 replies
01:08 pm September 19, 2019

Question - 

When we say 'Estimate' does it includes estimation of 'Sub-Tasks'? (E.g. Development task, Testing tasks etc in Hours) or Story in story points ?

Because we estimate the story in story points during the Sprint Planning (Planning Poker). 


01:13 pm September 19, 2019

If that's how your team is choosing to perform their estimates. The Scrum Guide does not prescribe how the team should estimate or how granular the estimates should be (story level vs task level). 

 


02:14 pm September 19, 2019

When we say 'Estimate' does it includes estimation of 'Sub-Tasks'? (E.g. Development task, Testing tasks etc in Hours) or Story in story points ?

 

Agree with @Tony , there is no specific rule and neither its in Guide. What does your development has to say on this ? Are they able to plan their work for a Sprint ? 


02:38 pm September 19, 2019

When we say 'Estimate' does it includes estimation of 'Sub-Tasks'? (E.g. Development task, Testing tasks etc in Hours) or Story in story points ?

It all depends on what your team deems suitable. If you think estimating on subtask level is improving your transparency or ability to deliver a done increment which suits the Sprint Goal, sure!

we estimate the story in story points during the Sprint Planning

I would advice the stories to be estimated during refinement sessions and not Sprint Planning event.

This will also help your team and PO to craft a Sprint Goal and forecast during the Planning event

 


12:59 pm September 20, 2019

Also user stories are not necessarily the best format, but it's about the 3 C's idea behind it:

- Card (user story, task, sub-task, banana peel). The card contains an idea, with limited information. This way the  development team doesn't get biased on how to do the work and keep a creative, open mind.

- Conversation: Development team has a conversation with P.O. (or stakeholders, if necessary) to understand and add details.

- Confirmation: Through for example acceptance testing, the details and outcome are verified.

More info:

L-l-l-linkie!


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.