EazyBI sprint burn by issue count (not story points)

Luke Sparkes

I'm successfully using a derivative of the Sprint Burn down chart in EazyBI (https://docs.eazybi.com/display/EAZYBIJIRA/Sprint+burn-down+or+burn-up+chart) to monitor an individual team's progress. This measures by Story Points (completed/remaining/committed/etc.)

I would like to produce a similar chart based on Issue Counts, so that I can aggregate the counts across multiple teams who are running sprints in parallel.

I'm aware you cannot compare Story Points between scrum teams (because everyone has a different meaning for an 8pt!) and I'm also aware that I shouldn't compare purely by number of issues (because people will just change this size of their stories to game any measure). What I'm really interested in is observing their commitments and burn/velocity - are they going to meet their collective targets.

Any tips on how to do this with EazyBI?

eazyBI Support

Hi Luke,

you can create an additional burn-down chart using issue count instead of Story points - see an example report https://eazybi.com/accounts/1000/cubes/Issues/reports/67507-issues-burn-down-in-selected-sprint

For multiple parallel sprints, you have to decide how do you want to represent the information in reports - as a common burn-up line for all sprints, or a report for each sprint separately, for example, as the following report (mainly used for ongoing sprints): https://eazybi.com/accounts/1000/cubes/Issues/reports/50010-story-points-burn-down-by-sprints, or another way.

The best way to discuss further details would be to contact eazyBI support directly: support@eazybi.com

Best regards,

Ilze, eazyBI customer support consultant