Report for October 2019

Report Date
October 2019

Work has been progressing on the fixing the issues on the reports for both Space and Maintenance.  A review of the project costs and issues around the project has been discussed with the Project sponsor. A further detailed report will be completed over the next couple of weeks  for the Business Sponsor of the project

Maintenance:

The work to fix the data model was completed in early October. Further system testing was carried out and this identified a further five issues. Three of these issues were around the access schema  and the other two were around the quality of the data.  Work has commenced to fix these issues and is targeted for the 12th of November. The formatting  for the reports have been completed for all 14 reports.

Space

The remaining work for Space was small  tweaks and these have now been completed and have been implemented in the Test environment. A couple of changes which have been asked for to make it easier to search for data have been put on hold as these changes  are considered nice to have as the user has a workaround.

Next Steps

Complete the development work on the Maintenance reports. A meeting has been scheduled with the Business to discuss the User Acceptance Testing strategy and  the issues with the data that has been encountered during system testing. Once the Acceptance Testing Strategy has been agreed then the User Testing dates will be agreed with the Business.

Produce a report for the Business Sponsor and then to get approval for a new baseline of the project for both costs and timeline.

Issues

  • The environments (dev, test and live ) Archibus that are being used for the testing are out of date and do not reflect the current Live environment. This makes the testing more difficult for the developers.
  • The scope of the project has been extended as the BRD was written 1.5 years ago and the interpretation of the requirements has not been controlled.
  • This project is over budget, has increased its scope and also the timeline will need to be extended due to  complex issues found during testing
  • The developers  have found further problems in the Maintenance reports after the data schema was updated. System testing has found more issues which is taking time to resolve.  Over the last 7 weeks the developers have been involved in rounds of testing before releasing this back to the customer. 

 

Summary

The project is taking significantly longer due to issues found during testing. It is clear that there was never any integration testing performed at the beginning of the Project and when the first User Acceptance Testing was conducted a number of issues were found.   These issues are mainly being found  in the ETL layer which is when we are picking up data from Archibus and transferring this across to the Enterprise Data Warehouse. In addition to this there was no formal project management on this project for a number of months which has meant that the project has not been managed and this has impacted the timeline and scope of the project.

The  Developers are now performing in depth testing to ensure that all the issues are rectified before being  user acceptance tested by the customer. The impact of this is that the cost of the project has significantly overrun and this is now being reviewed with the Business Sponsor. The current position is that we are 128 days over budget. The timeline will need to be extended to accommodate another run of  User Acceptance Testing which is planned for December. A new plan and budget will be available in the next couple of weeks for formal sign off by the sponsor.

 

 

 

 

Project Status
RAG Status
Time
RED
Cost
RED
Scope
RED
Overall
RED
RAG Commentary
Time and Cost: This project has extended multiple times due to technical difficulties in establishing the EDW solution and subsequent issues with failures in testing of reports, There are also technical issues with data synchronisation. These technical issues have taken significantly longer to address than expected. Project Manager is working with ISG Technical teams to progress these issues. Time and Cost extensions are the subject of discussions with Estate, who query the value and cost Scope: The business requirement was written 18 months ago and the business has moved on significantly. The agreed reports are therefore of less value than expected at the outset. A scope review is recommended, in addition to a more Agile delivery approach to delivery Next steps: Complete work with ISG Development to address technical issues and manage the next phase of User Acceptance Testing. Consider scope review with Estates. Provide report for Estates sponsor and agree funding model
Change Status
Time
Significant
Cost
Significant
Scope
Significant
Overall
Significant
Has formal escalation taken place?
Yes
Escalated to
Project Sponsor
Change Commentary
From the initial baseline there has been significant changes to all areas of the project. PICCL to be raised to WIS after estimates for completion of project have been formalised.
Activity
Approved budget
349.0 days
Activity this month
27.8 days
Activity this year
54.5 days
Activity to date
477.1 days
Estimate to complete current year
80.0 days
Estimate to complete future years
0.0 days

Project Info

Project
Estates Strategic Reporting - Space & Maintenance Mgmt
Code
EST109
Programme
Estates Systems & Technology Maintenance (EST)
Management Office
ISG PMO
Project Manager
Josephine McDonald
Project Sponsor
Karen Adamson
Current Stage
Close
Status
Closed
Project Classification
Grow
Start Date
02-Oct-2017
Planning Date
06-Oct-2017
Delivery Date
26-Jun-2020
Close Date
31-Jul-2020
Programme Priority
3
Overall Priority
Higher
Category
Discretionary