Total project control

Total project control (TPC) is a project management method that emphasizes continuous tracking and optimization of return on investment (ROI). It was developed by Stephen Devaux. It builds upon earlier techniques such as earned value management, critical path method, and program evaluation and review technique, but uses these to track and index projected project profitability as well as the more traditional cost and schedule.[1] In this way it aims to manage projects as profit and investment centers, rather than cost centers.

Introduced with TPC are a variety of project management metrics and techniques, among them critical path drag,[2][3] the value breakdown structure (VBS), Devaux's Index of Project Performance (the DIPP),[4] Doubled Resource Estimated Duration (DRED), and Cost of Leveling with Unresolved Bottlenecks (CLUB).

The Project Management Institute's monthly magazine PM Network reviewed the TPC methodology as making "solid points about what can be done to maximize ROI during project execution."[5] In a 2015 PMI white paper on organizational project management, Joseph Sopko wrote about the DIPP: "The effect of project delivery of any new capability on program NPV should always be quantified and communicated to the project team by the project sponsor... DIPP is the ratio of EMV divided by ETC. As either the EMV is improved or the ETC is reduced, the effect on project value contribution is quantified."[6] He also wrote: "Tools and practices for managing projects and programs as investments have been defined... For example, critical path drag is a concept for evaluating how much any activity along the critical path can be shortened to optimize the project duration."[7]

Later enhancements

Since the total project control approach was introduced in the first edition of Devaux's 1999 book by that title, others have extended both the theory and the practice. In 2013, Tomoichi Sato of JGC Corporation in Yokohama suggested an "extended DIPP" based on risk-based project value. He wrote: "The key concept of Simple DIPP is to obtain the ratio of expected income to cost ETC, neglecting sunk costs in the past. Using RPV instead of expected income, the author proposes a criterion "extended DIPP". This represents the ratio of remaining RPV to cost ETC. If there are project alternatives which are mutually independent, the one with the highest extended DIPP should be chosen... To maximize the project portfolio value of a company, extended DIPP can be used as criteria for prioritisation."[8]

Additionally, critical path drag calculation has been coded into project scheduling software, both in Spider Project and as an add-on product to Microsoft Project from Boyle Project Consulting, PLLC.[9]

Sources
    • Devaux, Stephen A. (1999). Total Project Control: A Manager's Guide to Integrated Project Planning, Measuring, and Tracking (pp. xxiv–xxvi) New York, NY: Wiley. ISBN 0-471-32859-6.
  2. William Duncan and Stephen Devaux "Scheduling Is a Drag" Projects@Work on-line magazine
  3. Stephen A. Devaux "The Drag Efficient: The Missing Quantification of Time on the Critical Path" Archived 2013-03-13 at the Wayback Machine Defense AT&L magazine of the Defense Acquisition University.
  4. Stephen A. Devaux ["When the DIPP Dips: A P&L Index for Project Decisions"] Project Management Journal, Vol XXIII, No. 3, Sep 1992, pp. 45 - 49.
  5. Gary Heerkens "Eye on the Prize: The Business of Managing Projects" PM Network, June 2015, p. 72.
  6. Joseph Sopko "Organizational Project Management: Why Build and Improve?" PMI white paper, 2015, p. 20.
  7. Sopko "Organizational Project Management: Why Build and Improve?" PMI white paper, 2015, p. 19.
  8. Dr. Tomoichi Sato "Risk-based Project Value Analysis – Contributed Value and Procurement Cost"
  9. Thomas Boyle "Drag Calculation in BPC Logic Filter for Microsoft Project"

Further reading
gollark: It does, you realise, support multiple lines.
gollark: <@263493613860814848> Well, it's very simple. Apparently YOU experienced a weird quirk where it suddenly decided to allow you to use it, *possibly* because of some inconsistent weirdness in the way discord.py works. Then I took it down and really quickly wrote a hotfix to do it in a more recommended way which should work.
gollark: <@160279332454006795> Please try it.
gollark: ++magic py return 4
gollark: Hmm. So now nobody can use it. Great.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.