Pi Planning, a key component of Scrum at Scale, is a collaborative workshop event where teams align on a shared vision and plan for upcoming sprints. Scheduling a Pi Planning event effectively is crucial for its success. Let's delve into the intricacies of creating a Pi Planning schedule that fosters collaboration, ensures alignment, and sets your teams up for success.
Before we dive into the scheduling details, it's essential to understand that Pi Planning is typically a two-day event. The first day focuses on understanding the current state, defining the future state, and breaking down work into manageable chunks. The second day is dedicated to refining the plan, estimating effort, and creating a shared understanding of the work to be done.
Preparing for Pi Planning
Preparation is key to a successful Pi Planning event. Here are some critical aspects to consider when scheduling:
**Identifying Participants**
Invite all relevant stakeholders, including team members, product owners, Scrum Masters, and other interested parties. A diverse group ensures a well-rounded perspective and fosters buy-in.
Setting the Date
Choose a date that works for everyone involved. Consider team members' calendars, as well as any upcoming holidays or company events. Tools like Doodle or When2Meet can help find a suitable time.
**Preparing the Agenda**
Create a detailed agenda outlining the event's flow. Include breaks, meals, and any necessary setup time. Here's a basic structure:
- Day 1: Introduction (30 min), Current State Analysis (2 hours), Future State Definition (2 hours), Breakout Sessions (2 hours), Review & Wrap-up (1 hour)
- Day 2: Plan Review (1 hour), Breakout Sessions (2 hours), Estimation & Planning (2 hours), Review & Wrap-up (1 hour)
Running the Pi Planning Event
Once the date and agenda are set, it's time to focus on the event itself. Here's how to structure the two days:
**Day 1: Understanding & Defining**
Current State Analysis
Start by understanding the current state. This could involve reviewing past performance, discussing current challenges, or analyzing existing processes.
**Future State Definition**
Next, define the future state. This involves aligning on a shared vision and identifying the work needed to achieve it. Use a large, visible board or a digital tool to capture and organize ideas.
Breakout Sessions
Divide into smaller groups to break down the work into manageable chunks. Each group should focus on a specific area and create a list of tasks or user stories.
**Day 2: Refining & Planning**
Plan Review
Review the output from Day 1. Ensure all teams have a shared understanding of the work to be done and any dependencies between teams.
**Breakout Sessions**
Teams refine their plans, estimate effort, and create a detailed sprint backlog. Encourage teams to use relative sizing and to focus on value rather than time.
Estimation & Planning
Teams create a sprint plan, including which tasks they will work on and in what order. They should also identify any risks or assumptions that could impact their plan.
**Review & Wrap-up**
Conclude the event by reviewing the plans, celebrating successes, and identifying next steps. Ensure all participants leave with a clear understanding of the plan and their role in its execution.
Pi Planning is a powerful tool for aligning teams and creating a shared understanding of the work to be done. By scheduling and running the event effectively, you can set your teams up for success and ensure your organization's goals are met. So, start planning your next Pi Planning event today and watch your teams thrive!