Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Table of Contents

Once a project reached prioritization in the project intake process, it will be given two project scores: a benefit score and a cost score. Both scores illustrate how well a project benefit SPU and how costly the project will be. Currently, the scores are deliberated and assigned by CIS with input from CIS directors and other key stakeholders.

The project score seeks to provide stakeholders with a quick glance at the value of a project. These scores only highlight a portion of the many criteria used to prioritize a project and they do not discount any possible criteria that may be present as part of evaluating or prioritizing a project proposal. 


If you have questions about the score for a particular project, contact a CIS BSA or PM.

If you have not submitted a project proposal, click here to fill out a short project request form.

To check the status of your project proposal, go to the Project Roadmap or the Project Backlog; or, contact a CIS BSA or PM.


Benefit Score


The benefit score is rated on a scale of 1-5 and comprised of an average of scores from 5 different criteria. The higher the score in each criteria, the bigger the impact that the project is expected to have in that area. The criteria and metrics are as follows:

CriteriaScore & Metrics
12345
Supports University Mission, Strategic Plan, and/or Revenue Generating InitiativesProject minimally supports one of the criteria.
Project moderately supports some of the criteria or significantly supports one of the criteria.
Project significantly supports all of the criteria.
Enhances Learning, Supports Teaching and/or Advanced Research InitiativesProject minimally supports one of the criteria.
Project moderately supports some of the criteria or significantly supports one of the criteria.
Project significantly supports all of the criteria.
Improves Service to the Faculty, Staff, and Students (The Campus Community)Project improves service for a small population of the campus community. 
Project improves service for a moderate population of the campus community. 
Project improves service for the entire campus community. 
Improves Efficiency, Improves Effectiveness, and/or Reduces CostsProject supports one of the criteria for a single department. 
Project supports some of the criteria  or for multiple departments. 
Project supports all of the criteria for all departments. 
Mitigates Risk to the InstitutionProject minimally mitigate risk to the institution.
Project moderately mitigates risk to the institution.
Project significantly mitigates risk to the institution.

The scores for all the criteria are then averaged to result in the project benefit score. 

Cost Score


The cost score is also rated on a scale of 1-5 and is based on an average of scores from 3 different criteria. For each criteria, a high score means that the project's costs are expected to be higher. The criteria and metrics are as follows:

CriteriaScore & Guide
12345
Budget Cost< $1,000$1,000-$9,999$10,000-$24,999$25,000-$99,999> $100,000
Labor Cost< 2 Staff & < 1 month2-3 Staff & 1-3 months4-5 Staff & 4-6 months5-6 Staff & 7-12 months> 6 Staff & > 12 months
Ongoing Operational (Maintenance) Cost< $1,000 per year and < 10 hours per year$1,000-$9,999 and/or 10-39 hour sper year$10,000-$29,999 and/or 40-60 hours per year$30,000-$59,000 and/or 60-100 hours per year> $60,000 and/or > 100 hours per year

The scores for all the criteria are then averaged to result in the project cost score. 

Interpreting Each Score


Both scores are assigned to a project to assist in quickly identifying the merits of a project proposal from purely a cost/benefit standpoint. In addition to cost and benefit, there are other factors that are considered when prioritizing a project. Learn more about those factors in the Evaluation and Prioritization article

The scores are meant to summarize a deeper cost/benefit analysis and as such, further conversation with CIS directors, a CIS project manager or business analyst, and other stakeholders around campus regarding each score is encouraged.

  • No labels