THE BATHTUB PERIOD

The award of the Scott contract on January 3, 1987, left Park Industries elated. The Scott Project, if managed correctly, offered tremendous opportunities for follow-on work over the next several years. Park's management considered the Scott Project as strategic in nature.

The Scott Project was a ten-month endeavor to develop a new product for Scott Corporation. Scott informed Park Industries that sole-source production contracts would follow, for at least five years, assuming that the initial R&D effort proved satisfactory. All followon contracts were to be negotiated on a year-to-year basis.
Jerry Dunlap was selected as project manager. Although he was young and eager, he understood the importance of the effort for future growth of the company. Dunlap was given some of the best employees to fill out his project office as part of Park's matrix organization. The Scott Project maintained a project office of seven full-time people, including Dunlap, throughout the duration of the project. In addition, eight people from the functional department were selected for representation as functional project team members, four full-time and four half-time.
Although the workload fluctuated, the manpower level for the project office and team members was constant for the duration of the project at 2,080 hours per month. The company assumed that each hour worked incurred a cost of $60.00 per person, fully burdened.

At the end of June, with four months remaining on the project, Scott Corporation informed Park Industries that, owing to a projected cash flow problem, follow-on work would not be awarded until the first week in March (1988). This posed a tremendous problem for Jerry Dunlap because he did not wish to break up the project office. If he permitted his key people to be assigned to other projects, there would be no guarantee that he could get them back at the beginning of the follow-on work. Good project office personnel are always in demand.

Jerry estimated that he needed $40,000 per month during the "bathtub" period to support and maintain his key people. Fortunately, the bathtub period fell over Christmas and New Year's, a time when the plant would be shut down for seventeen days. Between the vacation days that his key employees would be taking, and the small special projects that his people could be temporarily assigned to on other programs, Jerry revised his estimate to $125,000 for the entire bathtub period.
At the weekly team meeting, Jerry told the program team members that they would have to "tighten their belts" in order to establish a management reserve of $125,000. The project team understood the necessity for this action and began rescheduling and replanning until a management reserve of this size could be realized. Because the contract was firm-fixed-price, all schedules for administrative support (i.e., project office and project team members) were extended through February 28 on the supposition that this additional time was needed for final cost data accountability and program report documentation
Jerry informed his boss, Frank Howard, the division head for project management, as to the problems with the bathtub period. Frank was the intermediary between Jerry and the general manager. Frank agreed with Jerry's approach to the problem and requested to be kept informed

On September 15, Frank told Jerry that he wanted to "book" the management reserve of $125,000 as excess profit since it would influence his (Frank's) Christmas bonus. Frank and Jerry argued for a while, with Frank constantly saying, "Don't worry! You'll get your key people back. I'll see to that. But I want those uncommitted funds recorded as profit and the program closed out by November 1."

Jerry was furious with Frank's lack of interest in maintaining the current organizational membership

a. Should Jerry go to the general manager?

b. Should the key people be supported on overhead?

c. If this were a cost-plus program, would you consider approaching the customer with your problem in hopes of relief?

d. If you were the customer of this cost-plus program, what would your response be for additional funds for the bathtub period, assuming cost overrun?

e. Would your previous answer change if the program had the money available as a result of an underrun?

f. How do you prevent this situation from recurring on all yearly follow-on contracts?

FRANKLIN ELECTRONICS

In October 2003 Franklin Electronics won an 18-month labor-intensive product development contract awarded by Spokane Industries. The award was a cost reimbursable contract with a cost target of $2.66 million and a fixed fee of 6.75 percent of the target. This contract would be Franklin's first attempt at using formal project management, including a newly developed project management methodology.

Franklin had won several previous contracts from Spokane Industries, but they were all fixed-price contracts with no requirement to use formal project management with earned value reporting. The terms and conditions of this contract included the following key points:

? Project management (formalized) was to be used.

? Earned value cost schedule reporting was a requirement.

? The first earned value report was due at the end of the second month's effort and monthly thereafter.

? There would be two technical interchange meetings, one at the end of the sixth month and another at the end of the twelfth month

Earned value reporting was new to Franklin Electronics. In order to respond to the original request for proposal (RFP), a consultant was hired to conduct a four-hour seminar on earned value management. In attendance were the project manager who was assigned to the Spokane RFP and would manage the contract after contract award, the entire cost accounting department, and two line managers. The cost accounting group was not happy about having to learn earned value management techniques, but they reluctantly agreed in order to bid on the Spokane RFP. On previous projects with Spokane Industries, monthly interchange meetings were held. On this contract, it seemed that Spokane Industries believed that fewer interchange meeting would be necessary because the information necessary could just as easily be obtained through the earned value status reports. Spokane appeared to have tremendous faith in the ability of the earned value measurement system to provide meaningful information. In the past, Spokane had never mentioned that it was considering the possible implementation of an earned value measurement system as a requirement on all future contracts
Franklin Electronics won the contact by being the lowest bidder. During the planning phase, a work breakdown structure was developed containing 45 work packages of which only 4 work packages would be occurring during the first four months of the project

Franklin Electronics designed a very simple status report for the project. The table below contains the financial data provided to Spokane at the end of the third month.

A week after sending the status report to Spokane Industries, Franklin's project manager was asked to attend an emergency meeting requested by Spokane's vice president for engineering, who was functioning as the project sponsor. The vice president was threatening to cancel the project because of poor performance. At the meeting, the vice president commented, "Over the past month the cost variance overrun has increased by 78 percent from $14,000 to $25,000, and the schedule variance slippage has increased by 45 percent from $31,000 to $45,000. At these rates, we are easily looking at a 500 percent cost overrun and a schedule slippage of at least one year. We cannot afford to let this project continue at this lackluster performance rate. If we cannot develop a plan to control time and cost any better than we have in the past three months, then I will just cancel the contract now, and we will find another contractor who can perform."