| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-Id: <v04020a08b721f852a8fa@[18.152.0.142]> Date: Fri, 11 May 2001 16:26:31 -0400 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: May 11, 2001 submitted by: barbara goguen url: http://web.mit.edu/tooltime/notebook/ accomplishments past period: - conducted integration review on 4/9 - updated project notebook; take a look! - recruited additional resources to the team in part to replace nick howard, and in part to extend our ability to design, test and operate the new services. new resources are barbara johnson, fred baars, and potentially brian fisher. - set up cvs repository space for casetracker development - prototyped rudimentary proof of concept version of "view a case" - set up categories for sarah shreeves from libraries to use casetracker for tracking bugs in aleph; scheduled followup meeting with debra wiley from fss. - began learning about use cases to assist with our specifications work goals for coming period: - re-assess sponsorship of project with new IS organizational structure - get fred baars up to speed on project in particular the operational and administrative pieces currently handled by oliver. - hold second brainstorming session working toward a specifications document this time focusing on use cases on 5/17. - meet with rocklyn during week of 5/14 to assess whether/when east could take on some of the maintenance and operational aspects of casetracker - carry out data warehouse download to refresh the lookup data; teach process to fred baars - determine how best to handle developer "how-to" documents being drafted by steve; where to put them, how to fit them in with other documentation plans - determine process for tracking new users of casetracker, such as sarah shreeves and debra wiley to ensure we followup on their requests in timely manner and get earlier feedback on their pilot uses. - move email and web enhancements from test into production - do preliminary tracking of expenses to facilitate the creation of a casetracker budget should the decision be made to do so. - determine timing for upgrading production machine to oracle 8.1.7 issues: - still struggling to keep this work moving forward while all members of the team have other issues competing for their attention key learning: - it helps to keep track of all the tasks team dynamics: - all is well with existing members; need to introduce new members to the effort.
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |