Skip to main content

Is Backlog Refinement a Time-Boxed event?

Last post 03:13 am January 10, 2014 by Ian Mitchell
1 reply
11:47 pm January 9, 2014

Can anyone help to understand
" Refinement usually consumes no more than 10% of the capacity of the Development Team."

Here is my understanding :

Estimated Capacity of a team = Committed dev team members x( Effective Hours x No.of Sprint Days)

Hypothetically team members is = 4 (Fully committed)
Effective hours/per person = 6 Hrs
No. Of Sprint Days = 20 days(1 month sprint)

So the Capacity = 4*(6*20) = 480 man hours.
10% of 480 is = 48 hours which can be spent for the product backlog refinement.

Is it Time-Boxed?
do we need to convert this as a time-boxed of 2 days or 48 hrs for a sprint of one month?
in this case the time box varies based on the effective hours invested based on person's focusing factor.


03:13 am January 10, 2014

No, backlog refinement is not a timeboxed event in Scrum. It's a responsibility of the Scrum Team, and one to be fulfilled within each Sprint timebox. The 10% figure is merely a guide to help shape an activity that should happen on an ongoing basis.

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

Please note that the first and last name from your 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. does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, 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 may have their access revoked at any time, without warning. may, but is not obliged to, monitor submissions.