Plan and Estimate phase

A Scrum stage focused on planning and sizing User Stories and their related tasks. It includes creating User Stories, estimating User Stories, committing selected stories to the sprint, identifying tasks, estimating tasks, and updating the Sprint Backlog.

Key Points

  • Produces a realistic Sprint Backlog with agreed scope and effort estimates.
  • Product Owner clarifies priorities and acceptance criteria; Developers estimate; Scrum Master facilitates.
  • Common techniques: story points, relative sizing, Planning Poker, task breakdown and hour estimates.
  • Outputs include committed User Stories, decomposed tasks, updated Sprint Backlog, and captured risks/assumptions.

Example

At sprint planning, the team selects the top Product Backlog items totaling 30 story points, clarifies acceptance criteria, breaks each story into tasks (e.g., design, API changes, tests), estimates hours for tasks, commits to the sprint scope, and updates the Sprint Backlog accordingly.

PMP Example Question

Which statement best describes the Plan and Estimate phase in Scrum?

  1. The team plans and sizes User Stories and tasks, commits to sprint scope, and updates the Sprint Backlog.
  2. The team deploys the increment to production and gathers end-user feedback.
  3. The team creates the product vision and high-level roadmap.
  4. The team conducts a daily 15-minute meeting to synchronize work.

Correct Answer: A — Scrum planning and estimation phase

Explanation: The Plan and Estimate phase focuses on selecting, estimating, committing to User Stories, breaking them into tasks, and updating the Sprint Backlog for the upcoming sprint.

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


Advance your Lean Six Sigma expertise!

HK School of Management and Technology helps you take Lean Six Sigma to the next level without the overwhelm. Master advanced statistical tools, Excel-based analysis, and real-world improvement techniques to solve complex problems with confidence. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More