[1087] in I/T Delivery
casetracker report for feb 2003
daemon@ATHENA.MIT.EDU (Barbara Goguen)
Fri Mar 21 12:44:04 2003
Mime-Version: 1.0
Message-Id: <p05010403baa0e70263e1@[18.152.0.142]>
Date: Fri, 21 Mar 2003 12:43:58 -0500
To: delivery@mit.edu
From: Barbara Goguen <goguen@MIT.EDU>
Content-Type: multipart/alternative; boundary="============_-1163853856==_ma============"
--============_-1163853856==_ma============
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
project name: casetracker 1.5++
project leaders: goguen, barbara and thomas, oliver
report date: march 21, 2003
submitted by: goguen, barbara
project notebook: http://web.mit.edu/tooltime/
accomplishments past period:
- reviewed the option of replacing the "freeze" functionality with a
new waiting status; waiting without an accompanying date would be
waiting to hear back from client; waiting with an accompanying date
would be waiting until that date.
- deployed new application on test machine
- developed scenarios, identified testers, conducted usability testing.
- developed scenarios and identified testers for qa testing.
- worked with database services to schedule and apply security
patches on production server
- continued to explore ways to spend some one-time dollars on
casetracker development prior to the end of fy03, and how to tie
those into expenses that will continue into fy04
goals for coming period:
- review usability report, prioritize and implement reasonable recommendations
- post most recent version of casetracker policies to the web
- look into adding code that enables flexible sorting on case lists
that are the result of a search
- add waiting status on test database to explore issues in moving
from frozen to waiting
- begin thinking about phase 3 as completion of case sets will mark
the completion of phase 2
- decide if and when to hold the next ct-lead meeting, and possibly
another casetracker reporting clinic
team dynamics:
- queen esther rules!
next community milestones
- moving policies from "draft" to "real"
- rolling out case set functionality
--============_-1163853856==_ma============
Content-Type: text/html; charset="us-ascii"
<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { margin-top: 0 ; margin-bottom: 0 }
--></style><title>casetracker report for feb
2003</title></head><body>
<div>project name: casetracker 1.5++</div>
<div>project leaders: goguen, barbara and thomas, oliver</div>
<div>report date: march 21, 2003</div>
<div>submitted by: goguen, barbara</div>
<div>project notebook: http://web.mit.edu/tooltime/</div>
<div><br></div>
<div><b>accomplishments past period:</b></div>
<div>- reviewed the option of replacing the "freeze"
functionality with a new waiting status; waiting without an
accompanying date would be waiting to hear back from client; waiting
with an accompanying date would be waiting until that date.</div>
<div><br></div>
<div>- deployed new application on test machine</div>
<div><br></div>
<div>- developed scenarios, identified testers, conducted usability
testing.</div>
<div><br></div>
<div>- developed scenarios and identified testers for qa
testing.</div>
<div><br></div>
<div>- worked with database services to schedule and apply security
patches on production server</div>
<div><br></div>
<div>- continued to explore ways to spend some one-time dollars on
casetracker development prior to the end of fy03, and how to tie those
into expenses that will continue into fy04</div>
<div><br></div>
<div><b>goals for coming period:</b></div>
<div>- review usability report, prioritize and implement reasonable
recommendations</div>
<div><br></div>
<div>- post most recent version of casetracker policies to the
web</div>
<div><br></div>
<div>- look into adding code that enables flexible sorting on case
lists that are the result of a search</div>
<div><br></div>
<div>- add waiting status on test database to explore issues in moving
from frozen to waiting</div>
<div><br></div>
<div>- begin thinking about phase 3 as completion of case sets will
mark the completion of phase 2</div>
<div><br></div>
<div>- decide if and when to hold the next ct-lead meeting, and
possibly another casetracker reporting clinic</div>
<div><br></div>
<div><br></div>
<div><b>team dynamics:</b></div>
<div>- queen esther rules!</div>
<div><br></div>
<div><b>next community milestones</b></div>
<div>- moving policies from "draft" to
"real"</div>
<div>- rolling out case set functionality</div>
</body>
</html>
--============_-1163853856==_ma============--
