top of page

Software Quality

2016 - 2021

Software Quality Manager

IMG_4368.JPG
manual%20vs%20automation_edited.png
Manual to Automated Testing

Using my technical background, I developed a plan to integrate automated testing into our team. As our organization grows, we aim to deliver quality products faster.

Previously, frequent software releases left insufficient time for adequate test coverage and quality.

 

My strategy addresses this issue by enhancing our testing capabilities.

View the journey I led to automated testing!

Business Achievement
Quality with Speed to Market

Led the transition from manual to automated testing across all business areas supported by Software Quality, integrating it into development release pipelines for CI/CD.

Proposed converting 12 contractors to direct hires, saving Wegmans over $500k annually and supporting the growth of automated testing.

Career Goals Achieved

Strategic

 

Planning

 
Created a strategic plan to move automation into the IT department.
 
The plan included:
  • Educated the team on automation skills

  • Integrated QA into software development teams

  • Collaborated with HR to define new roles for automation support

  • Worked with IT to incorporate continuous testing into the release pipeline

  • Established new standards, best practices, and processes for automated testing

  • Set metrics for ongoing quality improvement

  • Developed a rollout plan for automated testing in IT-supported areas

  • Identified and executed a cost-saving opportunity, saving over $500k annually by bringing automation skills in-house

  • Expanded the team from 7 to 25 members to meet business needs

  • Restructured the team to accommodate increased personnel

Managing

 

Change

  • Frequent feedback meetings were held to ensure the process was working or needed to shift

  • Regular meetings with team members provided support through skills training

  • Frequent check-ins ensured adherence to standards and processes

  • Collaboration with development integrated the defined process into release pipelines

  • Updated management on the state of changes.

  • Held feedback meetings to assess and adjust the process

Leading

 

Continuous

 

Improvement

  • Integrated team into development for continuous support

  • Established processes, standards, and guidelines for automated testing

  • Identified tools, languages, and frameworks for automation in release pipelines

 

Influencing

 
 
  • Gained teams buy-in to shift
  • Transitioned the team from project support to embedded development, ensuring ongoing assistance

  • Established processes, standards, and best practices for automated testing

  • Selected tools, languages, and frameworks to automate release pipelines

  • Integrated the team into development for continuous support

bottom of page