Sprint planning connects your product backlog to actual development work by deciding what to build in the upcoming sprint. This team meeting sets clear goals for the short development cycle ahead, typically lasting 1-4 weeks.

The sprint planning session has two main parts:

• What part: The Product manager presents priority backlog items and explains their value
• How part: Developers break items into tasks and estimate effort to confirm what's doable

A clear sprint goal helps the team stay focused during the sprint. This goal should deliver real value to users, not just complete tasks. When problems arise, the team uses this goal to guide decisions.

Key sprint activities include:

• Daily stand-ups: Brief check-ins for progress updates and obstacle removal
• Sprint review: Demo of completed work to stakeholders, for example, a technical build of a feature to be released or a prototype made using Figma.
• Sprint retrospective: Team reflection on what went well and what to improve^[1]