Backlog Refinement & Prioritization Flashcards

When coordinating backlog refinement across multiple DA teams working on the same product, what practice helps align priorities?

Answer: Program Increment (PI) planning or equivalent cross-team backlog synchronization sessions

Cross-team synchronization sessions ensure that inter-team dependencies and shared priorities are visible and aligned across all teams.

A stakeholder insists on adding a low-business-value item to the top of the backlog for political reasons. As a DA Coach, what is the BEST approach?

Answer: Facilitate a transparent priority discussion using value-based criteria to help stakeholders make an informed decision

A DA Coach uses facilitation and value-based frameworks to help stakeholders make rational priority decisions rather than avoiding the conflict or escalating prematurely.

Which estimation approach aligns best with DA's philosophy of 'good enough' over 'perfect'?

Answer: Relative sizing using T-shirts, story points, or #NoEstimates for small items

DA supports a range of estimation approaches and favors lightweight relative sizing that is fast, collaborative, and 'good enough' to make planning decisions.

What role does technical debt play in DA backlog prioritization?

Answer: Technical debt items should be visible in the WIL and prioritized alongside features based on their impact on flow and quality

DA treats technical debt as legitimate work that belongs in the WIL and must be balanced with feature delivery to maintain sustainable pace.

In a DA team using Lean UX, how does backlog refinement integrate with user research?

Answer: Insights from user research and experiments are fed back into the backlog to re-rank or create new items

Lean UX within DA creates a continuous feedback loop where validated user insights directly inform backlog priorities and item creation.

A DA Coach wants to help a team visualize the flow of backlog items from refinement to done. Which tool is most appropriate?

Answer: A Kanban board or value stream map that shows item states and bottlenecks

A Kanban board or value stream map makes the flow of work visible, helping the team identify bottlenecks between refinement and delivery.

Which DA concept describes the risk of spending too much effort refining items that will never be built?

Answer: Over-processing waste

Over-processing is a lean waste type where work items receive more refinement or detail than necessary, particularly for low-priority or speculative items.