[708] in I/T Delivery

home help back first fref pref prev next nref lref last post

monthly project report - casetracker

daemon@ATHENA.MIT.EDU (Barbara Goguen)
Fri Feb 15 11:30:48 2002

Mime-Version: 1.0
Message-Id: <p05010407b892e5e94acc@[18.152.0.142]>
Date: Fri, 15 Feb 2002 11:30:45 -0500
To: delivery@mit.edu
From: Barbara Goguen <goguen@MIT.EDU>
Cc: tooltime-team@mit.edu
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

project name: casetracker 1.5
project leader: barbara goguen, oliver thomas
report date:february 15, 2002
submitted by: barbara goguen
url: http://web.mit.edu/tooltime/notebook/

accomplishments past period:
- completed draft of plan for upgrading the os (required step for 
upgrading to oracle 8.1.7) and the database in order to move the 
latest version of casetracker into production
- reviewed oracle audit file to identify all users of casetracker 
desktop; drafted and distributed email to affected clients clarifying 
issues and informing them of options for handling the upgrade
- discussed casetracker rules of use and other policy work with 
director of support, and began planning for an initial category 
owners' meeting to share this and other work with them

goals for coming period:
- complete review of document about transferring cases between 
categories, and then share with the category owners, along with draft 
of initial rules of use
- schedule meeting with oliver, lisa robinson and myself to discuss 
what might make sense moving to east
- complete all casetracker desktop upgrades by 3/1
- meet to plan next set of design discussions around status field, 
case lists, web searches, and prioritization of brainstormed lists 
from last design meeting
issues:
- need to adjust our schedule for moving latest version into 
production due to unforeseen issues
- revise casetracker web welcome screen to be more informative and intuitive
- revisit our document about casetracker development phases to 
refresh and modify our plans as needed
- make appropriate links between casetracker user documentation and 
casetracker rules of use and policy statements
- determine whether and how we might make effective use of one-time 
project dollars this upcoming quarter to assist in moving casetracker 
development forward

key learning:
- somewhere along the way we really did become an enterprise tool 
with 20-25 different top level categories, and growing all the time

team dynamics:
- all is well

home help back first fref pref prev next nref lref last post