We provide IT Staff Augmentation Services!

Release Manager Resume

2.00/5 (Submit Your Rating)

SUMMARY

  • My experience appears to concentrate in Information Technology: Configuration, Deployment, Upgrade, & Migrate, with exposure from Business Operations and General Business and Manager.
  • me has over 23 years of work experience, with 17 years of management experience, including a mid - level position.
  • me has worked in several different environments; such as CMMI Level 3, ITIL, and ISSO.
  • me has also worked with several different CM tools in both Agile and Waterfall environments
  • me enjoy multi-tasking and prioritizing among competing commitments and tasks.
  • me am an extremely motivated, self-starter, results-oriented, and driven individual dat can work comfortably in a team environment.
  • me has created and modified several documentations, release schedules, and pushed software versions to different servers.
  • me has worked through teh configuration process from UAT testing through Production.

TECHNICAL SKILLS

  • Serena PVCS (Version Manager
  • Service Manager & Tracker)
  • Serena Dimension
  • ServiceNow
  • Integration
  • Integrator
  • Best Practices
  • Debug
  • Scheduling
  • Scripting
  • Unix Shell
  • Budgets
  • Project Manager (WBS & Project Plan)
  • Rational Suites (Clear Case & Clear Quest)
  • Asset Management - Configuration Management Database (CMDB)
  • Build Management
  • Help Desk
  • IT Infrastructure
  • LINUX
  • Software Configuration (software development kit (SDK)
  • Team Lead
  • Documentation Management (Hummingbird
  • Documentum Enterprise Document Management System (WDK)
  • & Work Process Review)
  • Microsoft Suite (Share Point
  • Visio
  • PowerPoint
  • Excel
  • Word
  • Publisher
  • Visual Studio Team Server and Azure & Access)
  • Subversion
  • ITIL
  • CMMI
  • Maintenance
  • BMC Remedy V7
  • SharePoint administrator
  • JIRA Administrator
  • AWS Beanstalk Administrator
  • Test Case
  • CMS
  • Content Management System
  • Database
  • Embedded Team
  • Salesforce (Defect Tracking)
  • Audit
  • Librarian
  • Systems Engineering
  • Oracle (Oracle 10g
  • Database
  • PL/SQL
  • Oracle Forms and Reports & Data Warehouse)
  • Primavera Project Portfolio Management V5.0
  • Accounting
  • Change Control Board & Change Advisory Board(CAB)
  • IBM WebSphere
  • Mercury Load Runner
  • Data Center
  • Unix
  • Base Application Service Environment (BASE)
  • Putty
  • WinSCP
  • Cygwin
  • Snag It
  • Tortoise SVN
  • CVS source control
  • Eclipse PHP
  • Cruise Control.

PROFESSIONAL EXPERIENCE

Confidential

Release Manager

Responsibilities:

  • Created secure configuration management and release coordination processes (CM/RC), and system documentation. me facilitate teh creation of several documents, which include teh NEA Configuration Management Plan (CMP), NEA Change Management Plan, NEA Implementation Plan, NEA Configuration Management Standard Plan Overview in PowerPoint, and teh NEA Configuration Management Software Migration Overview in Visio. Which is in NEA SharePoint for NEA & NEA ITS department can access.
  • Within my first six months, me was able to updated and implemented new Software Lifecycles Development Process for NEA DevOps team.
  • Facilities weekly Techincal Review Board Meeting or Change Control Board with NEA stakeholder and team lead member.
  • Within SharePoint is where all NEA documentations kept include release notes and other documentations.
  • As SharePoint administrator responsible for overseeing an installation of teh Microsoft SharePoint collaboration and content management platform.
  • Implement new projects in teh configuration tool, which exist in cloud environments, such as Microsoft Azure, Visual Studio Team Server, JIRA, SharePoint, and AWS Beanstalk.
  • Responsible for all NEA change request approval process is documented, evaluated, approved, and communicated regarding teh changes to teh scope, schedule, risk and cost baseline.
  • Responsible for update teh appropriate project documentation to reflect teh new and modify change, track action items, and other relevant information to NEA team promptly.
  • Responsible for identification, evaluation, and estimation of teh levels of risks involved in a situation, their comparison against benchmarks or standards, and determination of an acceptable level of risk.
  • Responsible for update team on any update change or version of documents are in SharePoint, such as action items, outstanding issue, and version changes. By preparing and distribution by email and hard copy to teh team within minutes.
  • Responsible for Software Configuration Management and Continuous Integration which support NEA projects as well as development, lifecycle, maintenance activities daily essential.
  • Work on NEA’ multi-million dollar project, NEA360. My role on dis project requires dat me work with and coordinate nine vendors. As such, me establish release versions, develop milestones, and monitor teh defect tracking system.
  • As JIRA Administrators & Site Administrators, AWS Beanstalk Administrators all project coordinator TEMPhas to come to me to set up new projects and users.
  • Reposinsble for a created new repository for projects in AWS Elastic Beanstalk from subversion, integrated development environment (IDE), JIRA and handle automatically deployment tasks for several projects at one time..monitor teh development lifecycle, use for to build and run you're application.
  • Use AWS Beanstalk and JIRA to create and develop new and unique features for NEA sub-projects dat function under teh umbrella of teh NEA360.
  • Managed day-to-day operational aspects through teh directives of teh Project Manager.
  • Reviewed deliverables for compliance before passing to client or Project Manager.
  • Prepared for engagement reviews and quality assurance procedures.
  • Ensure project documents were complete, current, and stored as required. Performed all work duties and activities in agreement with organization policies and procedures.
  • Develop policies, procedures, and guidelines for program administration.
  • Coordinated with several team player on software releases such as 3 project managers, 10 Application team, 25 Developers, 10 Testing teams, 4 build teams, 6 Embedding Team, 1 Architect Team and 4 Business Analyst.
  • NEA Enterprise Software range from JAVA, C++, Oracle PL/SQL, Oracle Data Warehouse, Oracle 10g and 11g, .NET & Unix Mainframe use Microsoft Visual Studio, Subversion, IBM Rational Suites

Confidential

Configuration Analyst

Responsibilities:

  • Managed day-to-day operational aspects through teh directives of teh Project Manager.
  • Liaises with teh configuration Administrator/Librarian on teh population of teh Configuration Management Data Base (CMDB). Manages asset and CMDB, central libraries, standard codes and data; ensures regular housekeeping of teh asset and CMDB.
  • Uses teh CMDB to facilitate impact assessment for RFCs and to make sure dat implemented changes are as authorized.
  • Reponsible configure teh system in many different ways to address an organization's business needs.
  • Collaborated with GSA and Confidential SACM Team on ServiceNow features to gather solutions which is a need for configuration changes, change management, asset management, and incident team with GSA administrators and developers team assistant.
  • Teh CMDB stores attribute of teh CIs and their relationships with other CIs and asset tag number dat on teh hardware.
  • Responsible for to approach in which teams produce software in short cycles, ensuring teh building, testing, and releasing software faster and more frequently.
  • Responsible for day-to-day operations for HW Asset Management. Monitor and manage all aspects of inventory control, including data analysis, asset capitalization, depreciation schedules and fixed asset disposal write-offs.
  • Maintain implement policies, processes, and procedures for configuration items and assets management.
  • Responsible for created daily and monthly reports dat will indicate any changes in CIs and Asset such as new hardware, raw devices, and existing devices into teh environment for maintenance and break/fix.
  • Configuration Management will operate closely with Change Management to make sure all Request for Change(RFC)has correct and update CIs & Asset.
  • Generate daily, and monthly and quarterly activity reports.
  • CMDB stores attribute of teh CIs and their relationships with Asset Items.
  • Prepared agenda for CCB and CAB meetings also contains change requests dat are classified as SOP’s and third party change requests dat are approved and scheduled for implementation through other scheduling and approval methods. Teh agendas also contain a future schedule of release changes for information to teh boards. Teh agendas are sent out by email two days before teh meeting.
  • Facilitator and meeting minutes are formally documented and disseminated to respective board members no later than one business day after teh after teh conclusion of a board meeting by email and place into SharePoint.
  • Coordinate with teh change submitter and teh communications group for change requests dat will lead to teh temporary loss of services or applications. Reviews change information in totality to ensure alignment of risk, priority, impact, for teh proposed change. Ensure Service Lead approval for teh proposed change TEMPhas been provided.
  • Facilitation of change implementation status from teh respective points of contact for each change and documentation of teh outcome of each change implemented. Development of a monthly maintenance weekend schedule containing CCB and CAB approved change requests as well as regularly scheduled monthly maintenance changes for implementation.
  • As Configuration Analyst Lead is a disciplined process dat provides for teh effective planning, documentation, reviews, approvals, and implementation of organizational changes throughout teh change lifecycle before changes being introduced to teh production environment.
  • Coordinated with several team player on Software Asset Configuration Management such as 2 project managers, 9 Application team, 9 Developers, 6 Assest teams, and 2 Configuation management team.
  • GSA/ Confidential we use AWS ServiceNow ITIL Process.
  • ITIL Methodology.

Confidential

Change Manager

Responsibilities:

  • Responsible for creating and update Remedy change request on an everyday base. Updated BMC Remedy V7 Change Request documentation and Change Request Template from Normal, Emergency, Standard and No Impact. Created AWS Application Lifecycle Management (ALM) reports daily for customers and post to CM and AWS Dev Wiki such as Release Requirements Status, Items/Defect, SIT and CAT points.
  • Provide CM SBM Support, CM/Dev. Wiki when needed. Maintenance of existing and creation of CM Standard Operating Procedures (SOP).
  • Ability to contribute to teh new process documentation for CM Tools and reporting as needed. Support CM Team activities such as dishing out teh source code control system (SVN).
  • Responsible for to approach in which teams produce software in short cycles, ensuring teh building, testing, and releasing software faster and more frequently
  • USPS Enterprise Software range from JAVA, C++, Oracle PL/SQL, Oracle Data Warehouse, Oracle 10g and 11g, .NET. and Remedy.
  • Facilities and scheduled Tuesday and Thursday Configuration Control Board with stakeholder, vendors, and team lead member.
  • Created weekly agendas and meeting minutes and provide to teh team before and after CCB meeting.
  • Facilitator and meeting minutes are formally documented and disseminated to respective board members no later than one business day after teh after teh conclusion of a board meeting by email and place into SharePoint.
  • Coordinate with teh change submitter and teh communications group for change requests dat will lead to teh temporary loss of services or applications. Reviews change information in totality to ensure alignment of risk, priority, impact, for teh proposed change. Ensure Service Lead approval for teh proposed change TEMPhas been provided.
  • Responsible forthe cost or difficulty of implementing an effective countermeasure for teh associated vulnerability exceeds teh expectation of loss.
  • Performed a qualitative or quantitative approach assessment by following best practice methodologies dat project is using.
  • Coordinated with several team player on software releases such as 1 project managers, 50 Application team, 50 Developers, 25 Testing teams, 2 Architect Team and 4 Configuration Management Team.
  • Agile Methodology.

Confidential

Release Manager

Responsibilities:

  • Release Manager manages teh release process end-to-end, from teh planning of teh liberation content through teh actual release deployment to production.
  • Design teh deployment with all layers of teh solutions across teh tiers by established policies. Provide oversight of teh discharge process, including working with resource managers to ensure successful delivery of teh release within scope and character.
  • Ensure all testing, including operational, integration and user acceptance tests completed, all defects addressed, and all service errors contained in teh release were signed off.
  • Develop and communicate detailed release plans and sets delivery expectations with teh appropriate technical teams.
  • Responsible for developing release policy and plan, full implementation roll-out and back-out plans, producing release communication, conducting implementation audits; as well as other release process deliverables.
  • Work with teh QA team to ensure coverage and readiness of test plans, test strategy, high-level test scenarios of teh applications Coordinate a "Go/No Go" from all stakeholders on planned application release before production deployment.
  • Conducts regular post-implementation reviews and presents release metrics to assist with teh evaluation of release quality Identify dependencies, risks and work with teams to resolve or mitigate them Coordination with Infrastructure and Shared Services Update schedules and relevant metrics and dashboard for decision making and track release activities.
  • Responsible forthe cost or difficulty of implementing an effective countermeasure for teh associated vulnerability exceeds teh expectation of loss.
  • Performed a qualitative or quantitative approach assessment by following best practice methodologies dat project is using.
  • Define and communicate management expectations of information security.
  • Ensure consistent information security risk assessment methodologies.
  • Enhance teh organization’s ability to select and apply protection based on teh specific risks and threats affecting an asset.
  • Inform security priorities and planning.
  • Provide basis for measuring information security program efficiency and effectiveness.
  • Facilities and scheduled Tuesday and Thursday Configuration Control Board with stakeholder, vendors, and team lead member.
  • Created weekly agendas and meeting minutes and provide to teh team before and after CCB meeting.
  • Following tools used on dis project was Remedy, Subversion, Cruise Control, ANT scripts, PERL, UNIX, Java, Oracle, and SharePoint C++, Oracle PL/SQL, Oracle Data Warehouse, Oracle 10g and 11g, .NET. & Subversion. Microsoft Vivo and Microsoft project management.
  • Coordinated with several team player on software releases such as 1 project managers, 14 Application team, 25 Developers, 10 Testing teams, 1 Architect Team and 2 Configuration Management Team.
  • Agile Methodology.

Confidential

Release/Configuration Manager

Responsibilities:

  • Produce internally and externally published material such as knowledge briefs, deployment guides, and administrative manuals.
  • Defense Manpower Data Center (DMDC) standards for current build implementations, including version application code for each implementation, creating deployment packages, developing (and implementing, if required) back-out plans, recording and reporting teh status of teh deployed applications.
  • Coordinate teh release of software products with external and internal stakeholders.
  • Works with and under teh direction of teh Project/Technical Managers and teh Defense Manpower Data Center (DMDC) Product Managers.
  • Provides technical leadership on specific integration activities.
  • Facilities and scheduled Wednesday Configuration Control Board with stakeholder, vendors, and team lead member.
  • Created weekly agendas and meeting minutes and provide to teh team before and after CCB meeting.
  • Produces internally and externally published material such as knowledge briefs, deployment guides, and administrate manuals.
  • Ensure consistent information security risk assessment methodologies.
  • Enhance teh organization’s ability to select and apply protection based on teh specific risks and threats affecting an asset.
  • Inform security priorities and planning.
  • Provide basis for measuring information security program efficiency and effectiveness.
  • Following tools used on dis project was Remedy, Subversion, Cruise Control, ANT scripts, PERL, UNIX, Java, Oracle, and SharePoint C++, Oracle PL/SQL, Oracle Data Warehouse, Oracle 10g and 11g, .NET. & Subversion. Microsoft Vivo and Microsoft project management.
  • Coordinated with several team player on software releases such as 1 project managers, 4 Application team, 4 Developers, 2 Testing teams, 1 Architect Team and 1 Configuration Management Team.
  • Agile Methodology.

Confidential

Configuration Manager

Responsibilities:

  • Managed and directed day-to-day activities on technical projects to ensure dat policies and procedures were being followed and dat goals and objectives were being met.
  • Established milestones and monitoring adherence to contract terms and schedules.
  • Maintained software configuration integrity in subversion repository; preparing and packaging release increments to test and production environments.
  • Worked collaboratively with US Forest Service Natural Resource Management to deploy successful release packages into test and production environments.
  • Responsible for weekly software release deployment to all NRM application versions or patch on every Thursday.
  • Facilities and scheduled Wednesday Configuration Control Board with stakeholder, vendors, and team lead member.
  • Compile all teh forms, reports, library, and menu and deployed to NRM UNIX environments. Teh developer will compile teh Java, Dell, and ear/war files and CM will move teh file to NRM UNIX environments.
  • Following tools used on dis project was Remedy, AWS Subversion, Cruise Control, ANT scripts, PERL, UNIX, Java, Oracle, and SharePoint C++, Oracle PL/SQL, Oracle Data Warehouse, Oracle 10g and 11g, .NET, Putty, WinSCP, Cygwin, Snag It, Tortoise SVN, CVS source control, Eclipse PHP, Cruise Control. & Subversion. Microsoft Vivo and Microsoft project management.
  • Coordinated with several team player on software releases such as 1 project managers, 8 Application team, 8 Developers, 6 Testing teams, 1 Architect Team and 1 Configuration Management Team.
  • Waterfall Methodology.

We'd love your feedback!