Conferences & Events
Events for all Levels and InterestsStay
Jump Start Your Career GrowthStay
Get on the Higher Ed IT MapStay
Uncommon Thinking for the Common Good™Stay
Project Approval Process
We are in the process of attempting to move from a yearly, budget-based (committee) decision making process for projects to a year round process of project requests. This is due to the fact that we are growing rapidly and expanding to remote campuses. I have been asked to develop a decision matrix to help us determine what projects are approved and which one are not. Not a simple task at many levels.
Obviously IT does not want to get into the business of making these decisions. I see IT helping to facilitate this process, present solutions, and help to weigh the options, but not be the one to say yes or no. Of course, if there are major compatibility issues, sure, but that again would need to be part of the overall process.
Would any of you be willing to share how this happens at your institution? What does a technology project approval process look like at your institutions? Who gets to make the final decisions? What role does IT play in this process?
We have created a draft project charter template where stakeholders, budget info, and key information about the project request is documented. But where that should go next is my question. We have a Technology Advisory Committee. Should it go there and be vetted? Of course if funding is involved, that question has to be answered as well.
I realize there are a lot of questions here. Hopefully someone already has a framework in place they could share with us.
Director of Institutional Technology
PLEASE NOTE MY NEW EMAIL ADDRESS:
This email has been scanned by Marymount California University email security service
********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/discuss.