Measuring progress of high-level planning entities: Features, Epics, Projects, Releases, Sprints, Team Iterations | Targetprocess - Visual management software

Measuring progress of high-level planning entities: Features, Epics, Projects, Releases, Sprints, Team Iterations

In Targetprocess, total Effort is used as one of the key metrics in work progress tracking. High-level scopes of work such as features, epics, projects, releases and iterations do not have their own effort. Instead, you can assign work items to them. Effort for the high-level scope entity becomes equal to total amount of effort of all assigned entities.

To reflect actual progress, Effort value is divided into Remaining (To Do) and Completed part:

Measuring progress of high-level planning entities: Features, Epics, Projects, Releases, Sprints, Team Iterations. Image 1

For every high-level planning entity totals for both Effort Remaining and Effort Completed are automatically calculated across smaller work items (such as User Stories, Tasks, Bugs) assigned to them. It makes possible to overview current progress of any entity from bottom to the top of your backlog.

Progress calculation for Features

Progress for Feature entity is calculated using assigned effort and progress of its user stories and nested tasks.

If a Feature has no user stories, then its progress is based on its workflow state.

  • 0% when feature is New or In Progress
  • 100% when feature is Done

feature-progress-open

Progress calculation for Features

Otherwise overall progress of the feature is calculated from progress of assigned user stories.

Progress = SUM ( EffortCompleted ) / SUM ( Effort )

Let's consider a use case when a Feature has two user stories:

  • User Story 1: Effort 5 pt, Progress 100%
  • User Story 2: Effort 0 pt, Progress 0%

In such case the user story with zero effort does not contribute into total progress calculation. Total progress for the Feature will be 100%.

Progress = ( 5*(100/100) + 0*(0/100) ) / ( 5 + 0 ) = 5 / 5 = 1 = 100%

story-zero-progress

Let's now estimate User Story 2 and assign 2 pt effort to it.

Progress of the Feature becomes the following:

Progress = ( 5*(100/100) + 2*(0/100) ) / ( 5 + 2 ) = 5 / 7 = ~0.71 = 71%

Measuring progress of high-level planning entities: Features, Epics, Projects, Releases, Sprints, Team Iterations. Image 5

When you move a Feature to its final state (Done, Closed) its progress becomes equal to 100% even if this Feature still has incomplete user stories.

Measuring progress of high-level planning entities: Features, Epics, Projects, Releases, Sprints, Team Iterations. Image 6

Effort and Time Spent of nested Bugs is not included to the total Feature effort and time spent values. It is possible to set up custom calculations and get total Bugs count, effort, time spent, cost displayed per Feature. Learn how: Metrics for Bugs in User Stories and Features.

Progress calculation for Iterations, Sprints, Team Iterations

Progress for Iteration, Team Iteration entity is calculated using assigned effort and progress of its user stories and bugs.

Progress = SUM ( EffortCompleted ) / SUM ( Effort )

Let's consider a use case when an iteration has two user stories and one bug assigned:

  • User Story 1: Effort 5 pt, Progress 100%
  • User Story 2: Effort 2 pt, Progress 0%
  • Bug B: Effort 3 pt, Progress 100%

Progress of the Iteration becomes the following:

Progress = ( 5*(100/100) + 2*(0/100) + 3*(100/100) ) / ( 5 + 2 + 3 ) = 8 / 10 = 0.8 = 80%

Progress calculation for Iterations, Sprints, Team Iterations

Effort of standalone Tasks assigned to Team Iterations without their parent User Stories is not included into progress calculation. This use case should be handled with custom calculations based on Calculated Custom Fields.

Progress calculation for work items

Progress of any work item such as User Story, Task and Bug is based on its Effort and Time Spent data. Learn how Progress is calculated for work items in Targetprocess.

Burndown chart

Burndown chart for Release, Iteration (Sprint) and Team Iteration displays current progress and effort required for work completion. This chart gives an actual forecast of when you can expect all the work to be completed. It also shows the actual velocity, that is, an average effort of work done by a team over a given period of time. In Targetprocess Burndown chart, effort is shown on the vertical axis of the chart, and timeline — on the horizontal axis.

Burndown chart

Measuring progress of high-level planning entities: Features, Epics, Projects, Releases, Sprints, Team Iterations. Image 9

Release Progress Tracking

Release Planning view helps to track progress of your features across releases and easily balance the releases workload. Total effort of all assigned features is shown in the column header for each release. Total amount of completed effort is also displayed. Effort of each feature can be added to cards layout as well.

Release Progress Tracking

Estimation Accuracy: Initial estimate vs Effort and Time Spent for Portfolio Epics, Epics and Features

It is possible to compare Initial Estimate, Effort and Time Spent for every portfolio epic, feature and epic. Set up visual encoding that allows to compare Initial Estimate and Effort for every epic or every feature.

Comparing Effort and actual Time Spent makes more sense when we are estimating in ideal hours and not in story points.

Compare effort

Various estimation accuracy reports can be built for the same purpose.

Still have a question?

We're here to help! Just contact our friendly support team

Find out more about our APIs, Plugins, Mashups and custom extensions. Join our community of passionate users and even discuss directly with our developers.