Weekly “Macro” Status

1. Weekly “Macro” Status • Show the Plan and compare with Actual • of Scheduled Activities • of Functional content • of Quality/Test status when “appropriate” • of Team effort expended • of Risk items • Also, may use Earned Value indices (see lecture notes)

2. Status of Scheduled Activities • Show the original planned schedule • Show any change to the original schedule • Explain the reason • Show the actual in relationship extended because --- Today 10/27 10/20 10/23 11/08 11/10 11/15 Test Design 6 person hours 1 person hours (actual) 25 person hours Coding 6 person hours (actual) Note the slight “slip”

3. Status of Functional Content • Requirement 1 11/10 design complete • Requirement 2 10/31 code start • Requirement 3 10/28 code complete • Requirement 4 10/28 testing • Requirement 5 11/5 test case designed • Requirement 6 10/26 test complete ContentsTarget CompletionCurrent Status

4. Status of Test and Quality • Quality Goal is to execute all the black box test cases and fix all the problems found. The test cases cover: • All functions in the requirements • Every input field • Only legitimate data • Planned Test Cases : 75 • Current Status: • Accumulative Test cases designed - 65 (10 remaining) • Accumulative Test cases executed - 30 (45 remaining) • Accumulative Problems found - 121 • Accumulative Problems fixed - 79 • Accumulative Problem backlog - 42

5. Accumulative “ Test Problem” Status by Severity

6. Status of Team effort Expended Activity Planned Actual Requirements 25 ph 42 ph Proj. Mgmt 40 ph 35 ph 15 ph Design/code 45 ph . . . . 220 ph 92 ph Total

7. Risk Item Status Planned Resolution date Risk Items Actual Status • Tool implemented 1/15/2012 • Tool education complete 1/25/2012 • Good usage feedback 2/1/2012 • - Risk item removed 2/15/2012 Risk Item #5: Tool - y February 31,2012