RELATED IDEAS
Progress Should Include Dependencies
I would like the ability to calculate completion percentage automatically based on Dependencies. This is especially critical for evaluating the completeness of Master Features and Features. Today, the completion options do not factor dependencies into their completeness equation. I would like to see this added
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +3
26
MERGED
Portfolio Initiative ‘progress bar’ calculations
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 ...
0
Future consideration
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.