Project Scoring System

Prioritization Weight Factors

Data Management uses the results of DWH Steering Committee voting, as well as the factors stated below, to determine priority for each project request and propose a time schedule.

There are factors

• Cost
• Benefit
• Active Advocate
• Risk

Additionally, Mandatory and Future projects will also appear in the project plan.

Cost

Direct Cost - Estimate of costs for materials, outsourcing, etc.

• 3 = <$1,000
• 2 = <$10,000
• 1 = <$100,000
• 0 = >$100,000

Employees - Dedicated project time

• 3 = <40 hours
• 2 = <160 hours
• 1 = <320 hours
• 0 = <3 months

Benefit

Risk Mitigation - Project would reduce campus risk in business process or service

• 3 = Vital
• 2 = High
• 1 = Medium
• 0 = Low

Process Improvement - Project would improve efficiency of business process or service

• 3 = Vital
• 2 = High
• 1 = Medium
• 0 = Low

Active Advocate

Advocate Strength - Is there an external advocate willing to support the project?

• 3 = Has Resources
• 2 = Has Knowledge
• 1 = Has Time
• 0 = No Advocate

Risk

Scale Scoring according to highest single risk

Total Team Size - Team members directly working on project

• 3 =  2 people
• 2 = 3 to 4 people
• 1 = 1 person
• 0 = Non-Team

Workgroup Size - External subject matter experts participating in the project

• 3 = 1 to 3 people
• 2 = 4 to 6 people
• 1 = 7 to 10 people
• 0 = 0 or 10+

Technology/Technique/Process - Our technical comfort level for a successful implementation

• 3 = Expert
• 2 = Familiar
• 1 = New to Us
• 0 = Cutting Edge

Complexity - Planning for the unexpected

• 3 = Project is well-defined
• 2 = Problems have been identified
• 1 = Multiple approaches
• 0 = Project is vaguely defined

Political Profile - Who is asking?

• 3 = Single Unit
• 2 = Multiple Units
• 1 = Central Offices, Sr Mgmt, UCOP
• 0 = Public

Deployment Impact - Impact of project on constituents

• 3 = Single Unit
• 2 = Multiple Units
• 1 = Central Offices, Sr Mgmt, UCOP
• 0 = Public

Mandatory

Any project determined to be Mandatory will be included in the project plan. However, this classification is to be used judiciously. It is intended mainly for projects where the timing is not under our control or influence, such as responding to changes to source systems that would bring our systems to a halt. It is not intended for system upgrades or other time- negotiable or internal projects.

Future

Any "heads up" requests about future needs are appreciated. They will not be included in the final plan, but they are used as reminders to be revisited during the next planning cycle.