Yes, in fact EDUCAUSE has sponsored/organized several talks on this,
including Mark Jeffreys, professor at Northwestern U who really
developed the IT portfolio management concept. Also speaking on this
has been Kay Whyburn Rhodes of Texas Tech which has done great work in
this arena. ECAR published a research bulletin on this (by Jeffreys and
Goldstein) February 1 of last year.
And in fact you are quite right, this topic does fit closely with the
enterprise 2006 goals and in fact is incorporated into this program.
That conference will be held May 24-25 at the Intercontinental Hotel in
Richard N. Katz
4772 Walnut Street, Suite 206
Boulder, Colorado 80302-2996
(303) 939-0318 (phone)
(303) 440-0461 (fax)
From: Joseph Konopka [mailto:[log in to unmask]]
Sent: Wednesday, February 15, 2006 9:40 AM
To: [log in to unmask]
Subject: Re: [CIO] Prioritization of Projects
Hi everyone, has the topic of "enterprise portfolio management" been
addressed at any of the previous educause events? This seems to be an
interesting thread that I would certainly welcome more information. (I
am aware of the fact that it is a very ho topic in much of the CIO
literature outside of the academic environment)
If not, could this topic fit into the upcoming "enterprise 2006"
conference sponsored by educause?
Joseph A. Konopka
Business Systems and Technologies
1 World's Fair Drive, Suite 3400
Somerset, NJ 08873
E-mail: [log in to unmask]
>>> Theresa M Rowe <[log in to unmask]> 2/9/2006 4:24:34 PM >>>
We use our ticketing system Footprints accept work requests or
suggestions from anyone at the university. We found trying to keep
"tasks" separate from "projects" to be too difficult to manage.
We've also got a "collaborative organization structure" that I've been
playing around with, trying to document. I've attached the boxes. I
meet regularly with these groups to identify and prioritize projects,
including those submitted in the Footprints system.
For project work, we set the highest priorities by:
1) Approved by President, Vice President, Associate Vice President, or
2) Cyclical system or component replacement
Within system or component replacements, we can establish a point
formula to determine the relative priority of the item to be replaced.
(System Age + Technical Age) * Risk Factor * Scope Factor * Security
Factor * Strategic Plan Factor
System Age: number of years since purchase
Technical Age: how old is the technology platform (we've been known to
buy refurbished equipment or buy something late in the technology
Factors: We try to tally something on a 1 to 5 scale, with
5 meaning "time to replace".
Risk Factor: Number of failures within the last year, vendor announced
desupport, technical obsolescence
Scope Factor: Number of users, number of access points
Security Factor: Potential for security incident, breach, etc.,
Strategic Plan Factor: Linkage to the strategic plan, dependencies,
We pull this together to assist with budget allocation
decisions prior to the start of a new fiscal year, and this
becomes our tactical plan for the year.
On a day to day basis, we have many service requests.
Service requests are evaluated based on the customer stated
The work of the campus is stopped
The work of a department is stopped
The work of an individual is stopped
Requested installation, activation or move
Request for improvement
Request for development
It would be nice if....
Priority actions are based on:
* production down
* stopped critical business or government mandated processes
* data integrity issues
* technical currency
* VP or Assoc. VP approved projects
* After that, we work on the oldest request first.
Assistant Vice President
University Technology Services
www.oakland.edu/uts - the latest news from University Technology
Participation and subscription information for this EDUCAUSE Constituent
Group discussion list can be found at http://www.educause.edu/groups/.
Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.