Rebuild the interface so that the organization had more control over the elements that matter the most.
What did we do?
For the Dutch Ministry of Defence we were hired to be consultants on Identity Access Management (IAM). MoD had challenges that we found incrementally. Over the course of 2 years we worked on a number of cases.
- Build a process and start implementing applications to the IAM tool of MoD so we increase the centralized control on authorisations within the digital landscape. This was as part of a project called IAM 3.0.
- Rebuild the interface (known as IdentityHub) so that the organization had more control over the elements that matter the most.
- Spider in the web / business analysis for migrating complex infrastructure to a new more modern way of working.
The content of this page includes the second point.
IdentityHub and Migration
After the project IAM 3.0, a management decision of MoD was made to allocate the resources of our project to help out with the building block. Whilst we were planning to onboard applications into the existing environment, the existing organisation was struggling to finish a migration/upgrade and keep the functionalities working correctly. Because this was a showstopper for onboarding new applications, all effort was aimed at solving production issues.
The goal of the migration/upgrade was to upgrade to a newer version of IIQ. From 6.4 to > 7.3. and to implement a new custom build user interface to control the application.
Build a futureproof interface that can communicate with an existing (market) application that should remain upgradeable. A big challenge we had here is that when we joined this project, a lot was already built and the people that worked on it had largely left the organization. This made it especially difficult because there were no (written down) functional requirements of the work that had to be done.
To successfully complete this migration/upgrade, we had to get back down to the basics. For us this meant the following:
- Get all the functional requirements clear.
- Build information architecture/wireframes.
- Go over all existing code that wasn't deployed in production.
- Scratch the code that did not match our newly functional requirements.
- Build the new functionality incrementally whilst demonstrating this to the stakeholders on a biweekly basis.
The migration/upgrade had been stuck for quite a while when we joined the team. We ended up deploying a complete version of the application with the new functionality in 25% of the time that the project had lasted.
- SailPoint IIQ
- Angular IO
- Information architecture
- Java programming
- Automated deployments
- Process analysis
- Technical analysis
- Consultancy, business and technical