General

Currently it seems the IP sprint is also considered in the reports for velocity and capacity (maybe also in the upcoming BurnUp?) But the IP should not be considered here as it is not used for delivering and therefore not useful for predictability. Also if this is considered in the Burnup, adding Issues to IP after PI planning would be considered as scope change which is not the case.

Many of my teams are asking for Agile Hive specific fields to be added to our Board Issue Detail View. However, these fields are not available. These are the fields most commonly requested: Team level: Program Increment (Story, Objective), Planned Business Value (Objective), Actual Business Value (Objective), Uncommitted Objective (Objective) Program Level: User-business Value, RROE, Time Criticality, Cost of Delay, Job Size, WSJF, Program Increment, Teams Involved Solution & Portfolio Level: User-business Value, RROE, Time Criticality, Cost of Delay, Job Size, WSJF Risks: Impact, Probability, Exposure, Residual Impact, Residual Probability, Residual Exposure, Program Increment, Teams Involved Impediment: Program Increment, Teams Involved It should be noted that fields like Planned Start Date, Planned End Date and Epic Owner ARE available and we are using them, but the list of fields above would greatly assist in efficiency of use.

Not currently supported I know, but WHEN is it planned to be possible to use Agile Hive connected to Jira Cloud instance?

Would be appreciate by Management if we could display Agile Hive Reports in Confluence using Macros. E.g. to show "Program reports"

As PM/SA/stakeholder would like to recognize in which PI a program issue (feature, enabler) is planned and see directly deviating planning from teams: Example: A feature is planned in the roadmap for PI22. The tag in the feature appears "green". A team is now planning an additional story (child of feature) in a leading PI (PI21) and an additional story in a later PI (PI23). The feature shows the PI tag PI21 "blue", PI22 "green", PI23 "blue".

It will be very useful for teams to be able to quickly see the current status of a Feature or story when looking at the various views. As an example, the Program Board and the team Breakout views. This is important not only when doing big room planning but also when tracking progress during a PI

We have a large instance, and the cron job for recalculation runs for 12 hours, loading our cpu to 60% before our users have added load. We would like to be able to edit this cron job from the settings screen to run weekly at configurable times.

It would be useful to be able to re-order and group teams in the breakout views to better view dependencies within sub-groups in an ART.

When running the manual recalculation, it would be nice to have displayed the start and end time, as well as the duration. Particularly in understanding the impact to system performance, it would be helpful for this to be displayed. This would also be helpful to display so if there are multiple system admins, they can see either 1) the manual recalculation is running; or 2) when the last run was completed and it's status (success or failure). Similarly, it would also be good to display the same information for the cronjob when enabled. That way, it is easy to see when it ran and the status of the run. This will also be helpful if needing to adjust the overall cron schedule if the job runs longer than anticipated.

We had several teams complain about the forecast line for the PI Burn-Up chart showing a downward path from the current done total. In the screen snapshot provided, the current “Done” is 313, and the slope of the forecast line is downward from 313 to 221 (which is the “forecast”). This appears to be inconsistent with how the burn-up chart should be reporting once the completed (Done) to date exceeds the “forecast” value. It would be expected that the forecast line at that point should take into account the current PI’s burn rate and use that to project the end point. We are seeing this at both the ART and Team levels. (Also entered as Bug report since not sure if this was intended functionality: https://jira.apps.seibert-media.net/servicedesk/customer/portal/13/HELP-5454 )