[415] in magellan

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

IMAP Email Project Update - March 15, 2000

daemon@ATHENA.MIT.EDU (Matthew S. Brody)
Wed Mar 15 12:04:55 2000

Message-ID: <38CFC387.2D482C8B@mit.edu>
Date: Wed, 15 Mar 2000 12:08:23 -0500
From: "Matthew S. Brody" <mbrody@MIT.EDU>
MIME-Version: 1.0
To: magellan@mit.edu
Content-Type: multipart/alternative;
 boundary="------------7B6F9C719AB820AF7630AEF5"


--------------7B6F9C719AB820AF7630AEF5
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Project Name:   IMAP Email Services
Project Leader: Matt Brody
Report Date      March 15, 2000
Submitted by:    Matt Brody
URL:
http://http://web.mit.edu/is/discovery/imap/IMAP%20Project%20Notebook.htm

Accomplishments past period:

-  Launched project team
-  Developed overall project scope and initial version of project plan
-  Created project notebook
-  Made project work assignments to team members
-  Conducted initial check-ins with project sponsors

Goals for the coming period:

-  Continue our efforts at organizing the work.
-  Focus on outreach to key stakeholders.
-  Conduct email survey of early, unsupported IMAP adapters on mit.edu
post offices.
-  Conduct informal survey of email practices/standards at "Ivy Plus"
institutions.
-  Identify any initial major issues with email clients being evaluated
for IMAP (Eudora and Netscape).
-  Complete draft outline of Discovery Report and share with team
members.

Issues:

- Ensuring collaboration between the team members since their
assignments are highly interrelated.
- Connecting with key IS opinion leaders to ensure our efforts are
aligned with the overall IS architecture.

Key learnings:

- Define the project scope carefully and be realistic about what can be
accomplished within a given timeframe.
- Check in with the sponsors frequently -- especially in the beginning
and around issues of project scope.

Team dynamics:

- So far the team has come together nicely and seems very interested and
engaged in the work at hand.

Additional comments:

-  None

--------------7B6F9C719AB820AF7630AEF5
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Project Name:&nbsp;&nbsp; IMAP Email Services
<br>Project Leader: Matt Brody
<br>Report Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; March 15, 2000
<br>Submitted by:&nbsp;&nbsp;&nbsp; Matt Brody
<br>URL:&nbsp; <A HREF="http://http://web.mit.edu/is/discovery/imap/IMAP%20Project%20Notebook.htm">http://http://web.mit.edu/is/discovery/imap/IMAP%20Project%20Notebook.htm</A>
<p>Accomplishments past period:
<p>-&nbsp; Launched project team
<br>-&nbsp; Developed overall project scope and initial version of project
plan
<br>-&nbsp; Created project notebook
<br>-&nbsp; Made project work assignments to team members
<br>-&nbsp; Conducted initial check-ins with project sponsors
<p>Goals for the coming period:
<p>-&nbsp; Continue our efforts at organizing the work.
<br>-&nbsp; Focus on outreach to key stakeholders.
<br>-&nbsp; Conduct email survey of early, unsupported IMAP adapters on
mit.edu post offices.
<br>-&nbsp; Conduct informal survey of email practices/standards at "Ivy
Plus" institutions.
<br>-&nbsp; Identify any initial major issues with email clients being
evaluated for IMAP (Eudora and Netscape).
<br>-&nbsp; Complete draft <u>outline</u> of Discovery Report and share
with team members.
<p>Issues:
<p>- Ensuring collaboration between the team members since their assignments
are highly interrelated.
<br>- Connecting with key IS opinion leaders to ensure our efforts are
aligned with the overall IS architecture.
<p>Key learnings:
<p>- Define the project scope carefully and be realistic about what can
be accomplished within a given timeframe.
<br>- Check in with the sponsors frequently -- especially in the beginning
and around issues of project scope.
<p>Team dynamics:
<p>- So far the team has come together nicely and seems very interested
and engaged in the work at hand.
<p>Additional comments:
<p>-&nbsp; None</html>

--------------7B6F9C719AB820AF7630AEF5--


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