IN Year Project Proposal - LO Grade Reporting

Portfolio

HSS

Programme

College of Humanities and Social Science (CHSS)

Programme Priority

4

Proposed Overall Priority

3

Programme / Portfolio Owner

Fraser Muir 

Programme / Portfolio Manager (IS Applications)

Andy Stewart  

Project Name  (Project Code)

 HSS013

Project Sponsor  (Project Executive)

Geoff Lee / Fraser Muir

Project Manager (IS Applications)

 Andrew Stewart

Senior User

Olwen Gorie

Senior Supplier (IS)

N/A

Business Lead

Geoff Lee / Alex Burford

Other Key Stakeholders

What will this project deliver?

 The ability to report rubric-level grades to the ECA exam boards without duplication.

Why is the project needed? What problem is being solved? What are the benefits?

 The schools of Art, Design and ESALA within ECA grade their student work against learning outcomes.  The only way to do this within Learn is to use the rubric tool (for either Learn assignment boxes or Turnitin assignment boxes). However, Learn aggregates these scores to a single grade and it is this single grade which is returned to the relevant column in the Grade Centre. ECA exam boards require to see the rubric-level score for each student. Therefore, at present, graders need to keep two copies of their scores – one in Learn and one offline (later presented to exam boards) – risking error in the reporting of student grades. Being able to extract rubric-level grades within Learn would mean only one (golden) copy of data would be required. This would eliminate the possibility of error and drastically reduce both academic and administrative duplication of effort. In addition, we are mindful of the new exam board functionality in EUCLID and would like to use the resources of this project to ensure that these learning outcome-level grades are appropriately represented in the new system.

How will the services delivered be maintained after the project is complete?

Proposed Start Date For Project

 March 2016

Target Delivery Date

 July 2016

Category

Discretionary

Funding Source

HSS Ring Fenced Budget

Software Development

Risks

Risk is the uncertainty that comes from making any change. A risk may or may not happen but if it occurs it will have a material impact on the success of the project.  Effective risk management requires identification of the risk, an assessment of the probability and impact, contingency planning and  identification of mitigation action. Identify the most important risks for this project and any management actions required to reduce the negative impact or the probability of the risk occurring.  Probability =  Low, Medium, High, Critical Impact = Low, Medium, High, Critical. Management Approach is either: ¿    Monitor/Retain - accept the risk but continue to monitor ¿    Reduce - take action to reduce the impact or probability ¿    Remove - eliminate the risk entirely ¿    Transfer - move the risk to a third party For the selected approach identify the most important actions that will be taken to manage the risk.

Estimated IS Apps Days

Medium (120)

Estimated Business Partner Days

Small (50)

Estimated Confidence

 Reasonably Confident (Similar To Previous Work)   

Add notes on estimate confidence here 

Estimation References and Assumptions

Provide any other relevant information about the the project and it's estimate. This may include: ¿    Assumptions about the project approach, scope or deliverables ¿    Details of previous similar projects ¿    Links to supplier web sites or other external resources ¿    Links to attached documents  ¿    Other challenges or uncertainties not covered elsewhere ¿    Other opportunities or benefits not covered elsewhere  Record as many details as are relevant

Approvers (IS Applications)

Rhian Davies

Approvers (Business Partners)

Fraser Muir