PI Planning Magic!

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

Intro

Earlier this month I was helping a software organization in an Israeli defense organization (that’s why there are no pictures) run their first PI Planning event. The day after I told my colleagues at Agilesparks that this is one event I will try to remember whenever I get into difficult times doing coaching, something that happens from time to time, coaching being what it is. I will try to remember that day because of the magic that happened somewhere around noon. And I want to tell you all about it.

If you aren’t familiar with it, PI Planning is an event where the entire (yes, entire) organization (or part of the organization, if it is big, up to around 125 people) convenes for 2 days to plan the next 4 to 6 iterations (sprints). Most people, hearing about it for the first time, respond in the exact way you did just now – incredulity. Yet, at the end of the event people are just talking about how will they make the next time even better. Having said that, the event we did this time was one day only – you need to choose your battles. As you will see, we needed that extra time.

Warm-up

The main purpose of the PI Planning event is to align and synchronize the organization and so the first day opens with overviews by various stakeholders, product managers and architects, all bringing concise messages and information – we don’t want all the people sitting there getting too bored, a challenging task. Immediately following this the teams break out for planning. Everyone stays in the same venue, huddling around tables, trying to come up with content for each of the PI’s iterations (leaving the last iteration for other things.) And here things start to warm up.

At the beginning the teams will usually stay together, calculating their capacity for each iteration and better understanding the required features to develop. However, after an hour or so it starts to be evident that there are dependencies on other teams, and this is exactly what happened at the mentioned event. One of the reasons the organization went into this in the first place is that coordination and alignment between teams did not fare so well. Yet, even though it was obvious the dependencies should be discussed, teams preferred to continue and look at their own plans, keeping to their tables, exactly like other teams in other organizations do.

Enter the program board

This is a good time to mention that another output of the event, in addition to the team’s plan, is the program board on which we clearly see dependencies between the teams. At this point of the event, the board was empty. Seeing the situation for what it was, the RTE, a sort of a scrum master of the scrum teams, started going around the tables, prompting people to start placing dependencies on the board, assertively. And so they did. And then magic happened.

We asked teams that placed dependencies on the board to make sure they talk about it with the relevant teams (people and interactions over processes and tools, right?) and this started an interaction across the teams. While at the beginning the noticeable huddle was around the program board, soon you started to see people from different teams at other teams’ tables. It was not just scrum master to scrum master but any representative with any other team members. People were thinking about where should they move this story and whether they could split that feature to accommodate for the dependencies. Suddenly you saw how decision-making went down to the ranks, how they took ownership of the big plan.

Self Organization Magic

That magic of self-organization was happening right before our eyes. Instead of some managers making all the decisions and being the pipelines for messages, people were interacting directly. Later the RTE said that while she felt she was a bit losing control of the happenings, the volume of interactions and decisions was something that couldn’t be tracked by one person. She was happy.

At some point it seemed as though energy is starting to go down and that we can start to wrap up. The RTE called for a scrum of scrum meeting around the program board where some dependencies were not handled. We gave the teams another 45 minutes.

The Confidence Vote

Once we had everyone’s attention – it was not an easy task – we asked the people to raise their hands in the air and indicate with the number of fingers what is their level of confidence in the plan. One means no confidence at all, and five means excellent. As hands went up in the air we saw one One and a few Twos. Most were from one team. We asked the people what was the issue and the response we got was that everything got into the plan because this is what they were asked to do. Not good.

What the RTE did at this point was to allocate another 30 minutes for the teams to change their plans so they will believe in them. Stories were moved, features got a bit thinner and when we had the vote again, we had a few Threes and the rest were Fours and Fives. The number of Threes was small enough for us to decide to handle these issues during execution.

Retrospective

At the very end of the day, we asked the teams to present the main findings of their retrospective. The feedback was good, mainly that teams agreed on them when and who will do what is something that so far they couldn’t manage to do. This fast coordination loop is making things that would usually take weeks or months to happen in one day. And that’s magic!

Subscribe for Email Updates:

Categories:

Tags:

