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 risk Category and Resolution type from the drop-down list.

You can add or modify the Risk at the Program level, which is then rolled up to the Portfolio level and displayed there as a read-only field.


Note1: The drop-down values for the Resolution is pre-defined by the guidelines set by SAFe®. To know more about them, read the Program Risks section of the PI Planning page on the scaledagileframework.com.
Note2: The drop-down value for the Category can be configured using the Master List. To know more about creating a master List, see this topic

Business Value 

As the objectives are set during the PI planning, business owners can assign relative business value on a scale from 1 to 10 (10 being the highest). You can add Business Value Objectives for each of the teams under any ART.

You can add or modify the Business Value at the Program level, which is then rolled up to the Portfolio level and displayed there as a read-only field.

To create a Business Value (BV) Objective, perform the following steps:

1. Select the ART and the Team for which you want to set the Business Value (BV) Objectives.
2. Enter the description of the BV and the Planned value for that BV. Click the Add   icon.
3. At the end of the PI, the business owner will enter the Actual value they think, is achieved by the team against the planned value for that BV.
4. To delete any existing BV, click the Delete  icon.

Note: You will not be able to add any BV if you select All Teams from the Team drop-down list, because the BVs are supposed to be set differently for each team.

Share 

Share the PI across other boards by clicking the share icon, and then selecting the boards that you want to share with. Once the PI has been shared, it appears on the PI drop-down attribute of any card across those shared boards.
Note: Any PI created at the Program level Work Board, will automatically be shared with its Child board.

Sprint

In SwiftEASe, it is easy and quick to break down a PI into several sprints with the intuitive drag-n-drop interface. You should have a PI backlog defined so that cards from the PI scope can be associated to different sprints you create. The sprint capacity and progress can be visually tracked as it progresses and also rolled up to the PI progress, where again the visual indicators are based on these sprints.
You can directly push cards to the Work Board from the Sprint Scope itself.

To define a sprint, perform the following steps:

1. Go to the PI page (Board > PI) and click the Sprints icon for the required release. Alternatively, you can access the Sprint page directly from the Work Board menu. In the Sprints page for the PI, click Add New Sprint and enter following details:

    • Sprint Name: Name of the Sprint, which is mandatory.
    • Start Date and End Date
    • PI: Read-only field.
    • ART: Select the ART for which you want to allocate the user stories for the new Sprint.
    • Team: Select a Team under that ART who will be allocated the User Stories for the new Sprint.
    • Capacity: Enter the capacity either in Points or estimate values of To-Do’s or as per the UOM defined.

Note: The Capacity can be entered only when you select an ART and a Team under that ART. If the Team field is selected as ALL, then the Capacity field will be in read-only mode.

The Sprint screen is divided into two columns that are Not in Sprint and Sprint ScopeNot in Sprint is further divided into two columns that are Backlog Cards and Board Cards.
• Backlog Cards: Contain those backlog cards which are in the PI Scope.
• Board Cards: Contains those board cards which are in the PI Scope.

2. To define the Sprint Scope:

• Drag cards from the PI Cards to the Sprint scope. The cards you drop into the sprint bucket will be associated with the sprint.
• Before you pick up the cards in the backlog (indicated by a green Status line), you can run through the Card Title and the estimate, or click the card title link to view its details. On clicking back in the Detail view, you return to the Sprints page.
• Locate the card by scrolling through the pages by clicking the page numbers below or clicking first previous, next and last links. To limit the cards in the view, set the card count in the right corner, for example, 25 shows 25 cards on a page.
• To filter the columns to view specific cards, click the Filter  icon on the top right. Type the search string in the empty filter text boxes or select value(s) in the Filter drop-down lists.
• To remove a card added to the Sprint scope, drag and drop the card back into Not in PI column. Doing this will disassociate the card from the sprint but still keep the card active in the PI.

3. Click the Close (x) icon after you are done. The Sprints page lists all sprints you defined along with the details i.e. sprint dates, card count, progress, and capacity estimated.

