HKSM

The Updated Task List is the team-maintained, current list of all Sprint tasks with status, owner, and remaining effort. It is refreshed throughout the Sprint, especially after the Daily Standup, and is used to update the Scrumboard and Sprint burndown and to coordinate work.

Key Points

• Living list of Sprint tasks reflecting the latest work created, changed, completed, or blocked.
• Primarily updated after the Daily Standup; can be adjusted anytime new information emerges.
• Shows status, owners, and remaining effort to enable transparency and empirical control.
• Feeds the Scrumboard and the Sprint Burndown Chart for accurate visual management.
• Output of Conduct Daily Standup and Create/Estimate Tasks; input to Update Scrumboard and Update Sprint Burndown Chart.
• Scoped to the current Sprint and reset when a new Sprint begins.

Purpose

The Updated Task List enables the Scrum Team to inspect progress at a granular level and adapt daily. It supports coordination, exposes impediments early, and aligns the team on the most valuable next task to meet the Sprint Goal.

By capturing remaining effort and ownership, it provides the data needed to maintain the Scrumboard and burndown, helping stakeholders understand progress without micromanagement.

Key Terms & Clauses

• Task: A small piece of work required to deliver a user story within the Sprint.
• Status: To Do, In Progress, Done, or Blocked to signal current state.
• Owner: The team member currently responsible for the task.
• Remaining effort: The best current estimate to finish the task, typically in hours.
• Traceability: Each task references its parent user story or backlog item.
• Impediment reference: Notes or IDs linking to the Impediment Log when blocked.
• DoD linkage: Tasks collectively enable meeting the Definition of Done for their user story.

How to Develop/Evaluate

• Decompose Sprint Backlog items into tasks during Create Tasks and refine during the Sprint as learning emerges.
• After each Daily Standup, add, split, merge, reassign, or close tasks to reflect the latest plan.
• Update remaining effort based on current understanding; avoid percent complete and focus on effort left.
• Keep tasks small and clear; most should fit within a day so progress is visible.
• Validate every task maps to a user story and contributes to the Sprint Goal; remove non-value-adding work.
• Flag blockers and dependencies explicitly and create/refresh entries in the Impediment Log.

How to Use

• As an input to Update Scrumboard to ensure cards and columns match the latest task states.
• As an input to Update Sprint Burndown Chart by aggregating remaining effort across all tasks.
• During Conduct Daily Standup to coordinate handoffs, identify bottlenecks, and plan the next 24 hours.
• To support Remove Impediments by pointing to blocked tasks and their root causes.
• To prepare for Demonstrate and Validate Sprint by confirming that tasks achieving DoD are complete.
• To inform Retrospect Sprint with factual data on churn, blockages, and estimation accuracy.

Example Snippet

Simple fragment of an Updated Task List for a Sprint:

• T-12 — Story US-05 — Implement API call — In Progress — Owner: A. Lee — Remaining: 6h — Dep: T-14.
• T-14 — Story US-05 — Add unit tests — To Do — Owner: K. Rao — Remaining: 4h — Blocked by missing test data.
• T-21 — Story US-08 — Update UI labels — Done — Owner: M. Cruz — Remaining: 0h.

Risks & Tips

• Risk: Stale list leads to misleading burndown and poor decisions. Tip: Update immediately after the Daily Standup and major changes.
• Risk: Hidden work not captured as tasks. Tip: Enforce traceability from every activity to a task linked to a user story.
• Risk: Over-detailing becomes micromanagement. Tip: Keep tasks just enough to track flow and DoD; avoid excessive granularity.
• Risk: Tracking percent complete obscures reality. Tip: Use remaining effort and clear Done criteria.
• Risk: Scope creep inside the Sprint. Tip: Adjust tasks to meet the Sprint Goal without adding new scope not agreed in the Sprint Backlog.

PMP/SCRUM Example Question

After the Daily Standup, the team splits a complex activity into two tasks and identifies one new blocker. Which artifact should be updated and then used to refresh the Scrumboard and Sprint burndown?

1. Product Backlog.
2. Updated Task List.
3. Release Plan.
4. Definition of Done.

Correct Answer: B — Updated Task List

Explanation: The Updated Task List captures newly created, changed, completed, or blocked tasks and feeds both the Scrumboard and the Sprint Burndown Chart. The Product Backlog and Release Plan are not daily execution artifacts.