About this report
The Agile Earned Value (Epics) 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 epics and stand-alone features. 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 the team weeks completed and team weeks scheduled. You can select any of the legend labels to show or hide the different lines on the chart.
The display can be filtered by PI, program, release vehicle, theme group, and Scrum Masters/product owners.
- EVM fields must be configured in Administration > Settings > Platform > Program tab.
- PI must exist in the system and be tied to a program.
- Epics must be created and tied to a program and PI.
- Features must be created and tied to the PI.
- Stories, with point values, must be created and tied to features.
- Tasks must be created and tied to stories.
- Task hours/time entered must be logged for the tasks.
How are report values calculated?
- Start Date on Chart = PI Start Date
- End Date on Chart = PI Finish Date
- Team Weeks Completed = Sum of All Team Weeks on Accepted Epics and Stand-Alone Features on Each Day of the Report Time Period
- Team Weeks Scheduled = Sum of All Team Weeks on All Epics and Stand-Alone Features Scheduled in the PI, expressed as an Ideal Upward Trend from the PI Start Date to the PI Finish Date
- Program Increment Start Date = PI Start Date
- Program Increment End Date = PI Finish Date
- Team Weeks Scheduled = Sum of All Team Weeks on All Epics and Stand-Alone Features Scheduled in the PI
- Budget at Complete (BAC) = Team Weeks Scheduled * EVM Billing Rate * EVM Epic Multiplier
- Days Remaining (DR) = Days Remaining Between Today and the PI Finish Date
- Team Weeks Complete = Sum of completed Team Weeks on All Epics and Stand-Alone Features in the PI as of a certain date
- Actual Cost (AC) = Total Hours Spent on Tasks, Bugs and Disciplines Times EVM Billing Rate
- Billable Rate = EVM Billing Rate
- Expected Percent Complete = Total Days in PI – (Total Days in PI / Days Remaining (DR))
- Actual Percent Complete = Team Weeks Complete (PC) / Points Scheduled (PS)
- Planned Value = Expected Percent Complete * Budget at Complete (BAC)
- Earned Value = Actual Percent Complete * Budget at Complete (BAC)
- Estimate At Completion = Actual Cost (AC) + (1 / Cost Performance Index * (Budget at Complete (BAC) * Earned Value))
- Schedule Performance Index = Earned Value / Planned Value
- Cost Performance Index = Earned Value / Actual Cost
- Multiplier = EVM Epic 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 can 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 Team Weeks Completed line to closely match the Team Weeks Scheduled line, which represents the Ideal Upward Trend from the PI Start Date to the PI Finish Date.