To create your board, follow these steps. It is a time boxed event that lasts for 2 days and strives for delivering incremental value. Program Increment (PI) Planning is part of the SAFe (Scaled Agile Frameworks), a regular routined event that occurs with a planning agenda for Agile Release Train teams to align on a shared mission and vision, and to iterate on the next PI. Distributed PI Planning with SAFe Bringing everyone on an Agile Release Train (ART) together for PI Planning is a significant effort. Steps of PI Planning: For any planning, there are certain points or steps to be followed to make the planning successful. With Professional subscription you get access to advanced PI plannings with JIRA integration, progress tracking while in your PI … At the PI level, pictured below, the Program Board 2.0 can supplement the roadmap shown in Step 1. 1) Create Board. 5. Acceptance Criteria: The board must have the ability to integrate the Epics (not Jira epics), Features (associated to Jira Epics currently) and the associated users stories. Plan Review & Rework. The Program confidence vote is a Fist-of-Five vote from all team members. Step 4. VisualScript PI board follows a standard program increment board format and will scale across multiple teams, projects and even Jira instances with the help of custom fields. Create a PI planning board for Scaled Agile (SAFe), also known as PI board using your Jira data inside Jira and Confluence. Historically, PI Plannings are completed in person on whiteboards with A LOT of stickies and red yarn The Increment Overview is a digital representation of the physical Program Board created during the 2 day PI Planning session. Kendis provides capabilities to create PI Planning and Tracking board integrated to AzureDevOps and it has 2-way sync, so any changes made in Kendis are visible in AzureDevOps instantly and vice versa. Start planning your next program increment online with remote teams, automatic sync and intelligent dependency recognition. Now that the PI planning is over, and the Program Increment has commenced, you face the more granular iterations planning, typically every 2 weeks. As a business expands Agile, expanding PI Planning to multiple events to include all parts of the organization, connecting the ARTs, and the work to the overall business goals, is tricky. As a Scrum Master who is guiding my team through an essential SAFe agile transformation, it would be valuable to have a pre-designed template to support PI planning. Once PI Planning is over, the program board can be a key information radiator for use at Scrum-Of-Scrums. Program Confidence Vote. Effective PI planning for remote teams. Program Increment (PI) Planning is where Teams of an Agile Release Train that are united by a shared vision, meet and plan new features, discuss dependencies and risks. Any vote less than 3 should be explored and commitments potentially re-worked until all team members vote at least a 3. While both the Agile manifesto and SAFe highlight the benefits of face-to-face planning, often organizations will need to run these events across multiple locations. Digitising this limits double handling of information, and also means we can track progress towards Feature completion in real time. With the addition of business agility to the framework, PI Planning (and the pre- and post-PI Planning ceremonies) becomes even more valuable to the business. PI Planning board – The physical or digital Program Increment board which consists of new feature release plan, inter team dependencies for a feature and goals. You will use a dependency board for planning iterations.