The Weighted Worth field contains manually determined and entered values. In the example here, the Number fields are Number1, Number2, and Number 3, labeled “Weighted Worth,” “Physically Finished Weight,” and “Physically Finished %,” respectively.įigure 3 – A Column Definition dialog box showing a tailored header for the Number2 field. One technique requires three Number fields: one to reflect the total “weight” or “worth” of each individual task, one to measure the value of work in progress, and the third to convert that value into summary percentages. In order to track and report, Physical % Complete needs to be used with some customized fields. Physical % Complete allows people to track progress in a simple way, but it doesn’t support reporting at a summary level. People managing projects appreciate the simplicity of using % complete to both track and report progress, so they gravitate to the field they think supports this. Physical % Complete has no underlying formula, so manually entering a value in Physical % Complete has no further impact by default.Percent Work Complete calculates after Actual Work and/or Remaining Work has been entered.% Complete calculates after Actual Duration and/or Remaining Duration has been entered.Manually entering % Complete interferes with formulaic calculations: When project managers try to report on the situation as shown in Figure 2, some have trouble reconciling the differences between % Complete and % Work Complete, and they’ll often claim that Project isn’t calculating properly. Notice also that both % Complete and % Work complete aggregate cumulatively at the summary row level, whereas Physical % Complete doesn’t.įigure 2: % Complete aggregates while Physical % Complete doesn’t. Note that while the individual rows seem to be equal, the summary row isn’t, especially at the Project Summary level. When % Complete gets entered, the same number carries over to the % Work Complete field by default, also shown in Figure 2. Figure 2 shows where several tasks have been updated by entering the same values for % Complete and Physical % Complete for each task. Unfortunately, this field causes problems when project status needs to be summarized.įigure 1: A template example showing a Physical % Complete field inserted in the Entry table.įew Project users understand that updating progress with the % Complete field simply records what portion of the timeline has been completed.

Any values in the Physical % Complete field must be manually entered, and so it’s designed for human operators to insert their own subjective opinion of the relative degree of completion.

The Physical % Complete field is included by default in the Tracking Table (View | Table | Tracking) or it can be inserted into any Task-oriented view (Insert | Column | “Physical % Complete” in the Field name: field). The % complete or % work complete fields in Project work best when actual hours of labor or actual hours of time passed get entered (but that’s the topic of a different article.) If you wish to use the subjective assessments, the better alternative may be the Physical % Complete field. Microsoft Project doesn’t work well with this since manually entering values into the % complete field logically cascades a cavalcade of calculations, which aren’t necessarily intuitive. Project Portfolio Management (PPM) Trainingįar too often people arbitrarily track project performance through the “Percent (%) Complete” method with subjective estimates for “how finished” the project is.Project Management Office (PMO) Training.Enterprise Project Management (EPM) Training.Project Management Certification Training.

Projectlibre percentage complete