DAC Backlog Refinement & Prioritization 3 — Questions and Answers
Question 1: In DA's Disciplined DevOps layer, how does continuous deployment affect backlog prioritization?
- It eliminates the need for a product backlog entirely
- It shifts prioritization toward smaller, releasable increments with clear deployment readiness criteria (Correct answer)
- It requires all backlog items to be approved by the release train engineer first
- It moves prioritization authority from the product owner to the DevOps team
Correct answer: It shifts prioritization toward smaller, releasable increments with clear deployment readiness criteria
Continuous deployment favors small, independently deployable items, so prioritization must account for deployment complexity and readiness.
Question 2: When applying the DA process goal 'Manage the Work Item List,' which of the following activities is explicitly included?
- Assigning story points using Planning Poker only
- Triage, ranking, and estimating work items (Correct answer)
- Conducting formal change control board reviews
- Publishing a fixed-scope release plan quarterly
Correct answer: Triage, ranking, and estimating work items
The DA process goal for managing the WIL includes triaging incoming work, ranking items by priority, and estimating effort.
Question 3: A team is using Kanban within the DA context. How does backlog refinement differ compared to a Scrum-based team?
- Kanban teams do not refine backlog items at all
- Refinement is event-driven and occurs continuously as capacity becomes available rather than on a fixed cadence (Correct answer)
- Kanban teams must refine at least two sprints ahead
- Refinement is done exclusively by the coach, not the team
Correct answer: Refinement is event-driven and occurs continuously as capacity becomes available rather than on a fixed cadence
In a Kanban context within DA, refinement is pull-based and continuous rather than tied to sprint boundaries.
Question 4: What is the primary purpose of 'slicing' user stories during backlog refinement?
- To assign stories to individual developers
- To break large stories into smaller, independently deliverable pieces that reduce batch size (Correct answer)
- To convert stories into formal requirements documents
- To eliminate technical debt items from the backlog
Correct answer: To break large stories into smaller, independently deliverable pieces that reduce batch size
Slicing decomposes large stories into thin vertical slices that each deliver end-to-end value and can be completed within an iteration.
Question 5: Which DA mindset principle directly supports collaborative backlog refinement sessions with the whole team rather than just the product owner?
- Enterprise awareness
- Collaborate proactively (Correct answer)
- Apply design thinking
- Pragmatism
Correct answer: Collaborate proactively
DA's 'Collaborate proactively' mindset encourages whole-team participation in refinement to leverage diverse knowledge and build shared understanding.
Question 6: A coach notices a team's backlog has over 400 items, many of which are months old and never addressed. What DA-aligned action should they recommend?
- Archive the entire backlog and start fresh
- Conduct a backlog pruning session to archive, delete, or re-triage stale items (Correct answer)
- Split the backlog into two separate lists for the team to manage
- Promote all items to the current sprint to clear the queue
Correct answer: Conduct a backlog pruning session to archive, delete, or re-triage stale items
DA advocates for regularly pruning the WIL to remove stale items that no longer reflect current priorities and to keep the list manageable.
Question 7: In the DA context, what does it mean to 'right-size' a work item during refinement?
- Assigning the item to the most senior developer
- Ensuring the item is small enough to be completed within an iteration but large enough to deliver measurable value (Correct answer)
- Rounding story point estimates to the nearest Fibonacci number
- Splitting all items into exactly two sub-tasks
Correct answer: Ensuring the item is small enough to be completed within an iteration but large enough to deliver measurable value
Right-sizing ensures items are appropriately granular—small enough to fit in an iteration yet meaningful enough to provide customer value.
DAC Backlog Refinement & Prioritization 3
In DA's Disciplined DevOps layer, how does continuous deployment affect backlog prioritization?