I was given the opportunity to return to Stauder Technologies, where I had been previously employed for nearly 15 years. I am a member of the development team that primarily supports the JECLⓡ product. I played a key role in the design and development of the initial version of this product many years ago, and I'm excited to be able to combine my newly refined full-stack web skills with my past experiences at Stauder Technologies to help the team and the organization with their current efforts.

Serving as a software developer on the company's IT team.Developed a system to help manage vehicle movement for one of the organization's releasing companies. The system included a new Andoird Application and website/backend server written in CakePHP.Developed a new single-page application web app (using Angular) for managing various aspects associated with the dashboard cameras installed in our transport trucks. Continuing to add additional capabilities to the system to evaluate the possibility of having it be a successor to the organization's primary terminal-based management system.Worked on the initial portion of a company-wide project to streamline the driver dispatch system. I worked with a small team to design a new system that will provide a way to dispatch drivers online at any location. This system will increase efficiency by streamlining the dispatch process. The system (an Angular web app with a Node.JS backend) will be used by all drives as well as home-office personnel, and will likely serve as a framework for redesigning other systems in the organization. Sadly, I decided to pursue other opportunities before the completion of this effort, but I feel privileged to have been chosen to work on this important effort.

Scrum Product Owner for a new product called Palaroo. This is a separate project/role from the ones I currently hold at Stauder Technologies.Palaroo is a web and mobile app designed to help event organizers communicate more information to attendees of outdoor festivals and events. Opposed to building one-off apps as most of our competitors do, our app provides access to an event directory so that users can learn about events that match their interests. Some of the key capabilities of the product include a detailed interactive map, event schedule, and push notifications to attendees. Research on the project was completed during the 2014 timeframe. Actual development on the mobile apps and web dashboard began in Feb 2015, and our initial release was in June 2015.My current role on the project is Product Owner. Following the typical responsibilities of a Product Owner, my primary responsibility is to manage the backlog for the team. In addition to this, I also help to work with our marketing team, as well as the company president to manage priorities and desires. This effort has given me a chance to expand my skills by managing a project that is much different than efforts I've been involved with in the past. Typically I have worked on government contracted efforts that are fairly well defined. Since this project is an internally-funded commercial application, it has given me the opportunity to learn how to deal with challenges that simply don't exist in military/government efforts.

As a result of a minor organizational change to help streamline our efforts, in Feb 2015 my responsibilities shifted to a focus on research and development efforts, as well as larger highly-strategic activities. This includes the responsibility to direct all IRAD and CRAD efforts in the organization. As part of this change, I assumed the Product Owner role for two Scrum Teams who were responsible for the tasks associated with the IRAD, CRAD and strategic efforts.Along with the standard Product Owner responsibilities for the teams, I work close with the Marketing and Business Development Teams to help flush out potential and upcoming efforts that would transition to one of the teams. I work with these groups and the president/CEO to help prioritize tasks as we refine our strategic direction. This role also includes a significant amount of coordination and interaction with other teams in the organization, especially those who utilized the results of our efforts, and in situations when R&D efforts transition to production efforts.The primary focus for one of the teams is the JECL product, which I've been involved with numerous times in the past. The other team works on numerous products, but as of late they largely focus on a new effort we started called Palaroo. While in this role, I've had the opportunity to refine skills used in the past, such as being able to simultaneously approach efforts from both the low-level technical perspective as well as a high-level business perspective. This role also involves coordination with multiple individuals who often have opposing desires/goals, helping everyone to reach a common solution that benefits everyone.

As a result of a minor organization change in Feb 2015, I was given the additional role of Lead Engineer. In this role, I evaluate engineering & management processes and tools to balance quality/desirability for our customers, cost effectiveness for the company and overall satisfaction for the employees.In past efforts at Stauder Technologies, I have been involved in the development and execution of our software engineering and development processes, as well as processes in other areas such as project management. This included the responsibility to transition our organization from a traditional "waterfall" methodology to an Agile methodology using the Scrum framework. Once the transition to Scrum had taken place, I was transitioned to other efforts that needed attention. After a period of time, we found that this left a gap in the organization because those using our Scrum methodology had no one to go to for support and guidance. In this new role, I am responsible for understanding the successes and challenges of our Scrum teams in an effort to help improve our utilization of this methodology. I essentially serve as the Scrum Coach, attending retrospective meetings and participating in other team-related efforts. While it's not perfect, I am a firm believer in the Scrum methodology and the benefits that it can provide. This role has given me an opportunity to learn more about the challenges that teams face on a day-to-day basis and achieve a better understanding about how to improve things for not only the teams but the entire organization.

Scrum Product Owner for the second major iteration of an earlier-developed communications library called the Joint Effect Coordination Link, which is a suite of communication tools primarily designed for the military that allows for digital communications between airborne and ground systems using legacy/fielded combat network radios. This product is incorporated with internal products developed by Stauder Technologies as well as external products. Roles include typical Product Owner responsibilities such as coordination with customers / stakeholders to ensure that the Product Backlog is populated and ranked to match the current desires, ensuring that the team has the information needed to complete their sprint, etc. Simultaneous second role... Project Manager for an in-house developed communications hub that provides a bridge between legacy military equipment and modern commercial handheld devices. This effort includes the development of a custom system board, custom tactical modem, in-house developed power supply, and a custom enclosure that meets IP68 standards. Roles include the management of the schedule, costs, risks, and various other aspects of the effort.

