13.9 We saw in the EV example shown in Table 13.4 that there is more actual effort spent than what the BCWP indicates on 4/5/2021 because that calculation only includes the completed tasks. Suppose we invent another term called all actual efforts spent (AAES) to include all the efforts spent as of the status date and then use it to compute a new formula: EV9 = AAES / BAC.

1. Discuss your opinion of using EV9 instead of EV.

2. Because AAES is just a redefined and expanded BCWP, do you believe the SV and CV figures will be more representative of the true project status if we use AAES in computing SV and CV? Why?

- Actual cost of work performed (ACWP): The sum of the actual efforts of all the tasks that have been completed at a specific status-checking date. A factor that should be remembered is that BCWS, BCWP, nd ACWP are all stated in terms of a specific statusionitoring date. Thus those values will change relative to ie status date. TABLE 13.4 shows an example of estimated efforts and ctual efforts expended as of a specific date, which is April 2021. The date format used here is month/day/year. The fforts are measured in person-days (Pers-days). Each task as a budgeted cost of work, and the BCWs for the six tasks re shown in the column showing estimated effort. For xample, for Task 4 the BCW is 25 Pers-days. The sum of is column, or the sum of the BCWs, is the budget at ompletion: BAC=10+15+30+25+15+20=115Pers-daysTasks1and2.TheBCWforTasks1and2respectivelyare10and15Pers-days:BCWS=10+15=25Pers-dayscompletiondate,theBCWSasofApril5,2021includes Now let us look at the three values that are computed relative to the status taking date, which in this case is April 5, 2021. By examining the column showing the estimated Tasks 1 and 2. The BCW for Tasks 1 and 2 respectively are We next look at how much of the estimated work is completed on April 5, 2021. This can be found by examining the actual completion date column. We see that tasks 1, 2, and 4 have been completed. These three completed tasks had been estimated to take 10,15 , and 25 Pers-days: BCWP=10+15+25=50Pers-days The actual effort expended for those tasks that were completed on April 5, 2021 is found by looking at the actual completion date and taking the effort values for those completed tasks from the column entitled "Actual Effort Spent So Far in Pers-days." The actual effort for completed Tasks 1,2 , and 4 are 10,25 , and 20 Pers-days respectively: ACWP =10+25+20=55 Pers-days. In our example, on April 5, 2021, BCWP is 50 Pers-days, and ACWP is 55 Pers-days. Thus CV =5055, or 5 Pers- The next step is to define EV in terms of the earlier days. In this case, on April 5, 2021, we have 5 Pers-days of definitions. EV is an indicator that will tell us how much of effort cost overrun. the estimated work is completed on a specific date. It The EV management system provides us with a concrete compares the sum of all the estimated efforts of the way to monitor project status from a cost/effort perspective. completed tasks as of the status date against the sum of However, the schedule variance is not an indicator of the estimated efforts of all the tasks: calendar time schedule but an effort schedule. Clearly more EV=BCWP/BAC indicators may be constructed from this basic set of definitions, but we will not include them here. We have In terms of our example, EV=50/115=0.43. We may found that the set EV, SV, and CV provides a good indicator interpret this to mean that the project is 43 percent of project status, but we must still remember to look beyond complete as of April 5, 2021. the numbers, ask questions, and delve into other There are two more status indicators that can be derived parameters when monitoring a software project. As a final from the definitions. These are variance indicators that, reminder, if the monitored information indicates potential once again, compare the planned or estimated value project problems, then adjustments must be made. Do not against the actual value. The first one is a schedule variance wait for some project-saving event to occur on its own. (SV) indicator, which is defined as the difference between Project managers rarely have such luck. estimated efforts of the tasks that have been completed by the status date and the estimated efforts of the tasks that 13.2.4 Measuring Project Properties and Goalwere scheduled or planned to have been completed by the Question-Metric (GQM) status date: SV=BCWPBCWS We have discussed the need to set goals for a software project during the planning stage so that these goals can be In our example, on April 5, 2021, BCWP is 50 Pers-days, tracked and checked to see if they have been met. The and BCWS is 25 Pers-days. Thus SV =5025, or 25 Persgoals are stated in terms of such properties as schedule, days. We may interpret the project status as 25 Pers-days cost, productivity, maintainability, defect quality, and so on. ahead of schedule from an effort perspective. Clearly, the specific characteristics of interest must be well The second variance indicator is the cost variance (CV), defined before any measurement can take place. Besides which is defined as the difference between the estimated setting and tracking goals, the reasons for measurement efforts of the tasks that have been completed at the status include the following: date and the actual efforts expended for the tasks that have - Characterization: Allows us to gather information about been completed at that status date. and intelligently describe a property. CV=BCWPACWP - Tracking: Allows us to gather information about a property through such parameters as time or process - Actual cost of work performed (ACWP): The sum of the actual efforts of all the tasks that have been completed at a specific status-checking date. A factor that should be remembered is that BCWS, BCWP, nd ACWP are all stated in terms of a specific statusionitoring date. Thus those values will change relative to ie status date. TABLE 13.4 shows an example of estimated efforts and ctual efforts expended as of a specific date, which is April 2021. The date format used here is month/day/year. The fforts are measured in person-days (Pers-days). Each task as a budgeted cost of work, and the BCWs for the six tasks re shown in the column showing estimated effort. For xample, for Task 4 the BCW is 25 Pers-days. The sum of is column, or the sum of the BCWs, is the budget at ompletion: BAC=10+15+30+25+15+20=115Pers-daysTasks1and2.TheBCWforTasks1and2respectivelyare10and15Pers-days:BCWS=10+15=25Pers-dayscompletiondate,theBCWSasofApril5,2021includes Now let us look at the three values that are computed relative to the status taking date, which in this case is April 5, 2021. By examining the column showing the estimated Tasks 1 and 2. The BCW for Tasks 1 and 2 respectively are We next look at how much of the estimated work is completed on April 5, 2021. This can be found by examining the actual completion date column. We see that tasks 1, 2, and 4 have been completed. These three completed tasks had been estimated to take 10,15 , and 25 Pers-days: BCWP=10+15+25=50Pers-days The actual effort expended for those tasks that were completed on April 5, 2021 is found by looking at the actual completion date and taking the effort values for those completed tasks from the column entitled "Actual Effort Spent So Far in Pers-days." The actual effort for completed Tasks 1,2 , and 4 are 10,25 , and 20 Pers-days respectively: ACWP =10+25+20=55 Pers-days. In our example, on April 5, 2021, BCWP is 50 Pers-days, and ACWP is 55 Pers-days. Thus CV =5055, or 5 Pers- The next step is to define EV in terms of the earlier days. In this case, on April 5, 2021, we have 5 Pers-days of definitions. EV is an indicator that will tell us how much of effort cost overrun. the estimated work is completed on a specific date. It The EV management system provides us with a concrete compares the sum of all the estimated efforts of the way to monitor project status from a cost/effort perspective. completed tasks as of the status date against the sum of However, the schedule variance is not an indicator of the estimated efforts of all the tasks: calendar time schedule but an effort schedule. Clearly more EV=BCWP/BAC indicators may be constructed from this basic set of definitions, but we will not include them here. We have In terms of our example, EV=50/115=0.43. We may found that the set EV, SV, and CV provides a good indicator interpret this to mean that the project is 43 percent of project status, but we must still remember to look beyond complete as of April 5, 2021. the numbers, ask questions, and delve into other There are two more status indicators that can be derived parameters when monitoring a software project. As a final from the definitions. These are variance indicators that, reminder, if the monitored information indicates potential once again, compare the planned or estimated value project problems, then adjustments must be made. Do not against the actual value. The first one is a schedule variance wait for some project-saving event to occur on its own. (SV) indicator, which is defined as the difference between Project managers rarely have such luck. estimated efforts of the tasks that have been completed by the status date and the estimated efforts of the tasks that 13.2.4 Measuring Project Properties and Goalwere scheduled or planned to have been completed by the Question-Metric (GQM) status date: SV=BCWPBCWS We have discussed the need to set goals for a software project during the planning stage so that these goals can be In our example, on April 5, 2021, BCWP is 50 Pers-days, tracked and checked to see if they have been met. The and BCWS is 25 Pers-days. Thus SV =5025, or 25 Persgoals are stated in terms of such properties as schedule, days. We may interpret the project status as 25 Pers-days cost, productivity, maintainability, defect quality, and so on. ahead of schedule from an effort perspective. Clearly, the specific characteristics of interest must be well The second variance indicator is the cost variance (CV), defined before any measurement can take place. Besides which is defined as the difference between the estimated setting and tracking goals, the reasons for measurement efforts of the tasks that have been completed at the status include the following: date and the actual efforts expended for the tasks that have - Characterization: Allows us to gather information about been completed at that status date. and intelligently describe a property. CV=BCWPACWP - Tracking: Allows us to gather information about a property through such parameters as time or process