Posts Tagged ‘Programme Manager’

Project Update

No Comments »

Workflow with the Faculty Office

At the beginning of the week Cat, Sam and I met with Kate and Samantha from the faculty office. We were looking through stage 1 of the workflow which we had previously mapped out at the beginning of the year.  This meeting was very successful in working out what notifications faculty wanted and when they wanted them. It also helped to check the workflow was correct and what needed modifying. It was additionally decided that the faculty office would get their notifications within iPaMS rather than to a central faculty email. We currently still working on the workflow diagram and will be meeting with other departments to discuss their involvement in the workflow.

Lauren Welland (Project Support Officer)


Programmes

We have started to look at how programmes will be stored within iPaMS and which pieces of information we will need to hold against each specific programme.  The functionality of iPaMS has been a major consideration here as information from the programme specification will be used as a marketing tool for prospective students and as an information source for current students, it will hold all of the information required to comply with TQA and QAA standards and be worded in a way that will easily link in with the XCRI- CAP data feed.  Information imputed as a part of the workflow process for approving new programmes will also be archived against each specific programme, as will any changes made to the programme and the date in which these take effect.  Currently we have identified over 100 data entry fields for each programme; once we have established the level of data exchange between SITS and iPaMS this number could increase further.

Cat Hine (Project Support Officer)


User Roles

This week I have been working on assigning roles to users. I have first been creating different roles and permissions within iPaMS. Using Zend navigation I can hide/show relevant links dependent on the permissions these roles have. Some examples of roles will be system administrator, Webservice role and developer. I am also working on restricting view of data by College, to do this we are currently assigning all modules to their College. At the moment every iPaMS user has access to all the data in iPaMS, once we start moving other Colleges into the system we don’t want them to have access to edit other College’s data.

Ben Norcombe (Developer)


Code Improvement

I am currently rewriting the iPaMS module controllers. This builds on the work we did for the previous release of iPaMS to improve the codebase. That work was mainly about reducing the amount of SQL queries per page/action, whereas this time it is about cutting down on code repetition, thus creating reusable functions. The benefits will be that the iPaMS code is easier to maintain as well as more scaleable, setting us up nicely for work to begin on Programmes

Helen Connole (Lead Developer)


CLES Data

This week I have been working on collecting the CLES data needed for archiving into iPaMS. With help from the College we have collected a vast amount of word/pfd documents for their modules ranging from the academic years 08/09- 11/12. On Wednesday Sam, Cat and I met up with Andy, the Taught Programme Support Manager for CLES and discussed iPaMS. It was a very successful meeting where we showed iPaMS in action and discussed the move of CLES data onto the system.  As CLES’ data is all on word/pdf, a move to the database should help them significantly with reporting information and having easier access to their data.

Lauren Welland (Project Support Officer)


Quality Assurance

No Comments »

My name is Ruth O’Neale and I’m a IT Progamme Manager here at the University of Exeter, responsible for a number of projects of which CRIATE is one.  My role in the project is quality assurance, giving Sam and his project team day to day support but also acting as a critical friend and ensuring that the project is managed in the most effective way possible and in line with our University project governance and that of JISC.  I am keen that however possible project documentation is streamlined so no long onerous reports are produced and that we can easily keep JISC and internal stakeholders up to date on our progress  by using the same information but presented in the different templates required.

The project team are making good use of basecamp, an online collaboration website where we can share project information/documentation and this is a much more efficient way of sharing and maintaining project logs (risks, issues) etc rather than these being shared via email or on shared drives, especially as the project team is made up of individuals from various services (IT, Marketing, Faculty Office, Colleges).  It also alerts our basecamp members when updates are made so they are prompted to go and check the latest information.

A key success factor for our project is effective engagement with staff in the Colleges who have been maintaining their own separate databases up until now. Ensuring we communicate with them appropriately and in a timely way will be really important for our project.  As I’m delivering several projects across the University I may be aware of other factors outside of CRIATE which may impact on it and I see a role for myself in recognising these and in working with Sam  to mitigate any impact.  From a personal point of view like Sam I am relatively new to the University and to working in HE and I’m really enjoying working on the project and engaging with other institutions on the wider programme.