Why is Team Spend per Point for KanBan team not calculating?

Stephen_Miller_wo6797

Portfolio in Jira Align (Build: 10.132.3.44303) has only one Team which is a Kanban team linked to Jira.  Since this is Kanban there is no estimated spend values.  Accepted Stories with Story Point values are showing as Accepted in Parent Epics (rolled up from Stories) but is showing no 0 value for Spend on both Stories and Epics,  

At the team view, Five weeks of processing show a Throughput of 7 Stories/wk.  Burn Hours are set to 6. 

Six team members are allocated at 95%  (allocation we set on 5/9/24 - previously was 0)

Program Increment has Blended Rate of $50.

What am I missing for Align to calculate Team Spend per Point, and therefore show Accepted Spend value?

Steve Sauser

@Stephen_Miller Thank you for asking about this functionality, please see below for why this is likely not being calculated (these Kanban Teams are likely not adding any point value for their stories, and/or they don't have Team Roles and/or they don't have allocations set).  

Kanban Teams often resist the pattern of Estimating Stories.

• Remember that Capitalization Method is set at the Portfolio level and either all Teams in the Portfolio use Story Points or Task Hours.

  • You can use the “Auto-populate Estimate” for Kanban Teams and this will populate a default value for Stories (only the first time they are integrated into Align).

    • The default ONLY applies if the points are empty at the first time the story is integrated into Align.

      • Zero is an actual value and is not treated as empty.

    • Each Kanban Team could be different for the Estimate so we highly encourage understanding the teams appropriate default value, revisit as necessary.

    • Existing stories would need to be updated to reflect the default value when implementing this on an existing team. This can be accomplished via a JQL query and a bulk update in Jira which will update JA.

• Burn Hours is the value of how many hours are available for “Focus Time” daily per identified Team Members on the team.

  • This value must be populated for each Team and is typically defaulted to 6, but can be altered to be 5, 6, 7, or 8.

• Track By can be set to either Points or Hours, however it is important that this match the Capitalization Method for the Portfolio the team is allocated to.

• All Members of the Team must be in a Team Role

• All Members of the Team must be allocated (by % of dedication to the team).

  • Only “Allocation” and not “Defect Allocation” is used.

  • Without these allocations the Accepted Spend cannot be calculated.

Accepted Spend:

• Calculated by adding together the spend of stories related to the feature, capability, or epic.

• Based upon effort point estimates from accepted child stories.

Estimated Spend

• Feature: Calculated by multiplying the feature estimate by its program's Spend per Point.

• Capability/Epic: Calculated by adding together all the feature estimations (Spend per Point) related to this capability or epic.

• Based upon feature estimates, entered on the main tab of a feature's Details panel. 

  • Note: Feature Forecast flows back to the Details panel when the Sum All is selected for the Planning Interval Estimate.

Forecasted Spend (Epic, Capability, Feature)

• Calculated by multiplying each program forecast by its program Spend per Point.

• Based upon the program PI estimates entered on the Forecast tab of an epic, capability, or Feature.

  • Note: Feature Forecast flows back to the Details panel when the Sum All is selected for the Planning Interval Estimate.

Budget is set at the Epic Level on the Spend tab.