Bookmark the link: Predictablity chart in EasyBI
Request access to EasyBi through YME Information Systems Support Portal. Select Infra Servicedesk form, select Application-Module Jira - Access/Authorization on the form.
Predictability is "the ability of a scrum team to plan their work in an efficient manner, as to be able to follow through on the created plan."
It is important to note that Predictability does not speak to the value of the items built; it is essential to always link a Predictability chart to a results chart like Business Value, in order to understand what the team truly brings to the organisation.
The EasyBI report draws on data from the YME Jira instance to create an automatic chart for all scrum teams.
TEAM SELECTION: Any team from Jira field "Yamaha Team" can be selected in the dropdown, even though not all teams work using scrum. For this reason it is important to be aware which teams actually work in sprints, and not use the graph for other teams.
ISSUETYPE SELECTION: The standard issuetypes considered in this report are: Bug, Change Request, Defect, Incident, Spike, Story, and Task. It is possible to make your own selection of relevant issuetypes.
PERIOD SELECTION: The standard period considered in this report is 6 monts into the past, plus 3 months into the future. This should allow insight into the recent past to be used in retrospectives, plus insight into the planning for upcoming quarter as forecast. It is possible to make your own selection for the period.
SPRINT SELECTION: The sprints considered in this report are those Active, Closed, and Future (meaning all sprints). It is recommended not to change this. Please note: any sprint which had a story in it that at any point has been assigned to the chosen team will be shown.
Let us consider how the data is defined based on an example.
STORY POINTS COMMITTED (dark blue bar): All story points on items in sprint at the date of sprint start are counted (not the press of the button to make the sprint active). It is vital to set the correct date & time for sprint start - to start only after your sprint planning session.
STORY POINTS ADDED (blue bar): Any story points on items added to sprint after the sprint start date will be counted in this bar.
STORY POINTS CHANGE (light blue bar): Any change in story points to stories that were committed in sprint will be counted in this bar. The bar can be positive (showing on top of the COMMITTED + ADDED), or negative (showing below the 0 Y-axis).
STORY POINTS AT CLOSING (green bar): All story points with a status category "done" in sprint at the date of sprint end are counted. It is vital to close your stories before the end of your sprint, and not later.
PREDICTABILITY (orange line): STORY POINTS COMMITTED and STORY POINTS AT CLOSING are compared. If they are equal, Predictability is 100%. If they are not equal, Predictability drops by the difference. (for details, see addendum)
SPRINT ISSUES ADDED (red line): The amount of stories added to sprint after the sprint start date are counted. These are disturbances, while are likely detrimental to STORY POINTS AT CLOSING.
STORY POINTS FORECAST (turquoise bar): Any story points on items in future sprints are counted in this bar, showing the preparedness of the team for the future.
1) To check why a data point is shown in the graph, it is possible to view the underlying Jira data. To do so, click on the bar or point you are interested in, and choose "drill through issue".
2) The following pop-up will allow you to click and open a specific item in Jira, open the selection in Jira, or download the report overview to local drive as .CSV or .XLS.
3) This example shows a green bar, but no blue bar, and as a result to Predictability value either. This is caused by the 6 month time constraint. The sprint planning falls outside of the period, while the sprint closure falls inside it. This makes it a useless datapoint for the current graph.
4) To remove an uninteresting data point, click on the sprint, then choose "remove". This will remove the data point until you refresh the application.
5) When sprints from other teams are shown in your chart, this is likely because you have exchanged a story - something that was in their sprint previously and you completed, or something that was in your sprint previously that they completed. If this is the case, the best remedy is to remove the data point.
Alternatively, other team's sprints can be shown because your team or story is assigned incorrectly - this can be fixed by drilling through the item and correcting the data in Jira.
If you complete 0 storypoints, then Predictability will be 0. However, if you complete twice the amount of storypoints of what you've planned, then Predictability will also be 0. It will be 100% when you complete as many storypoints as you planned. Make sure to only make scope changes together with PO, to optimise Business Value.
CASE
WHEN
[Measures].[Sprint Story Points at closing] <=
[Measures].[Sprint Story Points committed]
THEN
([Measures].[Sprint Story Points at closing]/
[Measures].[Sprint Story Points committed])*100
WHEN
([Measures].[Sprint Story Points at closing]/
[Measures].[Sprint Story Points committed])*100 >= 100 AND ([Measures].[Sprint Story Points at closing]/
[Measures].[Sprint Story Points committed])*100 <= 200
THEN
ABS((([Measures].[Sprint Story Points at closing]
/ [Measures].[Sprint Story Points committed]) * 100) -200)
WHEN
([Measures].[Sprint Story Points at closing]/
[Measures].[Sprint Story Points committed])*100 > 200
THEN
0
END
Link (Under construction)