IT auditing services
Project - remediation
IT project remediation is a complex process that requires a deep understanding of business processes when the solution doesn't meet the expectations or misalignment.
Frequently, a change in direction is needed to ensure the project deliverables.
Approach
We look at the root cause by understanding the project by taking a targeted approach investigating available options and providing recommendations to the board. These are summarised in an assessment document outlining the way forward.
Real-World pension company scenario - example
This company has legacy infrastructure and software that doesn't conform or comply with current pension legislation. Their flagship software platform uses an auto-generated code engine that generates COBOL and which is now obsolete due to a lack of resources that work in the COBOL space.
The company has taken the approach of migrating to Java using a scrum approach, but they didn't meet the target delivery date for three years running. Therefore, the board requested an external audit to decide if the programme team can deliver the project.
Real-World - conclusion
Our assessment was that this project is extremely complex due to the nature of the technical stack which must be converted for the business to move forward and support its strategic roadmap. There are the following significant risks with the current approach which we outlined in detail to the board:
- Unknown challenges and scope based on the unconverted COBOL programs
- A lack of change control management
- Lack of documentation, planning and governance
- Missing technical architecture governance
These risks can be mitigated by the recommendations in our assessment document, which will give confidence in the direction of the work required and its eventual success. Recommendations listed below:
- Introduce a new test framework which is key to the delivery
- Project planning should not change direction in relation to the roadmap
- More documentation to support the JAVA processes is required
- Technical assurance - we advice an overarching layer of governance approach
Conclusion:
The current approach is tactical rather than strategic – and is characterised by indirection and a lack of defined requirements. Based on my findings, I cannot support the current approach with confidence, as it will not serve the needs of the business. However, there is still an opportunity to move forward based on my recommendations.