[621] in magellan
One to One Student Computing at MIT Report 3/29/2001
daemon@ATHENA.MIT.EDU (Joanne Hallisey)
Thu Mar 29 16:16:53 2001
Mime-Version: 1.0
Message-Id: <p05010413b6e947b845c9@[18.152.6.151]>
Date: Thu, 29 Mar 2001 15:52:35 -0500
To: magellan@mit.edu, delivery@mit.edu
From: Joanne Hallisey <hallisey@MIT.EDU>
Cc: ownership@mit.edu
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Project Name: One to One Student Computing Pilot
Project Leaders: Phil Long, Joanne Hallisey
Report Date 3/29/2001
Submitted by: Joanne Hallisey
URL: http://web.mit.edu/is/discovery/ownership/
Accomplishments past period:
- Project pre-planning work begun
- Identified initial list of project team members
- Met with 4 process directors to discuss project including correct resourcing
- Began high level project work plan
- Dell presentation on laptop directions in 9-253 on March 8, 2001
- Talked to HP rep about arranging the same kind of presentation.
This was postponed pending discussions on potential alliance
agreement in the iCampus space.
- Put together initial task lists and questions for major task leaders
- Met with project major task leaders to verify resource and effort
requirements
- Began to collect resource requirements and to write a draft for a
grant proposal
- Looked at initial proposals submitted to iCampus
- Phil scheduled appointments with proposal principal investigators
- Presented at NERCOMP
Goals for the coming period:
- Meeting with one more process director scheduled for April 2
- Task leaders will update task detail as necessary including
predecessors and dependencies
- Attend meeting with HP and MITCET on potential grant for proposals
- Begin discussions with experiment participants
- Project kickoff meeting on April 4
- Submit proposal to grants committee for April 5
- Prepare slide presentation for funding for end of April
Issues:
- Waiting to hear what effect gifted laptops and possible vendor
alliance will have on hardware and OS decisions. Being at the mercy
of a somewhat random laptop designation could make it difficult to
accomplish all of the desired outcomes. RFP work is stalled until
that decision is made.
- Have not seen or engaged with discussions with iCampus
participants...do they know that IS is involved? We need to ensure
that they do. We will need to maintain communications with the
experiment participants and keep all groups aligned.
- It is clear that there are some difficult technical issues to
resolve especially in the shared file, DNS and DHCP spaces.
- Some IS organizational change is happening in processes key to the
success of this project.
- While most people are very interested in participating, they are
having difficulty seeing how this work can be accommodated in their
already over-allocated environment. How does IS ensure that people
are available to do the work in a timely fashion once funding is
approved? What is our method for re-prioritizing the work we do?
- Lots of meetings - very hard to schedule meetings.
Key Learnings:
- Meeting with the key participants in this project has been a
valuable source of information for planning.
Team Dynamics:
If we get the team for which we have planned, it should be dynamic.
