The MR manager is unsure whether she wants a Scrum or Kanban board for her project. Identify one difference between the boards.

Scrum boards in Jira are designed around sprints, which require estimating work to plan sprint capacity and track progress. Consequently, Scrum board configurations have a dedicated "Estimation" section where you can select an estimation statistic, such as Story Points or Original Time Estimate. This statistic is crucial for generating velocity and burndown/burnup charts. Kanban boards, focusing on continuous flow and cycle time, do not have this specific board-level configuration for an estimation method. While issues on a Kanban board can have estimates, the board's core functionality and reporting (e.g., Control Chart) are not driven by a pre-selected estimation statistic in the same way.

A. Column constraints (WIP limits) are a primary feature of Kanban but can also be configured on Scrum boards to manage work in progress within a sprint.
B. The Scrum board's backlog is a dedicated list view for sprint planning, not a card layout. The Kanban backlog, when enabled, appears as a column with cards.
C. The "Days in column" indicator, which helps identify stale issues by showing dots for the number of days an issue has been in a column, is available on both Scrum and Kanban boards.
D. Both Scrum and Kanban boards support Quick Filters (sometimes referred to as sub-filters) to allow users to refine the issues displayed on the board.

1. Atlassian Documentation, "Configuring estimation and tracking": Under the "Enable estimation on your board" section, the documentation explicitly states, "Note that estimation is only available on Scrum boards, not Kanban boards." This directly supports option E as the correct answer. (Source: Atlassian, Jira Software Cloud Documentation, "Configure estimation and tracking").

2. Atlassian Documentation, "What is a Jira Software board?": This document compares the two board types. For Scrum, it highlights features like "Backlog," "Sprints," and "Reports (e.g., Burndown Chart, Velocity Chart)," which are all tied to estimation. For Kanban, it emphasizes "a focus on visualizing your workflow, limiting work in progress, and maximizing efficiency," which does not rely on a board-level estimation setting. (Source: Atlassian, Jira Software Cloud Documentation, "What is a Jira Software board?").

3. Atlassian Documentation, "Configure columns": This page details column configuration for boards. It describes setting up column constraints (WIP limits) and the "Days in column" indicator, noting their availability for both board types, which invalidates options A and C. (Source: Atlassian, Jira Software Cloud Documentation, "Configure columns").