LeSS Events

Sprint Planning Part 2

Sprint Planning Part 2 is done independently by each team. Each team creates their own Sprint Backlog — decomposing selected items into tasks and creating a plan for the Sprint. Teams may coordinate with each other during this phase for items with shared dependencies.

Per-team planning · Timebox: ~2 hours (2-week Sprint)

Overview

Sprint Planning Part 2 is done independently by each team. Each team creates their own Sprint Backlog — decomposing selected items into tasks and creating a plan for the Sprint. Teams may coordinate with each other during this phase for items with shared dependencies.

Event Ownership

Owned / Facilitated By
Teams (self-manage) / Scrum Master (coaching)
Each team independently plans how to deliver their selected items
SM coaches teams in effective planning techniques but doesn’t direct the planning
Teams reach out to other teams directly for coordination on dependencies
PO is available for clarification but doesn’t drive Part 2

Who Should Be Present

Individual Team
Decompose selected PBIs into tasks, estimate effort, and create the Sprint plan
Scrum Master
Available for coaching; may float between teams to facilitate coordination
Product Owner
Available for questions but not leading the session

Preparation Checklist

01Items selected in Part 1 with clear ownership per team
02Teams have capacity calculations from Part 1
03Cross-team dependencies identified with coordination agreements

Facilitation Techniques

Click any technique to expand details and learn when to apply it.

Silent Decomposition

Give team members 10 minutes to individually decompose items into tasks on sticky notes, then merge and discuss. Prevents the loudest voices from dominating.

Click to expand

Cross-Team Scouts

Send one team member to another team’s Part 2 to coordinate on shared dependencies in real time. This is direct team-to-team coordination — no intermediaries needed.

Click to expand

Tips & Tricks

01
Each team plans independently — this is their plan, not the SM’s or PO’s
02
Don’t over-plan. Decompose the first few days in detail; plan the rest at a higher level
03
If teams struggle to plan independently, it’s a coaching opportunity, not a reason to direct them
04
Cross-team coordination should happen through direct conversation, not through escalation
05
Board Setup
Immediately after Part 2, each team sets up their Sprint Board with all tasks. Visible work is the foundation of empiricism.

Success Takeaways by Role

What each participant should walk away with when this event is run well.

Team

A plan they created themselves; confidence in the Sprint forecast; clarity on how to start execution

Scrum Master

Insight into team planning maturity; identified coaching opportunities

Goal

Each team has a Sprint Backlog with decomposed tasks

Goal

Teams understand their Sprint goal and how it contributes to the whole product

Goal

Cross-team coordination plans are confirmed

Goal

Teams have confidence in their Sprint forecast