10X: Agile Earned Value (Stories)

About this report

The Agile Earned Value (Stories) report is a light-weight Agile EVM (Earned Value Management) report that is an adaptation of the traditional EVM technique. It provides the benefits of traditional EVM and applies them to Agile projects. The result is a simple set of metrics used for communicating progress and overall performance for stories. Using this information, metrics assessing cost efficiency and schedule efficiency are calculated. Metrics forecasting the expected cost to complete a project and total expected cost of a project based on past project performance are derived. 

Point to any portion in the Date axis to see points completed, points expected, and points scheduled at any given date in the time period configured for that PI. You can select or clear the check boxes at the bottom of the chart to toggle the display.

You can filter the chart by PI, program, release vehicle, theme group, and Scrum Masters/product owners. 
Prerequisites

  1. EVM fields must be configured in Administration > Settings > Platform.
  2. PI must exist in the system and be tied to a program. 
  3. Epics must be created and tied to a program and PI. 
  4. Features must be created and tied to the PI.
  5. Stories, with point values, must be created and tied to features.
  6. Tasks must be created and tied to stories.
  7. Task hours/time entered must be logged for the tasks. 

How are report values calculated? 

  1. Start Date on Chart = PI Start Date
  2. End Date on Chart = PI Finish Date
  3. Points Completed = Sum of All Effort Points on Accepted Stories on Each Day of the Report Time Period
  4. Points Scheduled = Sum of All Effort Points on All Stories Scheduled in the PI, expressed as an Ideal Upward Trend from the PI Start Date to the PI Finish Date
  5. Points Expected (Velocity) = Sum of All Effort Points on Accepted Stories For the Past 9 Completed Synch Sprints (Velocity), for All Teams, expressed as an Ideal Upward Trend from the PI Start Date to the PI Finish Date
  6. Program Increment Start Date = PI Start Date  
  7. Program Increment End Date = PI Finish Date
  8. Points Expected (PE) = Sum of All Effort Points on Accepted Stories for the Past 9 Completed Synch Sprints
  9. Points Scheduled (PS) = Sum of All Effort Points for All Stories Scheduled in the PI
  10. Budget at Complete (BAC) = Points Expected (PE) * EVM Billing Rate * EVM Story Multiplier  
  11. Days Remaining (DR) = Days Remaining Between Today and the PI Finish Date
  12. Points Complete (PC) = Sum of All Effort Points on Accepted Stories on Each Day of the Report Time Period
  13. Actual Cost (AC) = Total Hours Spent on Tasks, Bugs and Disciplines Times EVM Billing Rate
  14. Billable Rate = EVM Billing Rate
  15. Expected Percent Complete = Total Days in PI – (Total Days in PI / Days Remaining (DR))
  16. Actual Percent Complete = Team Weeks Complete (PC) / Points Scheduled (PS)
  17. Planned Value = Expected Percent Complete * Budget at Complete (BAC)
  18. Earned Value = Actual Percent Complete * Budget at Complete (BAC)
  19. Estimate At Completion = Actual Cost (AC) + (1 / Cost Performance Index * (Budget at Complete (BAC) * Earned Value))
  20. Schedule Performance Index = Earned Value / Planned Value
  21. Cost Performance Index = Earned Value / Actual Cost
  22. Velocity (Last 9 Sprints) = Sum of All Effort Points on Accepted Stories For the Past 9 Completed Synch Sprints (Velocity), for All Teams
  23. Multiplier = EVM Story Multiplier

How to interpret this report

Note that unlike a burndown chart, an Agile EVM report captures cost information, and therefore provides the ability to validate whether the teams will complete all of the work planned for the PI within both schedule and budget. This gives the Product Owner (who "owns" the backlog) early information about the cost effects of changes to the overall effort. Ideally, work to get the Points Completed line to closely match the Points Scheduled line, which represents the Ideal Upward Trend from the PI Start Date to the PI Finish Date. Also try to be a close to, or higher than, the Points Expected (Velocity) line to maintain or increase the average velocity across all teams.

Was this article helpful?
0 out of 0 found this helpful
Print Friendly Version of this pagePrint Get a PDF version of this webpagePDF

Join the Atlassian Community!

The Atlassian Community is a unique, highly collaborative space where customers and Atlassians come together. Ask questions and get answers, start discussions, and collaborate with thousands of other Jira Align customers. Visit the Jira Align Community Collection today.

Need to contact Jira Align Support? Please open a support request.