Project Visibility Calculations


Show all your calculations on this page. 
Perform the calculations described below and put the current week's data on the home page. Keep this page on the team wiki and the version history will be maintained automatically.
Then beneath your calculations, summarize the data by week in a table or chart.
 

Days ahead of Schedule

Simply refer to the tasks planned in the detailed schedule and report days ahead of schedule.  If you are behind schedule, report it as negative days.
 

Repository Source LOC

Refer to the Integration Plan.  Compute the percent of the planned versus actual LOC for all source modules (not tests).
 
LOC Stage 1
(CPE 308)		 Week 1 Week 2 Week 3               Total
Actual 2000 321 450 250                
Actual
To Date		 2000 2321 2771 3021                
Planned   569 473 458                
Planned To Date 2000 2569 3042 3500 ...             7000

For week 3 you would report 3021 / 7000 vs  3500 / 7000, i.e., 43% / 50%
 

Percent of Defects Found

Consider only code written this quarter.  Follow these sample calculations:

Actual Defects found to date:                   120
LOC Actual To Date:                            3021
Total LOC planned for project:              7000

Planned defects found to date:
LOC Actual To Date  *  50 defect / 1000 lines  =  3021 * 50 / 1000  =  151

Planned total defects found:
Total LOC planned for project  *  50 defect / 1000 lines = 7000 * 50 / 1000    =  350

Actual defects found %:
(Actual defects found / planned total)                = 120 / 350                    34%

Planned Defects Found to date %:
(Planned defects found to date / planned total ) = 151 / 350                   43%

This is reported on home page: 34% / 43%
 
 
Defects
Found		 Week 1 Week 2 Week 3 ...         Week 9 Week 10 Total
Actual 10 8 12 ...         23    
To Date Actual 10 18 30 ...         200    
To Date Planned 25 50 75 ...         225 250 250

Percent of Defects Fixed

A table of number of defects fixed per week.
Defects Fixed Week 3 Week 4 Week 5 ...         Total
  5 8 13            
                   

A chart showing found versus fixed per week will be needed for Release Criteria.
This data does not need to be summarized on Home Page.
 

Percent of System Tests Passed

A table of showing the number of System Tests written and the number that are running without failing.
The QA Manager is responsible for running the System Tests every week and compiling this data.
System
Tests		 Week 3 Week 4 Week 5 ...         Total
 Written 21
 23 24            
 Passed  3 12  19             

This data does not need to be summarized on Home Page.

Percent of Resources Used

Team X planned resource utilization is 15 hrs / person / week or 90 hours.  Project total = 90 hrs * 10 weeks = 900 hrs.
  Week 1 Week 2 Week 3 ...           Week 10 Total
Joe 8.25 13.0 12.0                
Sue 12.5 11.5 10.25                
Bill 9.75 10.0 11.5                
Sam 11.5 12.25 12.0                
Ted 10.25 9.25 10.0                
Total 52.25 56.0 55.75                
% of planned 58% 62% 61%                

To Date Resources Used

  Week 1 Week 2 Week 3 ...              Total
To Date
Actual		 52.25 108.25 164                
To Date
Planned		 90 180 270 360 450
540
630
720
810
900
 900
To Date
%Planned
 10
 20
 30
 40
 50
 60
 70
 80
 90
 100
 100

 For week 3 you would report 164 / 900 vs 270 / 900, i.e., 18% / 30%


Batting Average

This is a measure of how successful your team is at completing action items on time.
Action  Items
 Week 1 Week 2 Week 3 ...              
Completed
on time
 40 45 51                
To Date
 40
 85
 136







Due
 45 47
 53
                
To Date
 45
 92
 145







%ontime
 88
 92
 93







 For week 3 you would compute  136 / 145 and report 0.93