Date: Thu, 28 Mar 2024 10:09:54 +0000 (UTC)
Message-ID: <266093594.6057.1711620594152@ip-10-10-7-29.ec2.internal>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_6056_75737491.1711620594152"
------=_Part_6056_75737491.1711620594152
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
N2HE Minutes 5-8-12
N2HE Minutes 5-8-12
Tuesday 5/8/2012 @ 11 EST
Attendees: Chris Eagle, Jim Phelp=
s, John Grover
- Set up Google Hangout. Seamles=
s start this week! Next month we expect to record the meeting.=
- Introductions. All introduced themselves. John works for =
the University of Maine and has been there since 1988 when he left his dair=
y farm to become a student. He is the Director of Systems of Operatio=
ns. One of the challenges of U of Maine is that it is very geographic=
ally diverse with many different campuses. This led to a discussion o=
f Central Systems vs. Edge systems.
- Discussion:
- Central vs. Edge: How do you decide =
what runs where? How to you get buy-in? How do you get the Edge=
to stop and Central to start? There was much discussion following. &=
nbsp;John commented that Maine has a new-ish CIO (1 year) who is improving =
the process for Edge-to-Central. The noted that most requests to Cent=
ral come from CFO's or Presidents (business folks) and not very often from =
Edge IT. This provides Edge buy-in as well as ensuring that value is =
created.
- Methods used to track problems and i=
ssues. John explained that there is a manual step to get from their h=
elp desk software (for level 1 and level 2 support) to their development tr=
acking system (when a ticket was escalated to level 3). All three peo=
ple on the call noted that their campus worked the same way. Jim comm=
ented that this isn't necessarily a bad thing, since this provides a 'smart=
' gate for tickets to be escalated into the developer's system, and tickets=
with trivial solutions could just be handled directly in the help desk sys=
tem.
- Portfolio management. John ask=
ed what the different campuses were doing for portfolio management. S=
hort discussion on prioritization and tracking. John: "How =
do IT projects surface?" Jim: "Like Kraken from the deep." (Yes, thes=
e discussions are VERY serious!) All three participants commented on =
their maturing governance structures, but none are mature enough to use as =
a case-study.
- How do you get grassroots projects m=
oving? (Chris asks this question, in some form, pretty much every month). &=
nbsp;SOA was used as an example. John commented that he is able to us=
e their Chief Information Security Officer as an ally. Jim commented =
on the importance of getting a 'poster child' project to be able to show a =
success. The consensus was to "find ways to keep spinning =
the flywheel until it spins by itself." There was also some discussio=
n about using outside consultants to bring "weight" to recommendations and =
projects.
- We did not cover the question in ite=
m 4. These questions are going to be answered via a survey.
------=_Part_6056_75737491.1711620594152--