BRIDGETT L. REID
Frederick, MD 21703
***********@*****.***
301-***-**** cell
Current Department of Energy (DOE) Public Trust
Past DOD Secret Clearance
SUMMARY
Possesses over 29 years of Configuration Management (CM) experience and 4 years of Release Management (RM) experience in federal government contracts. Exposure has included both technical and managerial aspects of CM. Strong in being able to adapt and excel in the face of changing program and customer requirements. Well-rounded in both the CM and RM fields.
EDUCATION
University of Wisconsin - Platteville
Platteville, WI
Master of Science in Criminal Justice
December 2016
University of Mary Washington
Fredericksburg, VA
Bachelor of Science in Business Administration
May 1994
Configuration Management/Release Management Related Skills
CM
oAgile
oScrum
oWaterfall
oManaging multiple baselines
oCode branching
oSoftware builds
oVersion control
oMedia generation
oConfiguration audits
oConfiguration audit reports
oMultiple build platforms
oMultiple source control tools
oCM process improvement
oSoftware development life cycle
oManaging/Directing CM team members
oCustomer support
oConfiguration status reporting
oMaintaining CM metrics
oWriting CM tool transition plans
oWriting CM Plans
oSubversion
oGit
oGitHub
oRational Configuration Manager, Quality Manager, and Requirements Manager
oRational ClearCase
oRational ClearQuest
oRational RequisitePro
oUNIX/Linux
RM
oChange Advisory Board (CAB) activities
oChange Control Board (CCB) activities
oLeading Release meetings
oTracking User Stories for Releases
oRelease and Deployment metrics
oManaging Normal, Standard, and Emergency Change Requests
oManaging Release Content
oServiceNow
oMicrosoft Suite
oSharePoint
oProject and Issue Tracker (PIT)
PROFESSIONAL EXPERIENCE
Edgewater Federal Solutions
November 2019 – Present
Release Manager
Reason for Departure: Client Reduction in Funding
Supports the DOE’s Energy Information Administration (EIA) Applications Development and Maintenance (ADAM) team as the Release Manager.
Manages the team’s two regular monthly maintenance releases and each emergency and standard release as they occur. Serves as the main point of contact to ensure the release takes place on time, the correct tickets are deployed, the necessary people are at the deployment, that the testing is completed with a status of Pass, and that the client is satisfied with the results of the deployed product.
All releases are managed in ServiceNow via a Release Record (RR) and a Change Request (CR). This is one of the official records of what was deployed, and links are created between the RR and the CR to show stories, incidents, defects, enhancements, scrum tasks, and demands. Ensures all documentation is attached to the CR, all approvals are received, notes are entered, and that the CR and RR are closed in a timely manner.
Attends the Pre-CAB and CAB meetings to present and ensure approval of the team’s normal type CRs. This involves detailed planning since there is a required timeline for presentation and approval before work can be accomplished. Fast tracks any Emergency CRs through the emergency CAB and maintains client approval for any Standard CRs.
The detailed contents of each release (files deployed, release plans, approvals, testing results, etc.) is maintained on the team’s SharePoint site for others to access as needed. Keeps a detailed inventory of all stories, incidents, defects, enhancements, and demands to assist team members with historical records.
Serves as a backup for the Technical Lead for daily Scrum calls and weekly status reports. Ensures that the team on-call list is maintained and distributed in a timely manner each week.
ProSphere
September 2015 – June 2019
Team Lead/Configuration Manager
Reason for Departure: Contract end in June 2019
Supporting the COMS Project as a Team Lead
Supported the Chemotherapy Ordering Management System (COMS) project as the team lead. Helped guide the project on a day-to-day basis by managing customer expectations, the progress of the technical team, and required reporting.
Ensured that all deliverables were completed accurately and submitted to the customer on time. This included the Bi-weekly Status Report, the Contractor Project Management Plan, and the Veteran Integrated Process (VIP) Documentation. Completed and delivered any ProSphere related documents such as the T4 reports, past performance write-ups, and subcontractor evaluations. Ensured that subcontractors were monitored for their work and that they were sending correct invoices to ProSphere properly and in a timely manner.
Communicated with the VA customer daily as the face of ProSphere. Answered their questions, acted on their requests, and kept them apprised of team progress. Held weekly standing meetings with the VA customer and the team such as Sprint Planning, Scrum, Risk Review, and Sprint Reviews.
Ensured that the technical team was progressing, had what they needed both hardware and software wise to accomplish their jobs, answered questions, offered guidance, and raised/resolved any issues that needed addressing. Led the Bi-weekly Team Meeting that provided a standing time for the team to discuss anything company related or that they felt should not have included the customer. Wrote and provided each team member with their yearly performance review. Touched on strengths, weaknesses, and learned how to better assist the employee in their career development.
Supporting the VAPE Project as a Configuration Manager
Supported the VA by serving as the Configuration Manager for the Veteran Authorization and Preferences Enhancements (VAPE) project. Ensuring that the project’s Rational IBM repository was maintained and setup for each individual Build (release) during the project’s lifespan which included creating a specific folder structure, multiple sets of Rational tasks, links between the tasks, and verifying linkage for the project’s requirements and the project’s testing activities within the Rational repository.
Responsible for managing project Change Requests and conducting the project’s Configuration Control Board. Facilitated a bi-monthly Change and Configuration Management meeting when needed.
Other responsibilities included conducting configuration audit reports for each Build, submitting and tracking access requests for individuals who needed access to VAPE’s Rational repository, ensuring that code-in-flight submissions were completed, assisting project team members with Rational questions and issues, entering an Informational Patch Description into FORUM for each Build, and maintaining and submitting CM related deliverables on a monthly basis for customer delivery.
Columbus Technologies
March 2015 – September 2015
Data and Metrics Analysis
Reason for Departure: Job dissatisfaction
Supported NASA on the Geostationary Operational Environmental Satellite – R Series Ground Segment Project as a Metrics Analyst. Helped create advanced Microsoft Excel formulas and graphs that captured and displayed software development performance metrics and status on a weekly basis for multiple meetings. Graphs such as bar charts, pie charts, line charts, alligator charts, and trend charts were used all of which were automated based on data retrieved from multiple Microsoft ClearQuest databases. A total of about eighteen graphs were produced each week. Helped interpret the graphs to determine weekly performance such as how many Work Requests were opened, placed into analysis, placed into test, closed, placed on hold, etc.
Helped support the multiple meetings that these graphs were used for. This included meeting announcements, minutes, presentations during the meetings, and evaluating the outcome of the meetings.
The Cabezon Group
August 2014 – March 2015
Configuration Manager
Reason for Departure: Contract End in June 2015
Supported the Veteran’s Administration as the Configuration Manager for the Research Administrative Management System (RAMS).
Created the change and configuration management plans for RAMS and ensured that the team followed the procedures. From these plans, created individual process documents.
Set up two source code repositories for the project called Stash and Rational Team Concert. Ensured that the source code and documents for the project were controlled, versioned, and baselined and made sure that all team members had the appropriate level of access to the artifacts.
Supported deployments to the Enterprise Operations environments as needed. This included packaging the necessary code, creating the request for change orders (RFCOs) and obtaining the installation/deployment guide from developers. Continued to support the installation activities as needed.
Delivered monthly updates to the change and configuration management plans to the customer as well as a monthly status report to Booz Allen Hamilton, the prime contractor.
ProSphere
December 2013 – August 2014
Configuration Manager
Reason for Departure: Contract End in September 2014
Supported the Veteran’s Administration (VA) by serving as the Configuration Manager in the development of five new software product innovations: the Mental Health eScreening System, the Traumatic Brain Injury Clinical Decision Support System, the Chemotherapy Ordering and Management System, the Alert Watch and Response Engine, and the Automated Radiology Toolset. These five new innovations were to enhance medical services provided to Veterans by the VA.
Helped develop a configuration management plan and a change management plan for each of the five innovations. Attended many weekly meetings to monitor the progress of each innovation and to look at them from a CM/IV&V point of view. Data gathering, analyzing, communication, and giving project direction was critical.
Functioned as technical editor for various documents related to the innovations. Ensured all information was accurate, formatting was correct, and that the documents were delivered to the VA customer in a timely fashion.
Computer World Services
December 2012 – December 2013
Configuration Manager
Reason for Departure: Contract End in December 2013
Supported the Defense Information Systems Agency (DISA) at Fort Meade, MD by providing configuration management services for the Defense Information Systems Network (DISN).
Served as the CM point of contact for the entire NS251 branch. The main responsibility was to identify and track RFWs (Requests for Work) for the branch and ensure that each RFW was broken down into one or multiple specific RFCs (Requests for Change). After this took place, was responsible for tracking those RFCs from inception to closure and providing status whenever required.
Responsible for assisting the NS251 Branch Head in researching all new RFWs for the weekly RFW review meeting, guiding the meeting, capturing the outcome of discussions, vetting each RFW to the assigned government leads, and updating the respective SharePoint data. At this point, tracking of the RFWs (and their RFCs) began.
After the RFCs were created, assigned to Tier 3 engineers, and completed, responsibility continued with sending the resulting implementation plan and test report to the affected theaters for implementation at the site. Theaters are dispersed throughout the United States, Europe, and Asia. Resolved any problems or vetted them to the appropriate Tier 3 engineer. Ensured that all necessary system access at the various theaters was achieved for the Tier 3 engineers.
Exelis
April 2010 – December 2012
CM Analyst
Reason for Departure: Long Commute
Worked on the ITT Exelis SENSOR (System Engineering and Sustainment Integrator) contract in Dahlgren, VA. The SENSOR contract supports the Air Force Space Command and the U.S. Strategic Command. Provides CM support to the Mission Processing System (MPS) portion of the Space Fence.
Duties included capturing developers’ code, placing it in the CM library and running software builds to ensure that the code will build properly. After generating these executables, placed them on a test network (TNET) for the test group to execute their test scripts. At the end of all official testing, installed executables and other environment and database files to the production system to be used in real-time.
Maintained the CM library through labeling and generating and verifying library reports to ensure library integrity. Kept a detailed logbook explaining all changes or activity associated with the library.
Began the configuration audit at the end of release. Scheduled the audit, verified that all files and documentation were present and in the correct locations for the audit, generated all media to be reviewed during the audit, created and populated all Unix directories that were needed for the audit, created and distributed the audit agenda and check sheets to the meeting participants, and chaired and briefed the audit to the customer and fellow coworkers.
For configuration status accounting, maintained the discrepancy report (DR) database, the standard change form (SCF) database, and a separate spreadsheet for Dahlgren’s assigned DRs and SCFs.