
Refine and prioritize product and team backlogs, plan sprints with capacity and velocity, and execute daily scrums, sprint reviews, and retrospectives to deliver increments.
PI Planning, also known as Big Room Planning, is a key event in SAFe. Every 4 to 6 sprints, the ART teams convene to plan and sync their work for the next 4 to 6 sprints. PI Planning define the heartbeat of an ART.
This section describes what PI Planning is and how to run it effectively.
Identify inputs and outputs of pi planning, estimate capacity, refine backlogs, plan six sprints, map dependencies, and confirm the plan with confidence votes to deliver a realistic sprint plan.
Visualize each agile team's board to plan sprints, reveal capacity, and commit to work from the team backlog, while signaling dependencies with other teams for transparency.
Velocity is the amount of work completed in previous sprints. It’s a measure of past performance for the team. Typically, you look at the last three to five sprints, and take the average of their velocity. This helps to offset any spikes in a particular sprint. Teams that measure velocity can use it as their upper limit capacity to plan the next sprint. This is the Yesterday’s Weather pattern in action: we look back at past performance in previous sprints, and we use that measure to establish a baseline for capacity in the upcoming sprint.
Capacity is the maximum amount of work that the team can commit to doing in the next sprint. The team can quickly establish capacity by starting from the average velocity and then adjusting it based on everyone’s availability during the next sprint. For example, if you know that a couple of team members will be in vacation during the sprint, you need to reduce your capacity by a proportional amount. Capacity should always be equal to or lower than the average velocity of the team, to avoid overcommitment.
Load is the amount of work selected by the team for the current sprint. This is the amount of work that the team is planning to complete in the sprint. It should be less or equal to capacity (otherwise the team is overcommitting). You start from your capacity, and then decide how much work you want to actually select for the sprint.
The load should be less or equal to capacity. Think of capacity as the maximum quantity of a jar of cookies, and the load as the amount of cookies actually in the jar. Since you love cookies, I bet you’d like to fill the jar to the brim. However, there is nothing wrong with leaving some empty space in the jar. You can always add more cookies later if needed.
When we have multiple teams working together on the same product, how can we create transparency on the inter-dependencies between teams, and track them?
The Program/Planning Board is a key artifact in SAFe that allows the teams within an ART to visualize and track dependencies.
In this lesson we learn about PI Objectives. In addition, we discuss how to assign business value, and how to calculate actual value.
Identify and manage risks in SAFe PI planning by using risk cards to describe likelihood, impact, and ownership, and roam risks to resolve, mitigate, or accept.
SAFe (the Scaled Agile Framework for the enterprise) is a widely adopted framework to scale agile from one agile team to tens or hundreds of teams, all working together on the same product. SAFe has been adopted by thousands of organizations around the world and is today the most widely adopted scaling framework for large agile teams.
Since 2011, SAFe has gone through major enhancements over the years, however its fundamental structure remains the same. In this course, I will present the key elements of the framework such as the Agile Release Train, PI Planning, and the Program Board. This course is ideal for anyone who wants to grasp the key concepts and components of SAFe, with a short, focused training course.
This course is intended to be an introduction for anyone who wants to understand what SAFe is and how it works. This is also for people that already have a SAFe certification or are already implementing SAFe in their workplace, and want to review some of the key concepts and learn how to best apply them.
SAFe is a registered trademark of Scaled Agile Inc., the company that created the SAFe framework. This course does not replace a traditional SAFe certification. Scaled Agile Inc. provides a wealth of resources to learn more about each component of SAFe, and also provides certification courses for anyone interested in getting a SAFe certification. Please refer to their website for more information.
Throughout the course, I will share my experience in applying SAFe to large organizations, both private and public, and will provide tips to adopt SAFe properly and avoid some common pitfalls.
Most of the organizations I have worked with, when they scale agile typically have a number of agile teams using Scrum. In this course, I will assume that all teams use Scrum. However, Kanban and XP teams can also successfully apply the SAFe framework together with Scrum teams.
My goal is to provide you with an understanding of how SAFe works and how to best implement its key elements in your workplace.
We will start with a quick review of the Scrum Team. We will look at the key roles of Product Owner, Scrum Master, and Team Members or Developers on a Scrum team, and how these roles are extended when scaling with SAFe.
We will then review the Scrum workflow and the activities that happen at each Scrum event. While a baseline understanding of Agile and Scrum is a pre-requisite for the course, I find it useful to refresh our memory on how Scrum works with one team, before we can talk about scaling it to multiple teams.
Then we will learn about the SAFe framework, looking at how to scale from one team to multiple teams, and at PI Planning - which is a recurring activity that all teams do together. It's like the heartbeat of SAFe! And I'll share a few insights and tips to make it effective.
And finally, we will look at Epics and how to manage a portfolio of Epics with the Portfolio Kanban.
Throughout the course, I will offer a few quizzes as an opportunity to test your knowledge and understanding of the key concepts. And you will also find a helpful workbook that covers each session.
I hope you find it useful... let's get started!