Team Number: 20
Week: 4
Program Size (SLOC) Actual
Base 0
Added 0
Deleted 0
Modified 0
Reused 0
# of COTS 0
Total New SLOC 0
Effort (Hours) Planned Actual
Project Mgmt. 9 8
Requirements 5 4
COTS Assessment
Design
Life Cycle Planning 2 2
Configuration Mgmt.
Feasibility Analysis
Code
COTS Tailoring
COTS Glue Code development
Test
Deployment
Cumulative No. Of tasks Man-hours
Actual Planned Actual
Planned
Date Wk. Completed On Sched Late Date Wk. This Wk. Cumulative This Wk. Cumulative
09/19/2007 1 10 7 0 09/19/2007 1 73.5 73.5
09/26/2007 2 7 7 0 09/26/2007 2 98 171.5
10/03/2007 3 7 7 0 10/03/2007 3 121 292.5
10/10/2007 4 5 5 0 10/10/2007 4 87 379.5
10/17/2007 5 10/17/2007 5
10/24/2007 6 10/24/2007 6
10/31/2007 7 10/31/2007 7
11/07/2007 8 11/07/2007 8
11/14/2007 9 11/14/2007 9
11/21/2007 10 11/21/2007 10
11/28/2007 11 11/28/2007 11
12/05/2007 12 12/05/2007 12
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. Met our Client, Dr. Chris Boehm to get feedback on the prototypes that we have prepared
b. We contacted our off campus team member Ausin Cole to discuss about the first wiki win win negotiation session
c. Held a second WIKI win win negotiation session with the client to reduce the requirment sets
d. Prepared wiki win win negotiation report.
e. Prepared the MS Project Plan for the coming week.
f. Performed risk assesment using Dart tool
g. Prepared LCO CORE which consists of following documents SSRD V1.0, OCD V1.1 and SID V1.0
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.
Weekxx_PR_S02b_Txx.xls
d.
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. Meeting with the client held on October 9, 2007. - Report attached as a pdf file.
b.
c.
d.
Weekxx_PR_S02b_Txx.xls
Top Project Risks as of 10/10/2007
Last
This Week Risk Description Risk Mitigation Action Items Weeks Active
Week
The client wants the system to be used globally.
1 2 If there are a lot of users trying to access the Make the system capable of dealing with heavy loads 2
system in the future. The system may collapse
Currently the development team is planning to
use SQL server database or Oracle 9i.
The team needs to properly analyze the pros and cons of
Sqlserver does not support multimedia
2 2 each type of database and come up with the one which is 3
applications very well and Oracle 9i is not very
most suitable for the development of this project.
compatible with .Net which is being used as the
front end development tool.
Weekxx_PR_S02b_Txx.xls
# of Defects Injected Removed
Project Mgmt. 1 1
Requirements 4 4
COTS Assessment
Design
Life Cycle Planning 1 1
Configuration Mgmt.
Feasibility Analysis
Code
COTS Tailoring
COTS Glue Code development
Test
Deployment
Total 6 6
Problem Reports as of mm/dd/yyyy: 10/10/2007
* See QMP or Below for Definitions
Type New Opened New Closed Old Closed Current
Issues 3 3 0
Defects 6 6 0
Problem Reports
Definitions
Issues Issues are problems that the "Author" can not fix solely in the artifact or at that specific time
Defects 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).
Problem Reports 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
Weekxx_PR_S02b_Txx.xls
2
3
4
5
…
Weekxx_PR_S02b_Txx.xls
progress.
Weekxx_PR_S02b_Txx.xls
List of third-party components being considered for use in the system as of 10/10/2007
Component Component use in the
Function of the component in the system Related components
Name system
Black White Modify
Dependency Interaction
Box Box Code
Components that were filtered in the previous week
Component
Rationale for filtering the component Notes and References
Name
Project Indicators as of xx/yy/zzzz
Cumulative Project Effort
400
Man-hours
300
Planned
200
Actual
100
0
Week
Project Progress
Cumulative no. of tasks
12 Late
10
8 On Sched
6
4 Completed
2 Planned
0
Week no.
Weekxx_PR_S02b_Txx.xls