1. Home
  2. Videos
  3. Mission Possible or How to Implement Automated Identity Lifecycle in a 200 years old Enterprise

Mission Possible or How to Implement Automated Identity Lifecycle in a 200 years old Enterprise

In order to watch this video, you have to log in or create an account, if you don't have one yet.
This video is only available to registered participants of the event.

 Login
 Login with Google   Login with Facebook   Login with Amazon 

Identity Lifecycle automation project in Swedbank lasted for 4 years. During all those years I fulfilled business analyst role in IAM area. I collected requirements, draw process models, and did detailed analysis. I also defined minimum viable scope of the project and drove the team to reach the goal. Finally, I did acceptance testing. I can share key activities for business analyst throughout different phases of the project.
Analysis
* Get descriptions or describe yourself HR-processes, which are related to identity area.
* Get descriptions/explanations of data feeds from HR-systems.
* Describe your needs to HR-system development team, such as future employment changes, deputies etc in advance.
* Trust but verify: ask for example files /data. Perform data analysis to makes sure, that previous descriptions and processes are valid.
* Just acknowledge that “roll-out” of new processes is not one day activity, this can last for multiple months and must be treated and described as a separate process.

Development
* Help developers with clarifying tiny details from stakeholders
* Document the details
* Control the scope and drive team to do correct prioritization
* Discuss alternative solutions to implement same business need

Testing
* Rehearse migration
* Rehearse roll-out
* If testing resource is limited – verify major business cases. Prolong pilot period to see rare business cases in production.

Roll-out
* Define different scopes and roll-out in smaller scopes (to keep incidents queue managed)
* Start roll-out from the process, that has smaller impact on acting employees (In our case we decided to start roll-out with leaver)
* Set up regular meetings with major stakeholders to inform them about changes in the processes. Good if you managed to agree on convenient communication channels (such as chat in Teams) between operational teams to be able to resolve incidents quickly.

Pilot
* Verify not only concrete cases, but also analyze the data.
* Agree on convenient way of communicating issues/bugs/questions to developers.
* Resolve incidents and fix bugs as quickly as possible, so that operating units don’t feel alone with software/data issues.

 

Key takeaways:

 

* Everything is possible but
* Define viable minimum
* Management team must be involved and work for your project. Your project must be a priority for all stakeholders / involved parties
* Start roll-out from the end
* Find a way to analyze your data to make sure, that everything is ok
Ekaterina Silina, Business Analyst, Digital Identity team, Swedbank

Language: English • Duration: 21:09 • Resolution: 1280x720

Learn more about this hybrid event


KuppingerCole PLUS

Get access to the whole body of KC PLUS research including Leadership Compass documents for only €800 a year

Stay Connected

KuppingerCole on social media

How can we help you

Send an inquiry

Call Us +49 211 2370770

Mo – Fr 8:00 – 17:00