Program Increment (PI)

Information related to Program Increment (PI)

Working with Planning Event

To facilitate better planning and optimization of human capital, many organizations do a “plan-ahead” to help to scenario planning and what-if analysis. SwiftEASe Planning Event enables the team to do exactly that. Given the available Capacity across Teams and ARTs and work prioritization as per WSJF (outside the system), SwiftEASe helps you to allocate planned work […]

Important Information for the PI Planning

While planning for a Program Increment (PI) using the PI page, you must remember a couple of important points that would help you get a complete clarity over the PI planning. Cards Shown in PI Scope Versus Cards Considered in the Burndown Chart The cards shown in the PI Scope will always be those which […]

Working With the PI Menu Bar

You can perform various PI operations like defining Risks, setting Business Values, sharing PI, working with sprints and so on. Let us explore each option below. Risk  You can capture the program level impediments associated with the PI here. Select the ART and the team while adding the Risk name and description. Additionally, select the […]

Understanding the PI Page

You can access the PI page from the Board menu. The PI page can be accessed from any of the Work Board levels, but a PI can be created only from the top-level Work Board.  Once you navigate to the PI page, it shows the list of PIs that you have already created. If you wish […]

Creating A PI

You can create a PI only at the top-level Board. Once you create the PI, it will be available at all the Boards under that top-level Board. For example, if you are creating a PI at the Portfolio-level Board, then the same PI will be available at the Solution, Program and Team level Work Boards. Note […]

Working With Program Increment (PI)

Program Increment or PI is a time-boxed iteration where an ART delivers incremental builds and value in the form of working software and systems. Typically, PIs are eight to twelve weeks long, and the most common pattern for a PI is four development iterations, followed by one Innovation and Planning (IP) iteration. In SwiftEASe, the […]