Weekly Review Form

E-Coach Reading Assessment

Work Package #

Role

Artifact Name

Sections / Modules

C
r
e
a
t
e

A
d
d

D
e
l
e
t
e

E
d
i
t

C
o
r
r
e
c
t

A
s
s
e
m
b
l
e

Date Started

Date Finished

% Work Completed

Time Period Hours

Total Hours

Deliverable(s)

4.3.2.3

Requirements Analyst

Requirements Document

11/13/01

11/18/01

100%

Logical Database Requirements.htm

4.5.2.2

Requirements Analyst

Requirements Document

Functional Requirements:

11/28/01

11/29/01

100%

Requirements2.htm

Totals

Work Package ID	Date / Start Time	Time Arrived	Time Left	Meeting Purpose
9.3.3.2	11/13/01 8:30pm	8:30pm	9:30pm	Assign new tasks to each member, set date for for assembling the Requirements document.
Totals

Work Package ID	Role	Bulleted List of Specific Tasks	Date Started	Date Finished	% Work Completed	Time Period Hours	Total Hours
N/A
Totals

The weekly review submission times are confusing. I think it would be more effective and methodical to have everyone submit their work on a set day each week regardless of holidays. This weekly review contains Work Packages from 3 weeks ago (11/13/01), with redundant material. I think it would have been more effective to keep an older copy of the short term plan and reference it to older Weekly Review submissions instead of creating a new weekly review (with old work included, just new WP numbers).
Libi Samuel and I met twice during this week. Once on Wednesday 11/14/01 and once on Friday 11/16/01, both times to discuss diagrams for the Logical Database Requirements. Each meeting lasted approximately 1 1/2 hours.
I met with Brian Crowell twice, to better understand the structure of the database and review key requirements that would ultimately affect how the programming team would implement the database.

Managers and Leaders