Jenniffer Alvarez

I managed all activities related to the agile development cycle of the web application. One of the critical elements of my role was risk management, identifying risks in advance, and creating mitigation plans to ensure the project was successful. I also helped with conflict resolution among the engineering team members. As the main point of contact between the product owner and the engineering team, I helped define the requirements and the design of the roadmap.

I managed a team of seven software developers, one quality assurance engineer, and one technical writer. Conflict resolution among the members of the team was an important task that I oversaw. I also led as the main point of contact between the client and the engineering team, managing stakeholders' needs and keeping close communication with all of them. I supervised the project's schedule, roadmap, and overall timeline, ensuring that critical deadlines were completed on time.

I coordinated a training campaign for the entire team of over 2,000 people. I also helped with implementing and releasing a new release management tool to help adopt CI/CD and test-driven development (TDD). I tracked vital metrics to make sure that the adoption was successful.

I analyzed the limitations of the current ticketing system so I could make a case to convince people to move to the new system and avoid resistance as much as possible. I helped with the set up and configuration work that needed to be done before the teams could start using the system. I then designed a campaign to start with the transition. I decided to start with some early adopters based on the volume of tickets and their willingness to adopt the transition. I chose three of the over 30 teams available. Then I moved to a bigger group of teams (over 20 teams). Finally, I moved the last group of people, the resisters. The transition took around eight months, and we were ready with 100% of the teams using the new system by the initial deadline.

I established a process where the requesting team would open a ticket from my team; I would then make an initial analysis and identify local and highly restricted data. Then, I involved the SMEs and owners of each data set to coordinate data retrieval. I then included the security team, who was responsible for the masking of the data. Finally, I involved the team accountable for the storage of the data. I created a post on the company's wiki to know the current process and start a request quickly and efficiently. I built a strong relationship with the security team, the SMEs, and the storage team, so they would prefer to communicate with the team over the wiki post if any of them received a request that didn't come from the standard process. That way, we ensured all appeals followed the standard procedure and provided the data that was transferred securely.