4. To view the cards scoped in the past sprints, click the sprints row, and to hide the details, click it again. Thus, you can access the past sprint details to plan a new sprint better.
Note: The UOM for Estimate is To-Do’s by default. You can change the UoM to Points through the drop-down on the list of PI screen.

• The Card Count displayed for the newly added sprint indicates the number of cards scoped in the sprint.
• The Progress bar for the sprint indicates the sprint progress, which shows a percentage of points or To-Do vales achieved over the total points or To-Do values scoped.
• The Sprint capacity indicator denotes to what extent the sprint is booked or under-booked (white band in the capacity bar). The bar completely in red indicates that the sprint is overbooked. On hovering on the Capacity bar, you can view the capacity booking in the percentage that is the sum of estimates of To-Do values or points scoped in the sprint over the sprint capacity entered.
• To re-scope the sprint, double-click the required sprint and drag and drop cards from Release cards column to the sprint scope column or vice versa.
• To share a sprint across other boards, click the Sprint icon.
• To delete a sprint from the enterprise permanently, click the Delete icon for the required sprint.
To close a sprint, click the Close icon on the extreme right of the toolbar for the specific sprint. If you want to activate a closed sprint again, click the Open icon for it.

Chart 

SwiftEASe provides the PI Burndown chart for the team to track its progress against a PI plan in their daily scrum meetings. Burndown charts that can be tracked for any board containing tasks with estimates and actual effort, is a graphical representation of outstanding work (or backlog) against time. It is useful for predicting when all the work scoped in the PI plan will be completed. By default, the UOM for the Burndown chart will be Points.

Note: You can plot the Burndown chart for the current Board and its child Boards at the lower level . For example, if you are plotting the Burndown chart via Lean Analytics from a Program level workboard, then the chart fetches data from that Program Work Board and also from its child Team Work Boards .
You can further use the filter in the refine the scope of the chart based on card type. For example, if you want to view only the Team level Burndown chart, then you can select card types like User Story, Technical Story, Issue and Defect.

To view the Burndown chart for a PI:

1. Select PI from the Selected Work Board menu.
2. Expand the required PI by clicking the PI row and click the Charts icon for the PI. The Burndown chart is displayed below showing how remaining effort comes to ‘0’, which also is a burn-up chart if you track the progress of Actual Effort.
3. Click the Close icon to close the chart.

• Interpret the Actual, Planned, and Remaining values in points only as team members will be entering actual points covered.
• The PI Burndown chart plots the sum of all Daily Remaining Effort on the Y-axis against the dates on the X-axis (from the PI start date through the PI end date). The remaining burndown slope is the red dotted line indicating the remaining points as the PI moves through the end date.
• The PI Burnup line in green is plotted for the sum of all Daily Actual points achieved on the Y-axis against the dates on the X-axis (from the PI start date through the PI end date).
• The chart also shows a blue dotted line indicating the planned slope i.e. how the points should have been completed through the PI ideally. It is the sum of remaining points for cards on the PI start date through the PI end date closing at ‘0’.

You can filter the Burndown chart to view it for specific card types. Click the Filter icon on the chart toolbar. The filter will apply even for export in MS Excel format.

PI Burndown Export

The PI Burndown can be exported in MS Excel format, along with the Burndown data.Click the Export icon on the chart toolbar at the top-right.
You can open the file in MS Excel or your preferred spreadsheet application. You can click the Filter icon to export the chart and burndown data for specific card types.

Delete PI 

To delete a release from the account permanently, click the Delete icon for the required PI.

Close PI 

If you don’t want a PI to be available for tagging cards to it, you can close such as inactivate the PI. To close a PI, click the Close icon on the extreme right of the toolbar for the specific PI.

When you are adding or editing a card on the board or from its detail view, the PI drop-down will not show the PI anymore.
If you want to activate a closed release again, click the Open icon for it.

  • Was this helpful?
  • Yes   No