- #The ultimate books of pi pdf driver#
- #The ultimate books of pi pdf full#
- #The ultimate books of pi pdf code#
- #The ultimate books of pi pdf series#
You might need to do some work to enable another team to work on their feature first (and vice versa)Īs a result, teams can get things done more effectively, release more features in less time, and stay on budget.Īll very good reasons to do PI Planning. 
#The ultimate books of pi pdf code#
When you’re touching a system or a code repository, you need to know how it’s going to impact another team. They get the chance to nut out those important conversations about who’s working on what. PI Planning is the first time many of these really big companies get their teams together in a room or on the same call and talking to each other. Speaking of projects, these had a habit of conflicting - one team would release something and then it would break something in another team’s project. There would be a constant battle for resources, budget, and opportunities to work on the sexiest projects. Previously, alignment would have been at the leadership team level, and they’d have multiple levels of managers in between who cascade information down, but the people on the teams would never talk to one another. 😢(until there was a critical problem that forced them to talk) In the old way of working, these teams would never have spoken to one another before. For example, some larger organizations might have 200-300 teams and 10,000 developers. To understand the impact, let’s look at some numbers. PI Planning is incredibly beneficial for large scale agile organizations. #The ultimate books of pi pdf driver#
Whether you’re adopting all 5 levels or just essential SAFe, the foundation of your transformation and the driver for everything is the PI Planning ceremony. The framework is geared at improving visibility, alignment, and collaboration and should lead to greater productivity, better results, and faster delivery.
#The ultimate books of pi pdf series#
Quick definition: SAFe or the Scaled Agile Framework™ is a series of guidelines and practices designed to help bring agility into larger organizations, across all teams and levels of the business. That’s because it forms the foundation of the Scaled Agile Framework. If you’re adopting SAFe for the first time, chances are, it’ll start with PI Planning.
Technology is used to allow distributed teams to participate (if needed). Everyone attends in person (if possible). The goal is to align the teams to the mission and each other. Engineers and UX teams work to validate the planning. Development teams own user story planning and estimation. Product Managers work to prioritize the planned features for the increment beforehand. #The ultimate books of pi pdf full#
2 full day events run every 8-12 weeks (depending on the length of your increments). Here are the essential elements of PI Planning: PI Planning sessions are regularly scheduled events held throughout the year where multiple teams within the same Agile Release Train (ART) meet to align to a shared vision, discuss features, plan the roadmap, and identify cross-team dependencies. PI Planning stands for Program Increment Planning. Tips for distributed teams and remote PI Planning. What should we do to prepare for PI Planning?. What is the difference between a PI Roadmap and a Solution Roadmap?. What does SAFe have to do with PI Planning?. What is a pre-PI Planning event and when is it needed?. Why is a confidence vote held at the end of PI Planning?. What is accomplished in the first part of the PI Planning meeting?. What should be included in the PI Planning agenda?. This PI Planning Ultimate Guide ain’t short, so if you want to scroll ahead to a bit that’s most interesting/useful to you, be our guest. In this guide we answer a bunch of FAQs about PI Planning so you can feel confident enough to be part of an event (and start using all the lingo). 
We’ll help destroy the myths and crack the code to running successful and effective SAFe PI Planning sessions. We’ve put together this complete guide to PI Planning in 2020. Or maybe you’ve been doing PI Planning for a while now, but it’s not running too well and you’re thinking of throwing in the towel. When you’re getting started with scaling agile in your company, the thought of bringing multiple agile teams together in the one room is enough to bring on cold sweats.
0 kommentar(er)
