[368] in I/T Delivery
monthly project report - casetracker
daemon@ATHENA.MIT.EDU (Barbara Goguen)
Fri Oct 6 10:04:21 2000
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-Id: <v04020a00b603878e7160@[18.152.0.142]>
Date: Fri, 6 Oct 2000 10:04:13 -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: october 6, 2000
submitted by: barbara goguen
url: http://web.mit.edu/tooltime/notebook/
accomplishments past period:
- continued to integrate steve's thinking into the work of the team
- scheduled a casetracker 1.5 off-site project planning meeting for 10/24
- got ssit email feeds and casetracker accounts set up. presented overview
of how to work with the system.
- continued work on understanding current workflow patterns into and
through casetracker
- met with lorraine rappaport to better understand overlap between tool
discovery project coming out of ntip and casetracker directions
- met with alicia allen to better understand how vdist is currently
tracking their work in casetracker and other tools
- reviewed and clarified current architecture issues in order to help steve
get oriented to the project; documented in project notebook under design
documentation.
- made sample reports (brio scripts) available from the project notebook.
(this was done a while ago, but wanted to draw attention to it.)
- drafted business plan for casetracker 1.5 project team as part of
re-budgeting and business planning effort
goals for coming period:
- make sure lorraine has casetracker desktop installed for her exploration,
and continue conversation with her about overlaps and future tools planning
- followup with ssit about their experiences using casetracker
- conduct off-site planning meeting and from that draft proposed plans to
be used as starting points for conversations with others including
integration
- have more detailed conversation with circle.com regarding development
resources for hire
- move email and web enhancements from test into production
- populate it-partners access list with a small set of "testers"
- meet with greg anderson to discuss next steps for discovery effort(s)
issues:
- lack of time to focus on this project due to too many commitments and too
much change
key learning:
- you cannot get creative thinking out of over-committed, exhausted staff
team dynamics:
- all is well.
