Team Number: Week: Program Size (SLOC) Base Added Deleted Modified Reused # of COTS Total New SLOC Effort (Hours) Project Mgmt. Requirements COTS Assessment Design Life Cycle Planning Configuration Mgmt. Feasibility Analysis Code COTS Tailoring COTS Glue Code development Test Deployment Planned Actual 1 1 Actual 10 5 9.3 6 2 1 Date Wk. 1 2 3 4 5 6 7 8 9 10 11 12 13 Planned 11 Cumulative No. Of tasks Actual Completed On Sched 11 11 Late 0 Date Wk. 1 2 3 4 5 6 7 8 9 10 11 12 13 Man-hours Planned Actual This Wk. Cumulative This Wk. Cumulative 17 17.5 17.5 17.5 09/19/2007 09/26/2007 10/03/2007 10/10/2007 10/17/2007 10/24/2007 10/31/2007 11/07/2007 11/14/2007 11/21/2007 11/28/2007 12/05/2007 12/12/2007 09/19/2007 09/26/2007 10/03/2007 10/10/2007 10/17/2007 10/24/2007 10/31/2007 11/07/2007 11/14/2007 11/21/2007 11/28/2007 12/05/2007 12/12/2007 Based on submitted effort reports Progress Description: Describe the progress on the project during the past week, both in qualitative and quantitative. 1. List any significant accomplishments since the last status report (including the completion/revision of project deliverables). a. Complete Initial DART Analysis b. Completed inter Team role Assignments c. Identification of Shaper & Assitant Shaper d. Team website construction e. Accomplised Initial Client Interaction 2. If you are using COTS Process Framework, list the process areas that you worked in the past week (For example, P3, P4, etc.). a. b. c. d. Weekxx_PR_S02b_Txx.xls 3. Attach any client meeting notes. If you have not had a client meeting in the past week, say "No client meetings were scheduled". a. Cleared certain project requirments in the initial client meeting . The project requirment as gathered from Project description were a bit vague b. Ellobration on Project Description c. Identified Createive tension d. Identification of risks Weekxx_PR_S02b_Txx.xls Top Project Risks as of 09/19/2007 This Week Last Week 1 0 Risk Description No defined parameters for success Risk Mitigation Action Items Establish success criteria. Weeks Active 2 0 Unstable and changing requirements Establish clear requirements and scope of hte project 3 4 0 0 Implementation of Security Measures Use COTS Traning and Mentoring at client side post Project Actively Involve primary users in development process 5 0 Absense of Domain Expert Get Opinion of an domain expert or case study 6 0 7 0 8 0 COTS Interoperability Issues Do interoperability analysis before COTS selection Funding of the project is unclear Get funding information Commitment of Development Team Appoint member from client side to present Development team Weekxx_PR_S02b_Txx.xls # of Defects Project Mgmt. Requirements COTS Assessment Design Life Cycle Planning Configuration Mgmt. Feasibility Analysis Code COTS Tailoring COTS Glue Code development Test Deployment Total Injected 2 3 Removed 2 3 2 2 Problem Reports as of mm/dd/yyyy: * See QMP or Below for Definitions Type Issues Defects Problem Reports Definitions Issues Defects Problem Reports New Opened New Closed Old Closed Current Issues are problems that the "Author" can not fix solely in the artifact or at that specific time Defects in the artifact caused either by a human error (Avoidable Defect) or by situations that the "Author" has no control over ( Unavoidable Defect - e.g. change in the requirement). In case the team is using a Defect Tracking tool, that is the number of problems reported in the tool. You can also use the Review Forms to collect that information. In that case, this will be the total number of Concerns provided by the reviewers. Concers can be an issue, a defect or neither (consider that reviewers might indicate false defects). Problem Description: List any problems team is experiencing. This includes things that have caused delays, rework or any other roadblocks to anticipated progress. No. Problem Description Proposed Solutions Is it COTS Related? (Y/N) 1 Client Availability Will have to wait till next week N for main stake holder to arrive 2 3 Weekxx_PR_S02b_Txx.xls 4 5 Weekxx_PR_S02b_Txx.xls progress. Weekxx_PR_S02b_Txx.xls Weekxx_PR_S02b_Txx.xls List of third-party components being considered for use in the system as of mm/dd/yyyy Component Name Component use in the system Black Box x White Box Modify Code Function of the component in the system Related components Dependency In...