SUMMARY

• Seeking a full - time position wif a stable organization, which involves my interests in the field of management of computer technology and/or software configuration management.
• A position that will further my noledge, yet remain challenging and self-rewarding, while providing opportunities for career growth.

PROFESSIONAL EXPERIENCE

Confidential

Software Configuration Manager

Responsibilities:

• Established the CM department at the Nashville Biometrics office. When I arrived there were no CM or release processes. In two months I was able to migrate the entire source code base from CVS to SVN, establish a software versioning scheme, automate the entire baseline/build/release process for 3 projects, and provide traceability and reproducibility of all baselines.
• Administrator of the CM Toolset. The tools include: SVN, TeamCity, YouTrack, VersionOne, Artifactory, Patch Manager, InstallShield, and Fortify.
• Wrote, tested, and maintained all scripts use to drive the automation engine (TeamCity). I ran the automation on batch, ANT, and shell/bash scripts.
• Gained a vast noledge about the Linux Ubuntu and Red Hat operating systems, as well as Apache Tomcat Web Server.
• Managed all CM related tasks for all projects in the local offices. Managed a team of 2 CM engineers and responsible for 6 projects, including the company’s highest priority project.
• The main tasks I am responsible for are: Establishing software and configuration baselines, maintaining/tracking and reproducing those baselines, automation of critical development and CM processes to ensure timely delivery to internal and external customers, defining and enforcing all CM related processes, ensuring CM is compliant wif all contractual standards, administering all CM tools, providing CM metrics through audits, and supporting development/QA in any way possible.

Confidential

Software Configuration Management /Software Service Analyst IV

Responsibilities:

• Created, facilitated, and maintained the CM procedures and tasks.
• Helped configure and maintain the automation engine, Electric Commander, which was used to automate all CM related tasks. These tasks include automated software builds, software deploys, incremental versioning, proper baselining at the project and individual item level, source code updates from SVN, logging, emails, and status change events.
• Wrote, tested, and maintained all the ANT scripts necessary to drive Electric Commander.
• Supported the project from both a managerial and technical CM standpoint. Managerial tasks include working wif multiple teams to coordinate project efforts, project planning and estimates, support/planning calls wif the customer, and providing direction for the team. Technical tasks included ANT scripting, script testing, automation development and maintenance, and status/triage calls wif the customer and other internal development teams.

Confidential

Software Configuration Management /Software Analyst

Responsibilities:

• SCM and build management lead for 60 products across 4 project divisions.
• Managed the source repository (Visual Source Safe and Subversion) for all these projects, including defining baselines, version tracking, and providing traceability for all scheduled deliverables and post-release patches.
• Created, controlled, and maintained all of the build processes, scripts, and Microsoft installers (using InstallShield) for the 60 projects I maintained.
• Responsible for the release cycle of each project I maintained. This involves build of source code, packaging of the deliverables, and timely delivery to testing and QA according to product schedules.
• To accommodate the massive amount of projects and simultaneous release schedules, I implemented a continuous integration methodology. This build process, by use of programmatic automation, decreased the release schedule by approximately 60%, while increasing the quality of the products delivered to testing and QA by 30%.
• Chaired and was elected to many "Common Initiatives" designed to streamline development processes across segmented divisions wifin the organization. Examples include: Common Setup Initiative, Common Source Control Procedures, Development Environment Virtualization, Best Practices for Post Release Patching, Software Quality Procedures, and Procedures for Software Baselines and Version Control.
• Member of the internal ISO audit team. Conducted many internal ISO audits to ensure compliance and maintain certification.

Confidential

Software Configuration Management Engineer (SCME)

Responsibilities:

• Identified and maintained baselines of all software and software work products.
• Conducted various audits to maintain the integrity of software products.
• Identified and controlled all project Configuration Items and conducted configuration status accounting for Configuration Items.
• Wrote Standard Operating Procedures and Work Instructions to be compliant wif AS 9100, ISO 9000, and IEEE 12207.
• TEMPEffectively used and managed the configuration tool PVCS VM, and the configuration release tool AGILE.
• Tracked and managed software change requests using PVCS Tracker.