Project management through the accomplishment value procedure (AVP)
Digital Equipment Corporation
This paper describes a technique called the Accomplishment Value Procedure, AVP, which accurately measures the status of and provides visibility to an information systems development project. It builds upon the foundation of two of R. I. Benjamin’s axioms (1):
Axiom #10—“The great leap forward is best accomplished in short, comfortable hops; if there is a ‘Golden Rule’ in information systems development, this is it.”
Axiom#14—“If you can’t plan it, you can’t do it.”
to which I add my own corollary:
“If you don’t schedule it, it won’t get done.”
A persistent problem of project management has been to relate resources budgeted with work accomplished after the project begins (2). AVP bridges that gap. As a tool of project management, AVP:
- Provides the means to schedule, monitor, and control a project after it has passed the planning phase.
- Enforces a discipline for resource estimating and time scheduling that focuses on the completion of tasks.
- Provides a method to handle changes to schedules and to resources which can be documented and displayed simply and clearly.
- Provides a method for summarizing overall status of projects by management responsibility.
AVP does all this by focusing on the gathering of data that is plotted on a project visibility chart for an individual project and a summary visibility chart for a group of projects.
In doing so, AVP communicates with all levels of an organization in a consistent manner:
- Top management sees a snapshot of the overall status of development projects.
- Middle management sees a snapshot of individual projects.
- Project leaders can monitor performance and compare it to schedules and estimates which point to areas of potential problems that might require management analysis.
- Project team members can see the status of the 13 projects they are working on.
The remainder of this paper deals with (1) a discussion of background: AVP in the perspective of project management, (2) a description of the accomplishment value procedure, (3) a description of an example of the AVP process, (4) a description of how AVP handles changes in schedules and estimates, (5) a description of the AVP summary process and (6) a summary section that includes conclusions and observations regarding the applicability of AVP.
Background — AVP in the Perspective of Project Management
Project management usually means different things to each of us. A major reason is that a project is a unique effort marshalling resources to solve a unique problem. The uniqueness has attracted special management techniques which, according to Murdick and Ross (3) include “outstanding characteristics,” such as:
- Work breakdown structuring which is a method that decomposes the project end result, level-by-level, all the way down to something called the work package, the lowest identifiable element of work to be done.
- Network definition which describes task relationships in a project and which is usually associated with PERT/CPM activities.
- The integration of performance/cost/time for project planning and control.
You can locate AVP in the perspective of project management by relating the outstanding characteristics to the three basic managerial functions required as defined by Paulson (4) as follows:
- Planning — "... the various tasks . . . must be performed to complete the project . . . involves approximate requirements for material, equipment and manpower ...”
- Scheduling — "... the feasible start and completion dates for each activity ...”
- Control — "... monitoring actual performance and comparing it to that which was anticipated from the schedule. The essence of control lies in recognizing differences when they occur, determining reasons for them, and promptly evaluating effects on the schedule.”
In terms of the three “outstanding characteristics,” AVP assumes that (1) formal or informal work breakdown structuring exists with or without a standard work breakdown structure being built, and (2) that the relationships and dependencies among tasks are understood with or without a network being drafted. It is the third characteristic dealing with performance, cost, and time to which AVP applies — with one distinction. The distinction is that AVP takes place after planning is completed.
The matrix in table 1 shows where AVP fits in the relationships between outstanding characteristics and managerial functions of project management. AVP addresses itself to the articulation of accomplishment (performance) and manpower (cost) related to (integrated with) time. By displaying accomplishment and manpower at points in time, AVP provides a visibility that communicates the schedule and supports control.
The quantification of the value of accomplishing each task is crucial to AVP. As each task is completed, the project ect is credited with the value of the task. There is no credit for a partial completion; thus the notion of “percentage complete” is avoided. The expression of percentage complete has traditionally been difficult in its execution, abritrary in its determination and misleading in its interpretation (2). How often has one heard the response that a project is “x percent complete?” In fact, projects have been known to be “90 percent” complete for months.
The Accomplishment Value Procedure
The mechanics of the procedure result in the creation and update of the project visibility chart. The vehicle for this procedure is the estimating and scheduling form. The form integrates the key steps of the procedure and flows through to provide the data for the project visibility chart. The form is a composite of five parts, referred to as parts A through E. Figure 1 shows all parts in the relative positions of the flow of data and information, e.e., from A to B to E and from A to C to D.
Part A is where you would insert descriptive data about each task (milestone) deliverable. The procedure assumes a documentation standard and just about any version would do. Further, the procedure amplifies the doctrine espoused by ADP Analyzer (5), which says “. . . documentation be completed by the end of each phase and each review period. If the documentation has not been completed, then the phase has not been completed — and the next phase cannot begin.” AVP accepts any documentation standard and encourages even finer breakouts or subsets.
Part B is where you would enter the estimates of resources committed to each task/milestone/deliverable by time period (usually a month, but the procedure can handle weekly and daily). We focused on manhours because it is the key resource and it is easier to collect data regarding manpower on a timely basis.
Part C is where you enter the time span for each task/ milestone/deliverable further annotated with the “value” calculated for each.
Part D is a table which is built on the accumulation of data concerning accomplishment units scheduled and actual for each time period and accumulated by the end of each time period.
Part E is a table which is built on the accumulation of data concerning manhours estimated and actual for each time period and accumulated by the end of each time period. For convenience in preparation and for easy reference and analysis, parts D and E are physically part of the project visibility chart.
In Figure 2 is an example of a project visibility chart for a completed project showing in the top portion, the cumulative accomplishment values, scheduled vs. actual and in the bottom portion, the cumulative manhours (resources), estimated vs. actual, for the history of a project. The chart displays the status of the project expressed in accomplishment units as well as the expenditure of manhours, both over the life of the project. Notice that the points plotted on each chart are derived from the data tables, part D and part E, contiguous with each. The data tables are built as a result of the process previously described.
Example of the AVP Process
The Accomplishment Value Procedure (AVP) highlights actual completion of milestones and ignores partial completion. It provides the mechanism for identifying those milestones in the development process that have specific deliverable documents which signal the completion of a milestone.
Once the milestones are identified and resource estimates are associated with each, the sequence of events can be scheduled. Next is the calculation of the “value” of each milestone. For our purposes, value is based on the estab-16 lishment of an arbitrary denomination of units which reflect the relative estimated manhour resource for each milestone/deliverable.
The accomplishment value is the focal point for the project as it moves to completion. The accomplishment value is plotted monthly on the graph along with the resources. In this example, 20 manhours was selected as equal to one accomplishment value. Thus, if the milestone/deliverable is estimated to need 160 manhours of resources, then its accomplishment value is eight.
See figure 3, key I, which is the estimating and scheduling form — part A filled out with the accomplishment values for each milestone/deliverable and represents the beginning of the process.
Having completed part A, you can proceed to part B where the loading of the resources over the course of the project is entered. This loading then becomes the estimated manhours (resources) for the life of the project. See figure 3, key II, which shows the manhour loading or month estimate by month for each task/mileston/deliv-erable and the total estimate for each month.
For each milestone/deliverable that you have associated with a scheduled start and completion date, you can enter the 0——symbol for the start in the week in which the effort for that milestone/deliverable will begin and a □ in the week that it is scheduled to be completed and delivered.
In the square for the ending week, you can enter the accomplishment value. Next, add up the accomplishment values for each month. See figure 3, key III.
The values of each milestone/deliverable are combined to roll up to the total value of the project. In the course of completing the project and as each milestone/deliverable is achieved, the value of each milestone is credited toward project completion, and a measure of project status is established. Credit is given only to those milestone/deliverables that are completed; resources expended on an incomplete deliverable are given no credit. This criteria forces attention to establishing as many milestones as is logical and manageable — a basic rule in successful project management. As a corollary, a specific deliverable could be segmented with each segment becoming a separate milestone/deliverable that would be scheduled, estimated, and accomplishment valued.
Next, you build the data tables in parts D and E that will be the plots for curves on the project visibility chart. See figure 4.
The monthly schedule accomplishment value in part D is simply a posting of the totals from the bottom of part C and from which the cumulative schedule accomplishment value data is calculated.
The monthly est (estimate) manhours data in part E is simply a posting of the totals from the bottom of part B and from which the cumulative est (estimate) is calculated.
The cumulative schedule accomplishment value and the comulative est (estimate) manhours are the plots by month on the project visibility chart in figure 4.
As the project develops, actual data is collected for manhours and accomplishment values. In our example you can see the data recorded through April, the fourth month.
The project visibility chart representing the status of the sample project through April would be as in figure 4. An analysis of the charts and the data in the table above and below the charts (which are parts D and E of the estimating and scheduling form) shows that the project fell behind the scheduled accomplishment during March but that we caught up during April. The recovery, however, seems to be costly since we have exceeded our estimated manhours by nearly 200 manhours. If the trend continues, the project could get into a serious over-budget situation. This situation would require further analysis.
How AVP Handles Changes
The technique lends itself to a procedure for changing schedules and estimates based on changes in project scope or in availability of resources and so forth. If, for example, at the end of April it was determined that the project’s schedule could be shortened by infusion of additional available resources, (while it may violate Brooks Law(6), it is optimistically espoused here for illustration purposes), then the estimating and scheduling form — parts B, C, D, and E — should be modified to reflect this change and to show the impact on the bar chart schedules. The impact of the revision with the new manpower estimate, and the accomplishment value units, for May and June is readily shown in the project visibility chart, figure 5, which shows a new chart with the scheduled and estimated lines shifted upward for both accomplishment values and manhours. This representation is significant since it provides visibility for changes in estimates and schedules.
The AVP Summary Process
AVP further lends itself to summarizing groups of projects by management responsibility such as those of an individual cost center. A collection of project visibility data from several projects can be aggregated to provide visibility. By focusing on an individual fiscal month, you can display scheduled and estimated data for its development projects at the beginning of the month. At the end of the month, you can then aggregate the actual data for accomplishment and manhours.
On the right side of figure 6 is a summary visibility chart completed for a development cost center for the month of October 1978. The bar graphs show the scheduled accomplishment units next to the actual accomplishment units in the top portion with the estimated manhours next to the actual manhours in the bottom portion.
On the left hand side of figure 6 is the AVP log which is the vehicle for the summary process. The log provides space for recording the schedules and estimates for each of a group of projects at the beginning of a time period (usually fiscal month) and for their actual data at the end of the period.
While transferring accomplishment values from the part Ds you have to make certain that the unit of measure (U/M) is consistent. If 20 manhours were used as the U/M for the summary process, then the procedure is to divide the U/M of each project by 20 and then to multiply the resulting fraction by the accomplishment value units associated with the project. For example, if a project had scheduled 72 units with a U/M of 10, then to convert, divide 10 by 20 which results in ; then multiply by 72 which results in the conversion of 36 accomplishment units. It is the latter number that you post to the summary AVP log.
Six projects are posted on the summary AVP log with a total accomplishment value of 120 (based on a unit of measure of 20 manhours per each accomplishment unit) and 2,600 manhours are estimated (and committed) to be used in the process of doing project work. At the end of the month, the actual data are posted totaling 100 accomplishment value units and 3,000 manhours respectively. It is the data from the totals column that is used as a basis for constructing the bar chart.
This paper has introduced the accomplishment value procedure (AVP( by first discussing where it fits in the background perspective of project management. Then, the paper described the steps in the AVP process which lead up to the creation of and provides the basis for updating the project visibility chart. Included in the description was an illustration of how changes in resources or in time would be shown on the project visibility chart. Finally, there was a description of the AVP summary process which provides for tracking and displaying groups of projects of a functional organization by aggregating their visibility data.
AVP is currently in place in the customer service operations development (CSOD) department which is the internal ADP/MIS systems development and computer operations organization at the Field Service Headquarters of Digital Equipment Corporation, Maynard, Mass. CSOD provides system development and computer-based support to headquarters functions in worldwide logistics, financial control, and product engineering and centralized design and development of distributed systems for decentralized implementation at 15 data centers worldwide:
The benefits of its application revolve around the simplicity of how well it can be understood by project team members and how effective it is in communicating status to users and to management.
In addition, individual project team members reach a “comfort” level with the graphical representation of the project status and spend their time with greater attention to the objectives of the project.
There are other benefits. AVP highlights the viability of resource estimates and schedules at the onset of the development cycle and the resource consumption and accomplishment achievement during the development cycle by the smoothness or lack of smoothness of the curve on the project visibility chart.
The discipline of the Accomplishment Value Procedure lends itself to contracting applications development to a vendor. By focusing on specific deliverables you could contract for progress payments synchronized with each deliverable under either a cost reimbursable basis or a fixed-price basis.
At project completion, final payment could be held back until a reasonable warranty period has passed. Moreover, there can be variations that would provide incentives to a contractor. For example, a progress payment or a fixed-price commitment for a deliverable by a certain date would pay X dollars to the vendor but delivery one month earlier would pay 120 percent of X dollars where the incremental 20 percent would serve as an incentive to the contractor.
1. Benjamin, R. I., Conlrol Of The Information Systems Development Cycle, John Wiley & Sons, N.Y., 1971.
2. Block, Ellery B., “Accomplishment/Cost: Better Project Control,” Harvard Business Review, May-June 1971, p. 136.
3. Murdick, Robert G., and Joel E. Ross, Information Systems For Modern Management, Second Edition, Prentice-Hall, Inc., Englewood Cliffs, N.J., 1975, p. 265.
4. Paulson, Boyd C., Jr., Man-Computer Concepts For Project Management, Technical Report No. 148, The Construction Institute, Stanford University, Stanford, CA, 1971, pp. 9-10.
5. EDP Analyzer, “A Structure For EDP Projects,” Vol. 11, No. 5., Canning Publications, Inc., Vista, CA., May 1973, p. 13.
6. Brooks, Frederick P., “The Mythical Man-Month,” Datamation, December 1974.
1. What is the Accomplishment Value Procedure (AVP)? The Accomplishment Value Procedure (AVP) is a method that follows a series of steps in scheduling resources on an information systems development project and tracking actual data as you progress.
2. Who benefits from A VP? What’s in it for me?
In a professional organization involved with EDP and software development, individuals should do their own planning. AVP is a mechanism for scheduling and tracking achievement. So from an individual professional’s point of view, AVP will be a strong contributing factor to the time management. AVP will further provide a structure and an easily understood means of communicating where you are in terms of your project status and of your resource (your time).
3. How does it work?
Printed forms and formal procedures are available. You can use the forms to indicate the steps required to complete your project work. The key activities of a project life cycle are a good guide to follow in identifying your steps. Each step requires a milestone, an event, or a deliverable document associated with it. The printed forms allow you to chart the time span of each step and to estimate the resources (manpower) that will be required for each step. Next, you can calculate the “value” of each step. The value is derived from manpower estimates and can be plotted on a graph which now describes the scheduled accomplishment over time. When the step is achieved, you will have earned the value. The latter can be plotted as the “actual” and can be compared to the schedule.
4. Does AVP replace planning?
No. First of all, AVP is a tracking procedure that has a formatted scheduling process. It should be used after planning is accomplished. Second, AVP is complementary to any planning and control system or procedure you have in place.
5. Does A VP cover the tracking of all resources applied to project work?
It can, but in most implementations, it focuses on manpower.
6. How does it work?
AVP provides a “visibility” to project status by graphically showing progress against schedules as well as resource estimates and actual charges. The scheduling and accomplishment graph highlights whether there is visible progress or not; together with data provided by AVP, it points to reasons for deviation.
7. Doesn’t this mean extra work?
AVP does force a discipline in scheduling that suggests frequent milestones against which you will perform your project work. Frequent milestones provide a foundation and environment for effective project management.
8. Is A VP time consuming?
No, not in the long run. However, like any procedure that you are not accustomed to, you will spend some time in the beginning until you learn how to use it expeditiously.
9. What about maintenance tasks like fixing bugs — work that is not normally scheduled?
When manpower is committed to maintenance projects on a regular basis, it represents a scheduling of the resource. Therefore you can use AVP on maintenance tasks, understanding that progress accomplished is always equal to the scheduled resource that has been committed.
10. What advantage does A VP provide management?
At the project management level it is a discipline for estimating and scheduling resources (mainly manpower) for project work. At the cost center level, it provides a means for understanding individual project status and overall cost center development status. Finally, through the summary rollup process, it provides a measure for overall status of development work within CSOD.
11. Does A VP only apply to information systems development projects?
No. It can be used on any project where there is more than one person working on more than one step (or sub task).
Reprinted from the National Computer Conference, 1979.
“Reprinted with permission from the 1979 National Computer Conference Proceedings AFIPS Volume 48-AFIPS press publishers.”