Forum Discussion

gse08's avatar
gse08
Frequent Visitor
3 years ago

3 sprint rolling average for throughput

Hi everyone,

 

I'm new in this community and I've been struggling for a couple of weeks because I'm stuck in this problem.  My goal is to calculate a 3 sprint rolling average for the sum of story-points completed. I'm not sure if a DAX measure will work or rather a calculated column. I'm open to any workarounds.

 

Data tables

SprintReportIssues which is the principal table I'm using to produce all the visuals

DateSprint which is a reference table I created for filtering/labeling purposes

Boards which I'm using for the slicer and to filter by BOARD_NAME

 

I've produced some images to explain the problem

 

SprintReportIssues

 

The data has many boards (BOARD_ID and BOARD_NAME), that are composed by many sprints (SPRINT_ID and SPRINT_NAME) which have many issues (ISSUE_ID and ISSUE_KEY). POINTS COMPLETED is a measure I created to calculate the sum of CURRENT_ESTIMATE if SPRINT_REPORT_STATUS = "COMPLETED'

 

DateSprint

 

I'm using this table to group sprints by their dates (DATE). In DateSprint, DATE = START_DATE in SprintReportIssues. REFERENCE is just my preferred way of labeling

 

Matrix of Interest

 

You can see that the visual is summarizing POINTS COMPLETED by:

Rows: SPRINT ('DateSprint'[REFERENCE]) and SPRINT_NAME ('SprintReportIssues'[SPRINT_NAME])

Values: START_DATE ('DateSprint'[DATE]) which I use to sort and POINTS COMPLETED('SprintReportIssues'[POINTS COMPLETED])

 

Expected Outcome 1

 

I want a 3-sprint Rolling Average per REFERENCE. Usually sprints are 15 days so we'd be looking at the current sprint that we want to calculate and ~30 days back

 

Expected Outcome 2

 

Ideally, with this Rolling Average I'd be able to filter by BOARD_NAME using the slicer and we'd be able to see Rolling Averages a level down (per board)

 

Complexity

 

There are 36 boards and 871 sprints for now. In the images above the measures are grouped by board but in the future I'm looking to have the capability of grouping boards by some other reference that I will call "X" for now.  Hierarchy:

Highest Level                          Lowest Level

X             >        Boards      >     Sprints

 

Sample Data

Reminder: POINTS COMPLETED is a measure

SPRINTSPRINT_NAMEEarliest DATEPOINTS COMPLETED
2023.01.32023.01.3 - Analytics2/8/2023 0:0021
2023.01.32023.01.3 - Data Product2/8/2023 0:0018
2023.01.32023.01.3 - EDW Replatform2/8/2023 0:0075
2023.01.32023.01.3 - On Prem Data WH2/8/2023 0:006
2023.01.32023.01.3 -Data Mgmt & Arch2/8/2023 0:0026
2023.01.22023.01.2 - Analytics1/25/2023 0:0018
2023.01.22023.01.2 - Data Product1/25/2023 0:0018
2023.01.22023.01.2 - EDW Replatform1/25/2023 0:0091
2023.01.22023.01.2 - On Prem Data WH1/25/2023 0:0013
2023.01.22023.01.2 -Data Mgmt & Arch1/25/2023 0:0040
2023.01.12023.01.1 - Analytics1/11/2023 0:0022
2023.01.12023.01.1 - Data Product1/11/2023 0:0018
2023.01.12023.01.1 - EDW Replatform1/11/2023 0:0084
2023.01.12023.01.1 - On Prem Data WH1/11/2023 0:0024
2023.01.12023.01.1 -Data Mgmt & Arch1/11/2023 0:006
PI6 - IPPI6 - IP - Analytics12/28/2022 0:0012
PI6 - IPPI6 - IP - Data Mgmt & Arch12/28/2022 0:0012
PI6 - IPPI6 - IP - EDW Replatform12/28/2022 0:00112
PI6 - IPPI6 - IP - On-Prem Data WH12/28/2022 0:0015
PI6 - IPPI6 - IP- Data Product12/28/2022 0:0026
PI6 - S5PI6 - S5 - Analytics12/14/2022 0:007
PI6 - S5PI6 - S5 - Data Mgmt & Arch12/14/2022 0:0011
PI6 - S5PI6 - S5 - EDW Replatform12/14/2022 0:0019
PI6 - S5PI6 - S5 - On-Prem Data WH12/14/2022 0:0010
PI6 - S5PI6 - S5- Data Product12/14/2022 0:0013
PI6 - S4PI6 - S4 -  Data Mgmt & Arch12/1/2022 0:0015
PI6 - S4PI6 - S4 - Analytics12/1/2022 0:0027
PI6 - S4PI6 - S4 - EDW Replatform12/1/2022 0:0050
PI6 - S4PI6 - S4 - On-Prem Data WH12/1/2022 0:0024
PI6 - S4PI6 - S4- Data Product12/1/2022 0:008
PI6 - S3PI6 - S3 -  Data Mgmt & Arch11/16/2022 0:003
PI6 - S3PI6 - S3 - EDW Replatform11/16/2022 0:0060
PI6 - S3PI6 - S3 - On-Prem Data WH11/16/2022 0:0028
PI6 - S3PI6 - S3- Analytics11/16/2022 0:0016
PI6 - S3PI6 - S3- Data Product11/16/2022 0:009
PI6 - S2PI6 - S2 -  Data Mgmt & Arch11/2/2022 0:00 
PI6 - S2PI6 - S2 - Analytics11/2/2022 0:0014
PI6 - S2PI6 - S2 - EDW Replatform11/2/2022 0:0025
PI6 - S2PI6 - S2 - On-Prem Data WH11/2/2022 0:004
PI6 - S2PI6 - S2- Data Product11/2/2022 0:0017
PI6 - S1PI6 - S1 -  Data Mgmt & Arch10/19/2022 0:005
PI6 - S1PI6 - S1 - Analytics10/19/2022 0:006
PI6 - S1PI6 - S1 - EDW Replatform10/19/2022 0:0036
PI6 - S1PI6 - S1 - On-Prem Data WH10/19/2022 0:009
PI6 - S1PI6 - S1- Data Product10/19/2022 0:0019

 

Please help! I've been stuck for so long in this problem and I'm not sure if it cannot be solved because of the sprint order and the dates, or if there's another impediment.

 

3 Replies