Skip to Main Content

Share your product feedback

Status Future consideration
Categories Features
Created by Josh Tambor
Created on Feb 10, 2020

Progress calculations should include dependencies


What is the challenge?

  • Current progress calculations do not account for dependencies, making it difficult to evaluate the true completeness of Master Features and Features.

What is the impact?

  • Ensures more accurate progress tracking, especially for complex projects with multiple interdependent tasks, improving planning and decision-making.

Describe your idea

  • Add the ability to include dependencies in progress calculations

  • This would allow completion percentages to factor in the status of dependent features, ensuring that Epics and Features reflect more realistic progress.

  • This enhancement is especially important for teams managing interconnected activities where dependent tasks affect overall completion.


  • Attach files
  • Guest
    Reply
    |
    Jan 25, 2024

    I agree and discovered the same issue within our company. We can have a release (including its own features) within one division, but another division must deliver features for that release too. In other words, the release will not get ready without ALL features being completed. I took the dependency "depends on" and then at least I can see this in a Gantt chart. But when it comes to releases progress "calculate from features", only the features directly under the release are taken into account. The features that come in with dependencies, they are not within this releases progress calculation.

    This means that if you NOT will look into the Gantt chart (incl. other dependencies) or click on these depended features, you can misinterpret the release progress. If you assume that really ALL involved features are taken into the release progress calculation. Because that seems not to be the case.

  • +3
26 MERGED

Portfolio Initiative ‘progress bar’ calculations

Merged
Who would benefit? We have Portfolio Products that ‘Influences federated teams’ (i.e. product workspaces) and need visibility to the planned Strategy progress in workspaces that not owned. What impact would it make? The Portfolio Product does not ...
Mike Jacobson 9 months ago in Reports 0 Future consideration