Scrum Board

A highly visible team board used to organize and track product and sprint backlog items, mapping work through stages so progress and bottlenecks are easy to see.

Key Points

  • Visualizes the workflow with columns (e.g., To Do, In Progress, Done) and cards that move across stages.
  • Helps manage items from the product and sprint backlogs, keeping priorities and ownership clear.
  • Makes bottlenecks obvious via queues, blocked indicators, and optional WIP limits or policies.
  • Should be updated continuously by the team and be easy for stakeholders to view, whether physical or digital.

Example

A Scrum team uses a digital board with columns Ready, In Progress, Code Review, Testing, and Done. During daily Scrum, they notice many items piling up in Testing, signaling a bottleneck. The team adds a WIP limit to Testing and swarms to clear the queue.

PMP Example Question

Which artifact best displays the status of sprint work and exposes where items are getting stuck while also helping manage backlog items?

  1. Sprint burndown chart
  2. Scrum board
  3. Gantt chart
  4. Risk register

Correct Answer: B - Scrum board

Explanation: The Scrum board visualizes workflow and backlog items, making progress and bottlenecks transparent to the team and stakeholders.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Eight teaching sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Stop Managing Admin. Start Leading the Future!

HK School of Management and Technology helps you learn AI prompt engineering for project work. Move beyond status reports and risk logs with practical prompt frameworks for everyday tasks. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Enroll Now