Giving critical path the attention it deserves

The article describes the creation of a project tracking system that was used by the team implementing SAP for GTE (now Verizon).The previous system was capable of tracking 12-15 projects through 12 development lifecycle steps, each project containing as many as 600 items and over 7,000 milestones.Due to shortcomings in this system, it was decided to move from milestone tracking to buffer tracking.Among the pitfalls attributed to milestone tracking are its inability to monitor progress between milestones, the difficulty of estimating ripple-effects caused by delays, and the tendency of managers to focus on hitting dates rather than completing overall tasks.Switching to critical path tracking, and using estimate to complete (ETC) dates, provided a better representation of the work remaining to be done, among other benefits.
registered user content locked

Log in or join PMI to gain access

or Account Registration

Advertisement

Advertisement

Related Content

Advertisement

Publishing or acceptance of an advertisement is neither a guarantee nor endorsement of the advertiser's product or service. View advertising policy.