[144] in I/T Delivery
Discovery Team Leader Notes, 3/20
daemon@ATHENA.MIT.EDU (Mike Barker)
Mon Mar 23 14:53:19 1998
To: delivery@MIT.EDU, fortoul@MIT.EDU, tjm@MIT.EDU, brendakg@MIT.EDU,
mbarker@MIT.EDU, dbaron@MIT.EDU, tregan@MIT.EDU, vkumar@MIT.EDU,
jjv@MIT.EDU, pbh@MIT.EDU, azary@MIT.EDU, crockett@MIT.EDU,
jlittell@MIT.EDU, eyanow@MIT.EDU
Date: Mon, 23 Mar 1998 14:53:06 EST
From: Mike Barker <mbarker@MIT.EDU>
Very "sketchy" notes, but I thought I would share them...
attending: ljr, azary, crockett, fortoul, eyanow, jjv, ccount,
brendakg, mbarker, ganderso
1. We looked at the generic process map again. [in my notes, I tried
sketching a four quadrant map (discovery, delivery, service, support)
with an expanding spiral in it, and discovered that I think I like
that picture better than the simple one-time-through graphic we've
been using.]
2. Susan then talked about what integration is. Included: developing
standards, development tools, infrastructure. There is an integration
team that meets regularly. Influence set of infrastructure, connect
info across campus, vendor influence/relationships, data
analysis/admin (minimal interfaces; overlap of systems), integration
lab, physical and network security...fingers in many pies?
3. Places where we might expect interaction between integration and
discovery--integration needs a copy of the scope statement; they need
the data model; and they need a list of the infrastructure elements
that will be used.
Some questions I ended up with: What do we consider a "project"?
What assumptions do we have about what doing "it" takes? And where
does the work "get done"?
A Greg Quote: "There are a lot of words between the message there."
