My question is really about right metrics to report when looking at a set of projects and functionality of project management tools which help in highlighting these metrics.
We are trying to do retrospectives and look at our projects to see why they got delayed. In our system, anytime someone pushes back a release date, we force them to document a reason so we have documented every delay and every reason.
Here is the issue:
If I have 10 projects that are all dependent on one another and project #1 gets delayed by 1 week, all 9 other projects would then have dates slipped by a week.
When I review all the delays, I don't think it is correct to show 10 weeks of delay (if I add up delays in all projects) because I'd be adding the same week many times as all projects were delayed for the same reason, e.g. pushed back just because of the 1 week delay in project #1.
What is the best way to highlight and accurately report project delays (considering we understand what went wrong) without having this multiplied counting issue where you are penalized for just having many projects queued in the pipeline.
We can change our system so I am curious how other tools deal with this type of metrics.