You are here

DevProj Improvements

Project ID: 
152
Current stage: 
Manager: 
Unit: 
What: 

Description: Alastair reported that he had attended a presentation by Mark Ritchie on IS app's new "basic" project methodology. It appears to be pretty similar to ours, but unfortunately based on a Wiki rather than a database. There is potential here for aligning our project database with their methodology and perhaps even exporting any modified devproj for use by the rest of the university. It was agreed that this would be done as part of the proposed devproj improvement project.

Deliverables:

Why: 

Customer: Computing staff. Members of the School for the purpose of looking at and submitting projects.

Case statement: While the current devproj system provides the core functionality of what is required it lacks in usability, has a number of replicated fields associated with a project description making it unclear what to put where and does not have particularly functional tracking abilities.

When: 

Status:

Timescales:

Priority:

Time: 2 weeks maximum.

How: 

Proposal: See plan. This is an evaluation only.

Resources:

Plan: Identify core problems with existing system by review.
Evaluate whether refinement of the existing system or an alternative system would be the best option.
Look at the IS Apps system to see what alignment there might be.
Propose solution.

Other: 

Dependencies: None of note.

Risks: None of note.

Milestones

Proposed date Achieved date Name Description