Nexus and SAFe
GanttBan
Manage Budget Creation
Kanban
Agile Marketing
Webinar
Continuous Delivery
Kanban Basics
Spotify
lean agile change management
Atlaassian
Certification
Agile Basics
ScrumMaster Tales
Tools
Lean-Agile Software Development
Scrum Master Role
Jira Cloud
Daily Scrum
Lean and Agile Principles and Practices
Agile Community
Artificial Intelligence
Lean Budgeting
What Is Kanban
QA
Story Slicing
RTE Role
Agile and DevOps Journey
Scrum Primer
Coaching Agile Teams
Agile Games
Certified SAFe
TDD
Implementation of Lean and Agile
Games and Exercises
SA
Tips
Accelerate Value Delivery At Scale
Risk-aware Product Development
Confluence
Keith Sawyer
Presentation
Agile Assembly Architecture
Continuous Integration
Scrum
Amdocs
WIP
Agile India
Quality Assurance
Agile Exercises
Agile Outsourcing
Acceptance Test-Driven Development
Enterprise DevOps
Applying Agile Methodology
Agile for Embedded Systems
Agile Release Management
SAFe DevOps
Scrum.org
Kanban Kickstart Example
Limiting Work in Progress
Product Management
Agility
Software Development Estimation
Managing Projects
Principles of Lean-Agile Leadership
Agile Mindset
LPM
Lean-Agile Budgeting
Continuous Improvement
Retrospectives
Planning
Rovo
Team Flow
Change Management
Large Scale Scrum
Agile Games and Exercises
Advanced Roadmaps
Reading List
Sprint Iteration
ATDD vs. BDD
Rapid RTC
Scrum Values
speed at scale
Lean Agile Organization
Continuous Planning
Kanban 101
Code
RSA
SPC
DevOps
System Archetypes
Lean Startup
Agile Israel Events
Pomodoro Technique
Agile Program
Lean Agile
System Integration Environments
speed @ scale
Product Ownership
Agile Testing Practices
Kanban Game
PI Planning
Nexus
EOS®
RTE
NIT
Value Streams
AgileSparks
AI
ALM Tools
The Agile Coach
Iterative Incremental Development
ATDD
Risk Management on Agile Projects
Test Driven Development
Agile in the Enterprise
Lean Software Development
Nexus and Kanban
Scrum and XP
Nexus vs SAFe
Managing Risk on Agile Projects
Lean Agile Management
Built-In Quality
Agile Project
Agile Development
Legacy Enterprise
ARTs
SAFe
LAB
Video
agileisrael
Lean and Agile Techniques
The Kanban Method
Development Value Streams
Elastic Leadership
A Kanban System for Software Engineering
Agile Release Planning
Agile Contracts Best Practices
Hybrid Work
Portfolio for Jira
Professional Scrum with Kanban
Perfection Game
Systems Thinking
Self-organization
Agile Delivery
Lean Risk Management
Scrum With Kanban
Agile Project Management
Introduction to ATDD
ROI
Engineering Practices
Scrum Guide
Slides
transformation
Kaizen Workshop
Lean Agile Basics
Agile
Introduction to Test Driven Development
predictability
Legacy Code
ART Success
Software Development
Program Increment
chatgpt
Risk Management in Kanban
Sprint Retrospectives
Lean Agile Leadership
BDD
Professional Scrum Master
Effective Agile Retrospectives
POPM
User stories
Agile Techniques
Jira
An Appreciative Retrospective
Jira admin
Covid19
Scrum Master
Agile Risk Management
Operational Value Stream
SAFe Release Planning
Scaled Agile Framework
Agile Product Development
Agile Israel
Business Agility
Sprint Planning
Implementing SAFe
Entrepreneurial Operating System®
Process Improvement
PI Objectives
Atlassian
Release Train Engineer
AI Artificial Intelligence
Achieve Business Agility
Agile Product Ownership
IT Operations
Frameworks
Kaizen
System Team
Continuous Deployment
Jira Plans
Releases Using Lean
LeSS
Nexus Integration Team
AgileSparks
Logo
Enable registration in settings - general

Contact Us

Request for additional information and prices

AgileSparks Newsletter

Subscribe to our newsletter, and stay updated on the latest Agile news and events

This website uses Cookies to provide a better experience
Shopping cart