Skip to main content
6 events
when toggle format what by license comment
Dec 19, 2017 at 22:44 comment added Tom Boyle The add-in that I use all the time for such purposes is called BPC Logic Filter. We developed it for internal use in our company, but we routinely share it with others that have a similar need.
Dec 19, 2017 at 19:12 comment added Sean McDonnell Agreed on looking forward. The only problem is when presenting the latest schedule to a manager two levels above who now only has visibility to the current issue causing delays to the project. This causes the manager to be unaware of the other delays from other tasks/resources prior to that point. Near the end of the project this is especially important as the currently slipping/delayed task might be wrongfully perceived by said manager as the main cause of the accumulated delays throughout the project. Of course at one point during previous status updates those other issues were presented
Dec 12, 2017 at 23:47 comment added Tom Boyle As noted, I typically trace driving logic from beginning to end of project using an add-in. If the actual dates are accurate there will often be gaps in this path that may need to be explored.
Dec 12, 2017 at 23:43 comment added Tom Boyle Fundamentally, project managers need to look forward, not back. An as-built critical path is most useful to forensic consultants resolving disputes long after completion. They essentially apply #2 retrospectively - its a tedious process, largely because the "actual" dates stored in the project are not supported by contemporaneous data (i.e. they're usually wrong.)
Dec 12, 2017 at 20:13 comment added Sean McDonnell Thank you for understanding the question and for the clear response. I think your #2 could work, it still seems surprising to me that this is not built in to MSP in some form for reporting what was the critical path at the end of the project.
Dec 11, 2017 at 18:14 history answered Tom Boyle CC BY-SA 3.0