[437] in I/T Delivery
monthly project report - casetracker
daemon@ATHENA.MIT.EDU (Barbara Goguen)
Fri Feb 9 11:15:33 2001
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-Id: <v04020a08b6a9c5229f80@[18.152.0.142]>
Date: Fri, 9 Feb 2001 11:15:22 -0500
To: delivery@mit.edu
From: Barbara Goguen <goguen@MIT.EDU>
Cc: tooltime-team@mit.edu
project name: casetracker 1.5
project leader: barbara goguen, oliver thomas
report date:february 9, 2001
submitted by: barbara goguen
url: http://web.mit.edu/tooltime/notebook/
accomplishments past period:
- discussed development resource requirements and internal possibilities
with director of delivery and project sponsor
- discussed service and operations resource requiremrnts and possible
solutions with director of delivery and project sponsor
- set up alumni network services with accounts and email feeds
- corresponded with sarah shreeves from libraries about using casetracker
for tracking bugs in aleph
- started compiling documents to be shared during upcoming design review
- scheduled design review for 2/15, 3:30-5 in the demo center
- confirmed steve's increased commitment (50%) to the implementation phase
of 1.5
goals for coming period:
- continue to evaluation ejb tools and the possibility of going in the
direction of ejb rather than writing server from scratch
- continue to identify cause of problem with running Oracle 8.1.7 on test
server
- once bugs resolved, upgrade production machine to oracle 8.1.7
- conduct design review and hopefully get the go ahead to start coding
- continue to finalize development resources
- identify and/or design a service solution that gets us away from owning
service and operations responsibilities for casetracker
- move email and web enhancements from test into production
- decide whether casetracker should have a separate budget, and if so, what
that might look like. this is to followup on casetracker business plan
effort in october.
issues:
- need to off-load some of the knowledge and responsibility for casetracker
from oliver to steve and others on the team. it has been hard to integrate
new members into the work of the team since knowlege transfer takes time,
which none of us seems to have
key learning:
- it helps to think of work in phases and to sequence work appropriately
team dynamics:
- all is well, information is beginning to be more commonly shared, and
there is a renewed commitment to getting this work going
