Senior Atlassian Expert

Project Eunomia was a massive project to save one of the most messed up Atlassian platforms I have ever seen. With a background of having multiple Data Center products smashed together with little to no cleaning and with no strategy in any of the products it had created a tangled up mess that barely held together.

In order to save the platform I started by cleaning out hundreds of unused projects. I then moved over to the configurations where I aligned Priority schemas to two main schemas and a handful of extras. I removed hundreds of custom fields and a handful of apps that were not being used, but costed a lot of money. I reviewed 1700+ custom fields, close to a thousand workflows and more than a thousand screens.

I cleaned out hundreds of groups and set up a sync of organization groups from our AD to replace all existing groups. We removed dozens of automations using the old automation system and went over and removed several issue links and resolutions.

I changed dozens of statuses that were using the wrong status type and changed dozens if not hundreds of workflows that were failing to set resolutions on green statuses or worse. We introduced Forms using ProForma to remove hundreds of custom fields that were used just to get information and not for processing the report or otherwise be used beyond the request.

I conducted more than 1000 workshops, sometimes outside my regular working hours as Sinch is an international company. We aligned, improved and customized hundreds of projects to get rid of bad configurations and to optimize ways of working.

Assignment: Design up the new standard setup of Confluence & Jira, configure the systems, train and educate the organization and setup the integration with AD. I also did pre-studies and setup plans for adding portfolio management and test management in the next phase. I supported ITIL processes and integration initiatives as well as different security related topics such as SchremsII and information classifications.

Method / Tools: Jira software cloud, Confluence cloud, Qmetry, Big Picture, Advanced Roadmap, Atlassian Access

Customer Benefits: Provided a solid base for all teams to start from that allowed working cross projects in an easy-to-use setup. Provided 5 group training sessions, each two weeks in length, that gave a good introduction to the systems and the setup from both a theoretic and practical point of view.

My assignment is to set up, configure and design an Atlassian setup as a proof of concept for the new work processes.

Project Heimdall was a massive project where I went through a full security audit for the Atlassian Data Center products Confluence, Jira Software and Jira Service Management. During the audit I mapped out a number of activities such as securing the API's, revise the situation with how groups were being used as that was out of control, document integrations and ensuring that access was configured properly.

The first activity was to kick out everyone from system administration that was not a member of my team. After that I revised all access setting to ensure that the global permissions were set up properly and that the roles were properly defined and used within the permission schemas. I removed several roles and removed almost a hundred permission schemas to align access right to one common setup so that roles became the appropriate way to assign users to a project.

I removed groups from permissions and workflows and removed hundreds of groups that were unused or used the wrong way.

I removed a very poorly designed setup for legal compliancy and redesigned it using Assets and AD groups to ensure legal compliance was enforced without any possibility to override in the Atlassian platform. I also worked with legal and security to ensure that the setup was aligned throughout the organization in sales situation and contract signing processes.

I added Compass and forced all integrations to be listed there by securing the API's and turning off access to anyone that did not have a documented integration. The API's were only accessible through a special SAINT (System Account for INTegration) account that we controlled.

We also reviewed and corrected thousands of configurations in the products and the apps and made sure they were not in risk of a legal or security incident.

I worked with Atlassian to get an overview of all Atlassian products related to Sinch based on the known domain names Sinch own. From the list of 1300+ products I conducted a project to consolidate the many organizations under one Enterprise license and to shut down old and unused Atlassian products.

I used Assets and Confluence for organization and documentation and once the main organizations had been identified I took ownership of the organizations as Org Admin. I worked with the owners of the organizations and with Atlassian to consolidate the organizations into the Sinch Enterprise organization.

This required technical changes to adjust the groups and access settings since all global security configurations on the Organization level was managed by me. The people owning the external organizations were given site admin access as they were responsible for support and daily configurations until the second phase could begin.

I planned the second phase where all sites coming from old organizations would move into the Enterprise platform. This would be the third phase of the Cloud Journey program.

A massive project I single-handedly managed where 3000 users was moving from Data Center to Cloud using a greenfield approach. I configured the cloud platform from scratch by setting up standards for all configurations based on our Atlassian strategies.

I planned the entire project, defined the budget, scheduled the 1400 workshops, created the 300+ projects with standard configurations and set up each project in Confluence where each team managed their cloud journey. I also documented all configurations in assets and in Confluence.

I held 3 workshops every day to guide the users to the new standards and late in the project I added a consultant to help with the workshops. I aligned requirements from the teams to ensure they were built and I aligned the new platform with the many integrations to ensure the platform was secure, compliant and used responsibly.

I set up new processes for handling integration requests and collaboration regarding emails with infra. I set up the integration with our AD together with infra and ensured we had all the processes in place for security and legal compliance.

I planned the rollout activities, prepared for the transition of emails from the old platform to the new for our Jira Service Management teams and set the schedule for moving Confluence spaces to the Cloud.

I also held weekly and later bi-weekly meetings with Atlassian.

Jira tool manager with the task of stabilizing the system and setting up work processes for all teams within H&M. Responsible for several projects including cloud initiatives and coordination with other systems such as ServiceNow. Heavily involved in designing the build processes (requirements, development, design, deploy and test) for the process office. Responsible for the design and implementation of SAFe in Jira and the build processes. Responsible for a small team of Atlassian experts. Supported 400+ teams with Jira questions and training of work processes.

I was brought into the ISS project to help with the maintenance of their Data Center instance. My assignment was to help improve performance and suggest changes towards a more stable platform. During my time as an architect for maintenance, I implemented rate limiting for APIs and also conducted a manual move of Opsgenie to Jira Service Management Operations. I also tried to export old data from Opsgenie, and I built a Python script to scrape as much as possible since Opsgenie is not a very easy product to get data from.

After the summer, as the Data Center platform was stable, I transitioned to leading the Confluence migration preparations. I set up Confluence pages for all spaces and documented content and access, as well as connected the test tasks for each space using automations. I ran the test migrations and documented the outcome for any problems that needed to be addressed. I also wrote a Python script for migrating Draw.io diagrams. This became a bit tricky since there are several types of diagrams, and I had to make fallbacks for my fallback to ensure I captured all scenarios.

This was a very good assignment, and I was treated very well. So well that I got a very nice letter from the team to my manager as my contract ended, praising my contributions.

I often get praise from my customers, but this felt extra good 💙

For Saldo Bank, I acted as the Atlassian Architect, performing the initial platform setup, where I did the following:

• Connect the Atlassian platform with internal access management tools to provide SSO and policy management.

• Secure the API’s using security policies and security functionality in Guard, and set up a process for integrations in the future

• Claiming the customer's domain to control all user accounts and Atlassian product apps connected to it.

• Configure Access and permissions in a standard configuration for the 4 permission levels (Global, Roles, Project, and Security scheme)

• Assign the products to data residency to ensure data is stored properly in the geographical region appropriate for the customer

• Based on customer input, we also help configure the work item hierarchies, Priority schemes, and issue linking to ensure a standardized setup.

In addition to this, I worked with Saldo Bank to configure the platform to their needs, doing the following:

• Workshop with customer teams to understand their business needs

• Define workflows with strategies for standards and scalability

• Define Work Types, work type hierarchies, and request types to fit the work done

• Define Forms and custom fields to avoid performance issues

• Define SLAs to capture internal and external promises of efficiency

• Define the Incident process to ensure an efficient resolution and proper incident management

• Define information architecture in Confluence to help organize information according to best practices.