At Lockheed Martin I serve on a DevOps team supporting our program. In that role, I work to define development and testing processes for the program and assist in updating tools and processes for the future. My responsibilities include:- Pipeline definition and creation- Development and delivery of training materials for new processes and tools- Automation of metrics collection and reporting- Administration of key software development and project management tools

As a Project Engineer, I was responsible for coordinating status and execution of the SPARO-20 and SPARO-90. I served as the Scrum Master for the Engineering department and guided PDW in the launch and execution of operating in the Scrum framework. As the resident expert in Scrum/Agile principles I coached the engineering teams on how and why to operate within a Scrum environment and the value that could be realized by doing so.To assist in the transition to Scrum I also designed and implemented a new JIRA structure for the company. This involved designing new issue workflows and issue structures so that the JIRA tool could better serve our needs. I also evaluated and configured a third party tool for integrating JIRA with MS Project so that we could align our overall project schedules with the day to day work being done by the engineers.

As a Release Train Engineer I was responsible for the planning and execution of a Program Increment (PI) for my Agile Release Train (ART). Working with teams and individuals across three continents, I worked with Product Management and Systems Architecture to create and refine the product backlog for each PI, plan the backlog items during PI planning, and then monitor and assist in the execution of the PI plan. During each PI, I coordinated with the teams to determine the status of their plan and report that status to the rest of the ART and to upper management. I also worked with teams to remove impediments to their plan and drive improvement across the ART.

As a Release Manager I was responsible for the successful planning and execution of a release cycle for the Mosaic Cloud Platform (MCP) product. Elements of a successful release included resolution of all critical bugs, completion of all planned features, completion of the required testing for the product, and completion of required customer documentation. During my tenure as Release Manager I worked to improve the management of these elements to ensure a smoother and more predictable release cycle. Improvements made included the creation of an automated tool to generate product Release Notes, a rotating bug Triage team responsibility, and numerous graphical views for tracking bug status.

My teammate and I were responsible for developing a commercialization plan for a product currently in development at The University of Alabama. In December, we pitched our plan to investors at UA's Innovation day.

Four work terms at Adtran: Fall 2012, Summer 2013, Spring 2014, and Summer 2015.In my first term I worked in the Product Qualification division. I was responsible for performing application and feature testing on the NetVanta 7100 product and performing troubleshooting to try and identify the source of any issues or bugs that were discovered. I also wrote a few simple Python scripts to automate some of the tasks I had to perform, such as backing up the unit configurations.For my second term, I worked with Hardware Team 1. I was mainly responsible for performing various DVT tests on the TA 1148V board, particularly relating to multitude of clock signals on the board. Jitter measurements were performed on the signals to verify their consistency for proper board operation. I also performed some basic power sequencing testing on the board, verifying that the correct boot up sequence was executed upon initial power up of the board.My third term was spent working with Hardware Team 3. My main responsibilities were performing general testing, such as temperature testing, on an in-development product. Additionally, I performed several modifications to the PCBs for testing purposes and also built four "terminator"​ testing devices to each terminate 24 phone lines at once (simulating an "off-hook"​ scenario).In my fourth term at Adtran I worked in the Product Management group. My main responsibility was developing a Sales Database to provide engineers access to sales information for products they worked on so they could see how their work impacted Adtran's bottom line. Over the course of the project, I met with several engineering managers to receive feedback on what they would like to see from the project and I also met with the interim CFO to receive approval for the sales metrics made available. Ultimately, the project was implemented as a monthly PDF report that would be emailed to each engineer and contain sales information for products they requested.