Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How can demonstrate our sprints completion rate?

Matthew Vanderzee November 9, 2016

In EazyBI, I want to create a chart that lists our sprints, and then shows for each sprint:

  1. The Number of open tickets that were part of the sprint when the sprint was started
  2. The Number of resolved tickets that were part of the sprint when the sprint was closed.  This would not include tickets that were removed from the sprint after it was started, but would include tickets that were added to the sprint after it started.
  3.  #2 divided by #1 - the percent of the original planned sprint that was actually completed during the sprint
  4. The same measures but summing "original estimate" - as in, the total # of hours committed to and then completed, and the % completion rate based on the estimates.

 

Once I can do this for the whole team (demonstrating the sprint-by-sprint success ratio for the team), I would want to create the same graphs per person to see what each team member's success rate is.

What is the best way to accomplish this?

 

 

1 answer

0 votes
eazyBI Support
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 16, 2016

Hi! 

 

Together with Mattew, we got those measures:

1) To get "Sprint committed issues", calculated measure should be created:

 

Cache(NonZero((
  [Measures].[Issues history], 
  [Time].CurrentHierarchy.Levels('Day').DateMember(
    [Sprint].CurrentMember.get('Start date'))
)))

 

2) For Sprint resolved issues, standard measure "Issues resolved" could be used.

 

3) To sum up estimates from committed issues, calculated measure could be the following:

Cache(Sum(
  Filter(
    Descendants([Issue].Currentmember, [Issue].[Issue]),
    [Measures].[Sprint Issues Committed] >0),
    ([Sprint].DefaultMember,
    [Measures].[Original estimated hours]))
)

 

Be aware! As this measure iterates trough all issues and their changelogs, it is quite slow, therefore, should be used only for one or a few sprints selected in the report!

 

4) For Sprint resolved estimated hours, the measure could be the following:

 

(([Measures].[Original estimated hours],
 [Resolution].[Resolved]))

 

where  [Resolution].[Resolved] is a calculated member in Resolution dimension with aggregated all resolutions except (unresolved).

 

5) For ratios, measures with divisions between needed calculated measures were created.

 

Ilze, eazyBI Customer support consultant

support@eazybi.com

 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events