SUMMARY

• Goal - oriented, analytical and responsive INFORMATION SYSTEMS / JUNIOR PROJECT MANAGER professional with a proven history of success.
• Creative and persistent problem solver who thrives on challenges, excels under pressure and gets the job done.
• Confident, energetic and flexible team player who possesses excellent interpersonal and communication skills.
• Quietly assertive / firm but fair leader and coach, organized and thorough planner, and diplomatic negotiator dealing effectively across all levels of the organization.
• Accustomed to a fast pace and multiple projects, fulfills priorities and meets deadlines while maintaining a strong business focus, delivering high quality systems and outstanding user satisfaction when managing complicated projects.

PROFESSIONAL EXPERIENCE

Project Coordinator/ Consultant

Confidential

Responsibilities:

• Analyze and monitored production processes which involved using COBOL,DB2,SQL and JCL
• Result: SLA were met within the contractual guidelines
• Utilized CA-7/11 to monitor, schedule, run batch jobs and correct abends
• Result: Batch processes met their SLA completion times

Project Coordinator/Mainframe Tester

Confidential

Responsibilities:

• Oversee software release packages which included testing these software release packages to ensure we successfully met the scope of these project releases.
• Result: SLA initiatives and promoting software releases achieved a 95% success rate when promoted to production
• Made sure test nodes were not accessing production nodes across the testing environment
• Result: Reduced the amount of reruns that was done.
• Had numerous classes for offshore personnel and onshore personnel to train them in CA7,mainframe technology and Confidential infrastructure
• Result: Onshore and Offshore personnel were able to start doing mainframe and client server testing which helped to reduced the amount of over time
• Utilized pie charts and histograms in meetings to explain various project scope results
• Result: Management was always up to date with the project scope and status
• Tested software packages before they went into production utilizing COBOL,DB2,JCL and CA7
• Result: Reduced the amount of reruns that had occurred
• Utilized Confidential Project Plan and Earned Value Management techniques to monitor the project Progress and performance.
• Result: Projects timelines were successful 90% of the time
• Used estimate at completion to forecast the budget being utilized for each project.
• Result: Projects budgets were within the budget guidelines without using management reserves

Junior Project Manager / Environment Support Analyst

Responsibilities:

• Responsible for on-line system availability to meet all our service level agreements supporting 2,000+ users from a batch and on-line perspective.
• Matrix manage 4 professionals and report to the Team Lead.
• To achieve Disaster Recovery discipline, reviewed Confidential DRP and our local DRPs.
• Then prepared a combined plan and presented it to senior management.
• Result: recommendation accepted, funded and implemented; appointed to manage the unified plan.
• To make sure all the DR participants understood our Recovery Time Objective, Recovery
• Point Object and Project Scope I did a presentation concerning these subject matters utilizing
• Confidential Visio.
• Result: All participants understood how long we had to recover our application
• Data, the window we needed to do it by and the reason we needed to be successful.
• To insure our Project Scope was met I utilized Confidential Project instead of
• Confidential Word. Result: Managed and met all timelines by their appropriate due date that had to do with the Project life cycle.
• Our infrastructure documentation that had to do with accessing data and resource management was located in several areas.
• All this information was consolidated utilizing Sharepoint.
• Result: Created a centralized area where all critical infrastructure information was stored and retrieved.
• In order to perform calculations on data used to assist in trend analysis I utilized Confidential Excel.
• Result: Provided the necessary documentation to management to show what the risks involved.
• To insure that all files were backed up, conceived, developed and implemented a new strategy which automatically backed up any new files that were created.
• Result: eliminated all time spent backing up files; freed manpower to work on critical issues.
• To allow db2 files to always be accessible, conceived, developed and implemented a new process which monitored the db2 file size.
• Result: prevented our application infrastructure from ever being down for any length of time.
• In preparation for my vacation, developed a comprehensive Disaster Recovery Program and provided a daily, one hour classroom to my peers for a solid month.
• Result: successful test was conducted during my absence which met all SLA requirements.
• To reduce the amount of uncertainty surrounding our Disaster Recovery test, as Lead on the test, gathered all relevant staff, both locally and from throughout the country, and walked everybody including Confidential management, local infrastructure support and end users through the Disaster Recovery Plan.
• Result: achieved a successful test every year
• The IT function lacked formal documentation regarding identified problems on each shift.
• Conceived and implemented an issue management, ITIL methodology to record all problems utilizing Confidential access.
• Result: cut errors by 40%; management convinced of the need to purchase additional software.
• To meet our software release due dates, created a formal series of one-on-one meetings to review tasks to be accomplished.
• Result: tasks completed 12% sooner.
• To reduce overtime, analyzed and then identified administrative activities that could be reviewed in our formal weekly meetings.
• Result: eliminated one formal weekly meeting and saved 6 man hours without any reduction in productivity.
• During our QA testing, needed a way to backup all our data in a timely manner.
• Used existing utility to backup and capture all of our data.
• Result: able to retest our data doing sysstem and unit test more frequently; achieved 20% success rate increase going live with no problems.
• While doing a major conversion project, needed to come up with a way to test our converted files.
• Developed a process using our scheduling tool in a test structure.
• Result: saved over $30,000 and eliminated the need to purchase outside software.
• Because our space was being over used this constantly caused production problems, created a batch job to manually archive files to free up space on our volumes.
• Result:; prevented people from getting up in the middle of the night to fix these issues; cut production problems by 50%.