Completion Report
Project Summary:
Contributors
Role | Department | Name |
Project Manager and Programme Manager (Owner) | IS Applications - Project Services | Tim Gray |
Project Sponsor | University Website Programme | Dawn Ellis |
Business Area Manager | University Website Programme | Bruce Darby (was Miles MacCalman) |
Web CMS Support Officer | University Website Programme | Stratos Filalithis |
Senior Developer | IS Applications - Development Services | Mairi Fraser |
TechMan Representative | IS Applications - Technology Management | Chris Cord |
Apps Man Representative | IS Applications - Application Management | Ana Heyn |
DevTech Representative | IS Applications - Development Technology | Peter Jackson |
Project Review
The project started in September 2012. Due to a change in programme priorities the project was suspended until January 2013 when R&D was completed. The R&D identified suitable opportunities for development, these were developed in March and build signed off as scheduled. Integration sign off was achieved with a slight delay due to concerns about the search results and performance. UAT was moved out again due to changing priorities within the programme with UAT signed off in August, this had an effect on the original LIVE date. The revised deployment date of October was then moved as a result of issues with one of the live servers as a consequence of a fire at KB. The next available slot to deploy after these issues could be fixed was in early December. Some analysis was undertaken after deployment with no significant performance issues recorded using the new search tab, although it was noted that the logical i/o activity on the DB was high.
Objectives, Deliverables and Success Criteria
As defined at the outset of the project:
- Give the developer an initial degree of time to complete some R&D on the search functionality and to define what aspects of the functionality requested can be delivered and highlighted any simple enhancements that may have not be defined.
- Ensure that the necessary time is given to any new interface/layout that is proposed and allow usability testing to be completed.
- To consolidate all search functions onto a single tab in interface.
- To develop search function so any combination of criteria can be selected for a single search query.
- Allow search to be set at a specific point in the content tree so that it displays results from only the selected section.
- Use a fuzzy search on the ‘Name’ field.
- Introduce fuzzy search on ‘Title’ field.
- Ability to search on articles/sections saved by any individual user (based on UUN).
- Display total number of results rather than statement such as ‘at least 60 results’.
- Ability to search on orphaned article and sections.
Success Criteria
- Improved search function, with usable and intuitive interface.
- Ability for users to search pages/sections within their specific section of the content tree on any combination of criteria covering:
- Content/template type (different types of articles/section available, including media bank)
- Name field (fuzzy search)
- Title field (fuzzy search)
- Min/Max date and time
- Min/Max ID
- UUN of last author on latest version
- Review date
- Workflow status (draft, ready for approval, published to live)
- Disconnected from content tree
- Locked articles/sections
- Ability for users to search workflows by UUN or group name.
- Ability for users to search groups by UUN or workflow name.
- For users to clearly see how many results a particular search has resulted in.
- Users should only be able to search article and section types that they have permission to access; core system files shouldn’t appear in results.
Scope
The project remained in scope and fulfilled the objectives.
Schedule
The project started in September 2012, was suspended until January 2013 and scheduled for deployment in August 2013. The deployment was then delayed until December due to prioritisation, UAT and service issues as detailed above.
Analysis of Resource Usage:
Staff Usage Estimate: 37 days
Staff Usage Actual: 35 days
Staff Usage Variance: -5%
Other Resource Estimate: 0 days
Other Resource Actual: 0 days
Other Resource Variance: 0%
Explanation for variance:
The project will use a couple of days more than estimated. This can be attributed to the longer duration which as noted in the review was down to issues from UAT and the delay in deployment.
Key Learning Points:
This project has again emphasised the importance of all colleagues from UWP and Apps working closely together during the early stages of the project to ensure that the achievable deliverables are aligned with the maximum benefit for the customer.
Outstanding issues:
There are no outstanding issues.