Sprint Planning & Backlog

Sprint Planning & Backlog

Sprint planning is where the team decides what work to accomplish in the upcoming sprint. A well-managed backlog ensures the team always knows what to work on next.

Product Backlog

  PRODUCT BACKLOG
  ===============

  Priority | Item                      | Points | Status
  ---------|---------------------------|--------|--------
  1        | User Login                |   5    | Ready
  2        | Password Reset            |   3    | Ready
  3        | User Profile              |   8    | Ready
  4        | Dashboard Analytics       |  13    | Refining
  5        | Export to PDF             |   5    | Refining
  6        | Multi-language Support    |  21    | New
  7        | Dark Mode                 |   8    | New

  Backlog Items:
  - Continuously groomed and prioritized
  - Ready items are "Definition of Ready" compliant
  - Estimated using story points
  - Written as User Stories

User Stories

  USER STORY FORMAT
  =================

  As a [type of user],
  I want [an action],
  So that [a benefit/value].

  Example:
  As a registered user,
  I want to reset my password via email,
  So that I can regain access if I forget my password.

  Acceptance Criteria:
  - Given I am on the login page
    When I click "Forgot Password"
    Then I see an email input form

  - Given I enter a valid email
    When I submit the form
    Then I receive a reset link within 2 minutes

  Story Points: 3 (Fibonacci: 1, 2, 3, 5, 8, 13, 21)

Sprint Planning Meeting

  SPRINT PLANNING AGENDA
  ======================

  Part 1: What (with Product Owner) - 1 hour
  +------------------------------------------+
  | - Review sprint goal                     |
  | - Select backlog items for sprint        |
  | - Clarify requirements                   |
  | - Confirm "Definition of Ready"         |
  +------------------------------------------+

  Part 2: How (Development Team) - 1 hour
  +------------------------------------------+
  | - Break items into tasks                 |
  | - Estimate task hours                    |
  | - Identify dependencies                  |
  | - Assign initial ownership               |
  +------------------------------------------+

  Output: Sprint Backlog with committed items

Sprint Ceremonies

• Daily Standup: 15-minute daily sync (What did I do? What will I do? Any blockers?)
• Sprint Review: Demo completed work to stakeholders
• Sprint Retrospective: Team reflects on what went well and what to improve

Key Takeaways

• The product backlog is a living, prioritized list of work
• User stories describe features from the user's perspective
• Sprint planning defines what the team will accomplish
• Regular ceremonies keep the team aligned and improving