A project lead is managing an agile project. The project activities, which have been placed in a backlog, still need to be refined and prioritized…

Backlog refinement is an essential, ongoing activity in agile frameworks, not a one-time event. It is performed regularly to ensure that items at the top of the backlog are well-understood, estimated, and ready for upcoming sprints. For a two-week sprint cycle, conducting a refinement session in every sprint is a standard practice. The primary focus of these sessions is to clarify and prepare the highest-priority user stories, as these are the most likely candidates for the next sprint. This ensures a continuous flow of value and allows the team to adapt effectively.

A. The primary focus of refinement is on priority to deliver maximum value, not solely on story points, which represent effort.

B. Waiting for three sprints is too infrequent and creates a significant risk of not having stories ready for upcoming sprints, disrupting the project flow.

D. This option combines two incorrect practices: an infrequent schedule (every three sprints) and the wrong focus (story points instead of priority).

1. Project Management Institute. (2017). Agile Practice Guide. Section 4.2.4

"Backlog Refinement

" describes this as a regular activity where the team reviews

estimates

and prioritizes backlog items. It states

"The team may spend up to 10% of its time during the iteration to help the product owner with refining the backlog

" which supports a recurring session within each sprint. The focus is on preparing items for future iterations

which implies prioritizing them.

2. Schwaber

K.

& Sutherland

J. (2020). The Scrum Guide. The guide defines Product Backlog refinement as an "ongoing activity." It states

"Product Backlog items that can be Done by the Scrum Team within one Sprint are deemed ready for selection in a Sprint Planning event." This necessitates regular refinement of high-priority items to get them into a "ready" state before the next sprint begins.

3. Stray

V.

Sjøberg

D. I.

& Dybå

T. (2016). The daily stand-up meeting: A grounded theory study. Journal of Systems and Software

114

101-124. While focused on stand-ups

this and similar academic studies on agile methods emphasize the principle of frequent

short-cycle activities. Backlog refinement fits this principle

where continuous attention (i.e.

every sprint) is favored over infrequent

large-batch activities (i.e.

every three sprints) to maintain agility and a ready backlog. (DOI: https://doi.org/10.1016/j.jss.2016.01.004)