[710] in magellan
IS Server Business Status Report 4.4.02
daemon@ATHENA.MIT.EDU (Joanne Hallisey)
Thu Apr 4 16:20:09 2002
Mime-Version: 1.0
Message-Id: <p05010411b8d26d30f905@[18.152.6.151]>
Date: Thu, 4 Apr 2002 16:02:38 -0500
To: magellan@mit.edu
From: Joanne Hallisey <hallisey@MIT.EDU>
Cc: isserver@mit.edu
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Project Name: IS Server Business
Project Leader: Joanne Hallisey
Report Date:4/4/02
Submitted by: Joanne Hallisey
URL: http://web.mit.edu/is/discovery/isserver
Accomplishments (what did we accomplish in the last period?)
- Followed up survey with interviews for clarification
- Summarized and analyzed survey data
- Collected peer school information
- Put together some "standard" server configurations
- Sent benchmark server configurations to 3rd party vendors for pricing
- Continued to build report
- Outlined customer needs and expectations
- Outlined some potential new service opportunities
- Began to formulate recommendations
Goals (What are we planning to accomplish in the next period?)
- Conduct interviews with some large labs and centers ie. LCS, Sloan
- Hold team meeting with Sponsors
- Summarize and analyze peer school information
- Complete price comparisons
- Define new service offerings
- Refine recommendations based on Sponsor feedback
- Begin financial models
- Continue to build report
Have there been any developments that may impact the scope or schedule?
- We had to postpone the sponsor meeting. This did not necessarily
slow the progress. But we did gather new insights from the
discussion.
Do we need any additional information from the client,
stakeholders,sponsor? -yes, we have identified a need to get more
information from the large labs and centers who may do their own
server operations.
Issues/Key Learnings
This is a large undertaking with many possible new service solutions.
It will be important to remember that we do not have to build a
solution that will provide all of the services, but we do need to be
able to provide the customer with guidance and point to other viable
resources.
Trust goes two ways.
Team Dynamics
Good.
