{"title":"International Guidance and Controls","authors":"P. E. Pfeifer","doi":"10.2139/ssrn.2975064","DOIUrl":null,"url":null,"abstract":"Thomas Stearns must decide whether to continue with planned software development and risk missing the completion deadline on a $20 million project or bite the bullet and make some costly hardware changes that will virtually eliminate the risk of missing the deadline. This introductory decision analysis case: (1) contains a compound (square-circle-square) decision, (2) encourages a discussion of the meaning of probability, and (3) requires the use of sensitivity analysis to handle the unspecified costs of missing the deadline. \nExcerpt \nUVA-QA-0350 \nINTERNATIONAL GUIDANCE AND CONTROLS \nTime was running out on the $ 20 million CARV (confined aquatic recovery vehicle) project, and Project Manager Thomas Stearns was concerned about maintaining the project's schedule. With 10 months left, considerable portions of the software remained to be developed, and Stearns was by no means certain that all the necessary development work would be completed on time. \nSoftware Development \nStearns had had his project team working full force in recent months on the software development for CARV's command and guidance system. His headcount (the number of full-time-equivalent workers assigned to the project) had been increased recently, so total development costs were running at $ 300,000 per month, which was 25% over the project's budget. Stearns believed that there was but an 80% chance that the necessary software would be completed in the remaining 10 months. Despite the risk of not maintaining the schedule, he could not increase the headcount on the project or increase the rate of software development in any way. \nIf the software were not completed on time, Stearns was fairly certain that one or two extra months of work would suffice to complete the project. Unfortunately, each month's delay in project completion meant a 2.5% ($ 500,000) reduction in the price of the contract. In addition to this precisely defined cost of not meeting the schedule, a hard‑to‑quantify, but no less significant cost of lost reputation was associated with not completing the project as scheduled. \n. . .","PeriodicalId":390041,"journal":{"name":"Darden Case Collection","volume":"16 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2017-06-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Darden Case Collection","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.2139/ssrn.2975064","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 0
Abstract
Thomas Stearns must decide whether to continue with planned software development and risk missing the completion deadline on a $20 million project or bite the bullet and make some costly hardware changes that will virtually eliminate the risk of missing the deadline. This introductory decision analysis case: (1) contains a compound (square-circle-square) decision, (2) encourages a discussion of the meaning of probability, and (3) requires the use of sensitivity analysis to handle the unspecified costs of missing the deadline.
Excerpt
UVA-QA-0350
INTERNATIONAL GUIDANCE AND CONTROLS
Time was running out on the $ 20 million CARV (confined aquatic recovery vehicle) project, and Project Manager Thomas Stearns was concerned about maintaining the project's schedule. With 10 months left, considerable portions of the software remained to be developed, and Stearns was by no means certain that all the necessary development work would be completed on time.
Software Development
Stearns had had his project team working full force in recent months on the software development for CARV's command and guidance system. His headcount (the number of full-time-equivalent workers assigned to the project) had been increased recently, so total development costs were running at $ 300,000 per month, which was 25% over the project's budget. Stearns believed that there was but an 80% chance that the necessary software would be completed in the remaining 10 months. Despite the risk of not maintaining the schedule, he could not increase the headcount on the project or increase the rate of software development in any way.
If the software were not completed on time, Stearns was fairly certain that one or two extra months of work would suffice to complete the project. Unfortunately, each month's delay in project completion meant a 2.5% ($ 500,000) reduction in the price of the contract. In addition to this precisely defined cost of not meeting the schedule, a hard‑to‑quantify, but no less significant cost of lost reputation was associated with not completing the project as scheduled.
. . .