Scrum Master/Business Analyst/Consultant

At DUO (part of the Ministry of Education, Culture and Science) I act as senior business analyst/ deputy Product Owner within the scrum teams for status funding education. The project has complex structures with a client in The Hague, three Scrum teams with team members from Groningen and The Hague in each team and customers in other parts of the country (the schools and providers of school administration systems). The systems developed have numerous connections to internal and external systems, such as BRP (population register), student administration systems and various Education Registry's.

As a business analyst, I am responsible, among other things, for fine-tuning user stories and making Use Cases, generating YAML/JSON files, WSDL, XSD and propagate chosen solutions within the teams, the clients and the customers in the country. The biggest problem with this implementation is the hard deadline due to the passed law. Problems with the implementation where often strange and illogical laws, regulations or expert decisions, often intended to solve historical (no longer existing) problems.

As deputy product owner, I support the product owner in carrying out team-related tasks, such as maintaining and prioritizing the backlog, leading planning, and preparing sprint reports. Since the product owner was away for a long time due to an accident shortly after I started, I took on all of the product owner's tasks from November 2020 to August 2021. After his return, the internal tasks remained with me.

After a tender at DUO, large parts of the DEVOPS teams were replaced, which led to the teams functioning poorly. In the period July 2022 to Oktober 2023, I took the role Scrum Master to get the teams back on track. After this was successful, the role was brought back to the teams.

Within the project, several decisions were needed to determine how status assignment would work in the future. This included which techniques to use where (Java, Powercenter, MagicDraw, RMS, no Blueriq), how to adjust processes to make them simpler, how to do the implementations, etc. For all these points, I wrote a leading advice together with the PO or another business analyst.

At AMAG, I worked as a senior business analyst on the project to renew the Dealer Workbench (DWB), the application where the dealers order the vehicles. The new application uses SAP Fiori. For the new DWB, I collected the requirements, structured processes, created use cases and helped test the application. DWB went live on January 1st.

At the Dutch tax authorities (de Belastingdienst) I acted as a business analyst in the project "Uitfasering DAS" (phasing out the digital archive) and later as an architect for the archive systems. DAS was the old digital archive of the tax authorities. In the first phase I researched how the archive could be migrated (what is efficient, what is realistic, what other options are there), what software needs to be adapted and/or created for this and what processes need to be set up for this. To this end I described the designs, the non-functional requirements and the mapping of old metadata to new metadata. I also created a plan for the migration process to be followed. The new archive (GDA) is based on IBM FileNet. One of the biggest challenges was the very limited knowledge of DAS at the tax authorities, the metadata of DAS not matching the metadata of GDA, missing descriptions of the interfaces and the enormous amount of data that had to be migrated from one system to another while daily production continued as usual. The functioning migration software on the side of the current archive (DAS) and the functioning broker for converting production and migration flows were put into production. However, the newly developed GDA system experienced significant delays, which meant that the migration was stopped for the time being.

After the migration was stopped, I took on the role of solution architect for the older archives. For this, I created various Solution Architectures for various changes and was the point of contact for the archive systems. In addition, together with another architect from business operations, I advised CFD (facility services, owner of the central archive) on how GDA should be set up. GDA is the generic document and archive system that should also support case-oriented work.