[458] in magellan
Magellan Clinic for IMAP Email Services
daemon@ATHENA.MIT.EDU (Matthew Brody)
Thu May 11 14:37:17 2000
Message-ID: <391B0AF7.56F4834A@mit.edu>
Date: Thu, 11 May 2000 14:33:11 -0500
From: Matthew Brody <mbrody@MIT.EDU>
MIME-Version: 1.0
To: Magellan Mailing List <magellan@mit.edu>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
The below is an outline of points I discussed at today's Magellan
meeting re. an IMAP project clinic. These were drawn primarily from my
bi-weekly Magellan status reports.
Greg asked that I forward this to the list. I hope this proves helpful
to you in your project work.
Matt
>>>>>>>>>>>>>>> OUTLINE FOLLOWS >>>>>>>>>>>>>>>
MAGELLAN CLINIC FOR IMAP
Key learnings …
· Define the project scope carefully and be realistic about what can be
accomplished within a given time frame.
· Check in with the sponsors frequently -- especially in the beginning
and around issues of project scope.
·· Ensure that individual points of view by team members are respected
and encouraged
· Check in with team members frequently on an individual basis
· Begin writing the Discovery Report early --- building the text as
various components of the project yield conclusions, recommendations,
etc.
· Use project work as an opportunity to encourage team members to
interact with IS or other MIT staff members who they might not otherwise
frequently interact with
· Allow adequate time for Discovery Report review/feedback at the end of
the project.
· Continually take steps to maintain project momentum.
· No report needs to be perfect -- shoot for 90% and then call it a
day. Over editing can be non-productive.
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.
· Keeping the team focused given outside workload, priorities, etc.
· Work to avoid the project getting sidetracked because a particular
avenue of discovery is unavailable to you.
· Ensuring that we get substantive feedback from all team members on the
Discovery Report draft.
· Maintaining continuity between the Discovery and Delivery phases of
this project.