Lead a small group that was tasked with the goal to transition the company from its Project Management and Software Development Processes which were very waterfall-ish to ones that followed the Agile Methodology and Scrum Framework. Once the planning was complete and the new Agile "processes" were officially adopted by the organization, it was my responsibility to work with the various teams/programs to help with the transition and address issues/challenges along the way. As problems were identified, I would work with others in the organization to identify solutions that both met the organization's needs and adhered to the framework specified by Scrum and the general principles of Agile.

Selected as one of a handful of individuals to become part of a team that would develop one of the first Android-based targeting and Forward Air Controller tools for the U.S. Marine Corps. Worked with a small team to take an extensive set of existing capabilities (mostly written in C++) from existing products and make them available for use in various Android applications via Google's Native Development Kit (NDK). We then created/enhanced Android applications that provided the same capabilities as systems which were typically much larger and heavier for the user to carry. This effort paved the way for smaller/lighter equipment for the end-user, utilizing commercial equipment.The above effort included numerous areas of the end product, including a new capability that allowed for the automatic detection of tactical radios. Before this effort, users of previous products were required to specify the type of military radio connected to the system, because each radio requires unique API considerations. This manual approach often led to incorrectly configured systems, which hampered communications. For this product, I implemented an approach that allowed the system to automatically detect when a radio was physically connected. The software would identify the type of radio connected, and then automatically configure the system to work with that particular radio. What once required deliberate actions from the users became totally automated. The user could simply plug in a radio, and the back-end software would notify the client that a radio had been connected and would handle the unique requirements for that radio. To our knowledge, this is the first military product to implement such a feature. Worked on a product called "Contrive" which helped to automatic the mission planning process for Forward Air Controllers. Information that was typically entered manually became a simple scan of a QR code, greatly reducing the likelihood of incorrectly entered information.

The communications suite that was developed during the 2001-2005 timeframe was revamped by a small software development team in order to add numerous enhancements. Once complete, I was responsible for managing the changes to that product. This required coordination between the various projects in the organization to ensure that needed features were implemented based on their timing needs.

As the lead Software Architect, I lead, managed and coordinated the software efforts for our USMC targeting system called StrikeLink. This included technical responsibilities regarding how features were implemented and integrated into our existing product. Lead the Change Control Board (CCB) for our targeting system to manage both the technical and business aspects of the product. These meetings decided what would and would not make it into the final product.This effort requires an enormous amount of coordination, not only between internal engineers and management, but also with Marine Corps Systems Command.Converted the organization from SourceSafe to Subversion for our software configuration management system. Installed and configured Atlassian's JIRA as a replacement for our issue tracking system. Migrated the team from our previous in-house system to JIRA, and became one of the primary administrators of JIRA.Installed and configured Atlassian's Confluence as a way to provide an on-line approach for managing our files and other various information. Lead the small Recruiting Team that was responsible for recruiting and hiring new software engineers.

Continued the work of the owner of Stauder Technologies to refine and enhance the digital communications capabilities of the ACASS product, which provided Forward Air Controllers digital communications between it and the U.S Marines' Harrier (AV-8B). This was THE FIRST application to ever digitally communicate with that aircraft. Led a 2-person team to create a completely new version of our digital communications suite that would extend our digital communications capabilities from just the Harrier to include the Hornet (F-18) aircraft. The resulting product is one of the first products to successfully communicate digitally with that aircraft. That capability provided significant usability and safety benefits to the U.S. Marine Corps Forward Air Controllers, because it eliminated the need to verbally communicate coordinates and other data. Migrated the existing communications software library from a modem that was specific to a single computer to one that was developed by Raytheon, which was (and still is) usable in a wide variety of systems. Participated in many exercises with the USMC Forward Air Controllers as one of the original FAC systems. This effort helped us to refine the capabilities to best meet their needs. Created a way for our system to automatically learn the typically-complicated network addressing scheme of systems on the tactical network. Prior to this, both the aircraft and ground system users would have to manually enter addressing information. With Boeing, we devised a way to completely automate the process. Created a prototype app that was THE FIRST to exchange digital imagery between the F-18 and a USMC (or any military) ground system. This prototype led to the definition of an imagery exchange standard that still exists today.

Senior Programmer/Analyst for the Information Systems Investment Representative Recruiting & Hiring Team.Supported the Investment Representative Laptop Training System - Tests taken on the laptops by potential Investment Representatives were submitted to headquarters electronically to an OS/2 machine for processing. The scores were then uploaded hourly to the mainframe training system.Participated in the development and support of a large market analysis system written mostly in C++ using Motif for the interface. The system also included a replication system to keep mainframe and Oracle databases in-sync to within one second. The system also utilized a large geographic database for displaying existing and future branch office locations.Converted the above application from using ESRI's MAP LIBRARIAN and ArcStorm scripts to ESRI's Spatial Database Engine (SDE), which allowed the geographic data to be stored in Oracle. Developed a method for updating the geographic data quarterly, which also synced up the business data to match any geographic changes. Also automated a process to create plots for metropolitan statistical areas automatically, requiring the user to only draw a rectangle of the desired area of interest, which then generating all of the needed information.Created a algorithm for generating annotated map information, allowing it to be rendered more quickly.Participated in the redesign of the U.S. online Information Representative Application section of the www.jonesopportunity.com website, which was used as as a tool to recruit new Investment Representatives. Using HTML template files and numerous Perl scripts, the site saved information as the application was being filled out, allowing the user to complete part of the (lengthy) application and then return later to finish it. Once submitted, the application was automatically merged with a PDF file using Adobe FDF forms and sent to a printer in the Recruiting Department for immediate review.