We provide IT Staff Augmentation Services!

Project Qa Lead Resume

4.00/5 (Submit Your Rating)

O Fallon, MO

SUMMARY:

  • I’m a Professional Quality Assurance Project Lead with 21 years of experience in software testing, business process, custom and commercial software application development projects.
  • Strategized and directed all software testing activities including forecasting, estimation, scheduling, procurement, resource & allocation, daily, weekly and monthly metric reporting to project executives, stakeholders and clients.
  • Accountable for management obligations including budgeting, change management, risk identification and constraints of product releases.
  • Successfully committed to numerous projects sustaining reversal of hitherto prevailing negative conditions, process improvement and software development completed within the timeframes and cost estimates.
  • Determined abilities to deploy standard product and development Life Cycle (SDLC) methodologies specifically focused on software quality assurance, project management, business analysis, implementation and migration of software to commercial production releases.
  • I’ve worked with a variety of Project team sizes ranging from 100 - 350 colleagues, utilizing my knowledge and expertise to promote positive interaction between all levels of management, peers and clients motivating any size organization to achieve success.

PROFESSIONAL SKILLS:

  • Reviewed the Project Plan, Technical and Functional Design documentation
  • Composed Test Strategy, Approach and UAT Test Plan
  • Provided Testing Milestones, Deliverables and Tasks
  • Selected, Implemented and Maintenance of Quality Assurance Tools
  • Created and Maintain documentation for Quality Assurance environments, Processes and Procedures
  • Managed the Budget, Forecasting, Schedule and Resource Allocation
  • Prepared Quality Assurance Reports and Presentations
  • Participated in Compliance Auditing
  • Prioritizing Activities in Alignment with Testing Objectives
  • Held Training Meetings with the Testers to Ensure Testing and Defect Reporting Processes are Followed
  • Provided Clear and Concise Feedback to Software Engineers on UAT Test Execution
  • Engaged with the Necessary Functional Groups in Communications and Decisions
  • Reviewed Testing results and Defects to Assess Impact on the Project and Implementation Schedule
  • Primary Point of Communication for Project Leads
  • Developed and Managed the Quality Assurance Testing Matrices
  • Lead Weekly Change Management and Production Training Meetings
  • Attended Weekly Project Team Lead Meetings
  • Attended Stand-Up, Pre-Sprint Demos Planning, Sprint Demo, Sprint Planning, Sprint Planning & Retrospective, Story Elaboration, Technical Grooming and Story Code Review meetings.
  • Reviewed Test Strategy, Approach and UAT Test Plan with the Quality Assurance Teams
  • Studied the Elected Requirements for Gap Analysts with the Quality Assurance and Development teams
  • Executed the Quality Assurance Plan with UAT Testing Teams
  • Provided Input, Overseen and Reviewed Script Writing to ensure Complete Test Coverage
  • Ensured Traceability of Scripts to Business and Functional Requirements
  • Coordinated Assignments for UAT Testing Teams
  • Facilitated Daily Quality Assurance Meetings and Maintained Agenda
  • Supported UAT Teams with testing execution roadblocks
  • Held Daily Defect review meetings with UAT Testing Teams and Development
  • Worked daily with all Project Teams on Development progress and issues
  • Maintained MS Project weekly on UAT Deliverables, Tasks and Time
  • Mentoring and Motivating UAT Teams during difficult/stressful times
  • Attended Stand-Up, Pre-Sprint Demos Planning, Sprint Demo, Sprint Planning, Sprint Planning & Retrospective, Story elaboration, Technical Grooming and Story code Review meetings.
  • Developed and lead the software system testing process, resources and documentation
  • Implemented departmental policies and standard operating procedures as needed to effectively execute the principles and responsibilities of software quality assurance
  • Responsible for identifying testing resources and budgets necessary to perform the functions of quality assurance testing
  • Owned Software Testing Life Cycle (STLC), Reviewed Requirements and Gap Analysis, Design Review, Test Strategy, Test Plan, Test Environment Setup/Maintenance, Test Execution and Test Reporting from Unit, Incremental Integration, Integration, Functional, System, End-to-End, Sanity, Regression, Acceptance, Load, Stress, Performance, Security, Usability, Compatibility, Install/Uninstall Testing using Black or White Box testing
  • Overseen all aspects of quality assurance including establishing metrics, applying industry best practices, developing new tools and processes to ensure quality goals are met
  • Key point of contact for all QA aspects of releases and coordinating QA resources On-Site & Off Shore
  • Assigned testing resources and managed test execution of 54 application/interfaces including ETL (Extract, Transform, Load) SOI (Service Oriented Integration) GIS (Geographic Information System) Mobile (Mainframe OAS/DOJM) ESB (Enterprise Service Bus), IVR (Interactive Voice Response), Web Services WebSphere MQ Stored Proc API Trace, Web Interface, Mobile, AVL (Auto Vehicle Locator (GPS)) and Browser
  • Assisted and Reviewed Test Cases, Requirement Traceability and Executed the Test Plan
  • Lead Daily morning QA Testing Debrief, afternoon Defect Development Review meetings, sent out Testing & Defect Metrics to the Project Team and Stakeholders
  • Communicated Risk Management Weekly to the Project Team and Stakeholders
  • Risk Identification
  • Listing everything that might potentially come up and disrupt the flow of events
  • Execution delay due to design tasks
  • Not enough resources
  • Defects found late in the stage of the cycle or discovered late due to unclear specifications and are time consuming to resolve
  • Scope not completely defined
  • Natural disasters
  • Non-availability of independent test environments and accessibility
  • Testing delay due to new issues
  • Risk Assessment/ Risk Impact Analysis
  • Risk
  • Probability
  • Impact
  • Risk Mitigation
  • Risk
  • Probability
  • Impact
  • Mitigation Plan
  • Ensured the entire team understood what each defect status exactly meant. Also, made sure the defect life cycle is documented
  • Reviewed with each individual his/her responsibility as regards each defect
  • Confirmed enough details are entered in each defect and status change.
  • Avoided defect related requests’ without an appropriate change in the status of the defect in the tool.
  • Managed Daily Defect meeting with Development and UAT Teams

TECHNICAL PROFICIENCIES:

SDLC: Agile, Waterfall, RUP and Spiral Model

Tools: MS FrontPage, MS Project, Office Suite (Word, Excel, Access, PowerPoint, Outlook), Lotus Notes, Project Central, SharePoint 2007 & 2010, Google Docs, Visio, SQL Enterprise and Query Analyzer, Crystal Reports, Clear Quest, DOORS, Rational Requisite Pro, HP Quality Center, Mercury Win Runner, Test Director, Planview, STAMP, Quick Base, Rally/ALM, PL/SQL, SoapUI Pro, Toad, Postman, Advance Rest Client, Selenium, TestNG, Maven 2.2.1, GIT, SourceTree, Tortoise SVN, JIRA, Eclipse Kepler IDE, IntelliJ IDEA, Bamboo, Jenkins, Bitbucket

Languages: VB, C++, HTML, Perl, Pervasive 2000, SQL, XML, ASP.Net, VB Script, Java, MS Access, ADO, FoxPro, Basic and Shell

OS: Windows (95, 98, NT, 2000, 2007, 2008), XP, UNIX, Linux, Mainframe, Android, DOS, Red Hat, MAC OS, Java, SOA and Apache Tomcat

DBMS: Oracle, SQL Server 2003 & 2005, DB2 and MS Access

WORK EXPERIENCE:

Confidential, O’Fallon, MO

Project QA Lead

Responsibilities:

  • Receive notifications related to different events on a card
  • Block a transactions for a particular merchant based on Issuer Id, Merchant Id and ICA
  • Enable Velocity for cumulative limit on unauthenticated transactions
  • Add Non and Recurring Payments to controls
  • Implementing a merchant certification process will be leveraged by multiple services that onboard merchants including, MDES for Merchants (M4M) and Third-Party wallets.
  • Genuine Confidential accepting merchants
  • Obtain the most current and accurate acquirer information for merchants
  • Ensure that the merchant and acquirer (and any service provider in the chain) are DSRP compliant (i.e. capable of handling DSRP data)
  • Decompose the monolithic architecture into separate and distinct products, Merchant, Switch and White Label Wallet
  • Remove the dependency upon PM3 increasing the flexibility to enhance and support newer capabilities for merchants, service providers, and developers in the future

Confidential, Saint Louis, MO

Project QA Lead

Responsibilities:

  • Provide reports that meet business requirements for reporting on team arrangements, team dissolutions and modifications to team arrangements on a semi-annual basis.
  • Provide a systematic process for identifying team relationships on a monthly basis as per business requirements.
  • This process will support other manual / human decision processes around team arrangements.

Confidential, St. Louis, MO

Project QA Lead

Responsibilities:

  • I researched, fixed system configuration and technical issues.
  • I tested Remit applications core processes; Scanning, Extraction, Check Keying and Supplemental Data Entry.
  • Validated DNP (Do Not Process) Rules(Config) by Server, Credit Card Processing, Deposit Cuts, End of Day / Start of Day and Outputs for ACH, EDI, Image Look, Singlepoint, Customer Data Trans, Customer Image Trans, Web, Printing, Faxing and X9.37 DDA and validated Billing Rules for client Billing.
  • I assisted in downstream application testing for Quality and Productivity Statistics, LSTAR, Hogan RPM, Image Look and X9.37 DDA.

Confidential, Baton Rouge, LA

Sr. Quality Assurance Engineer

Responsibilities:

  • In an Agile environment, I was responsible for the design of Test Strategy and implementation of the Test Plan.
  • Overseeing the execution in accordance to the Test Plan specifications for Confidential Medical System (AMS) and Point of Care (POC) application.
  • I carried out procedures to ensure that all web portal functionality and services meet organization standards and UAT requirements based on business specifications and designs.
  • Lead and executed functional testing. I tracked, reported testing statuses, defect and progress on issue resolutions to management.
  • Mentored the QA Engineering Team and ensured my work exceeded the project performance, reliability and quality goals.

Confidential, Irvine, CA

Project QA Lead

Responsibilities:

  • Over time, as Confidential grow, we converted the MS Access billing application to a SQL back-end to support the companies growing needs.
  • As more time pasted Confidential bought a child company called OCIS, a company that built a Confidential Billing application.
  • Confidential and OCIS sold the Confidential Billing application to many Confidential companies. It was agreed, with this purchase Confidential and OCIS will work side-by-side with the tasks of data clean-up, data conversion testing and all QA phases automated and manual testing.
  • This meant documenting all current processes and external client needs. Once this deliverable was completed we needed to document all Confidential 's business requirements to convert successfully. I worked closely with development and unit testing to confirm once QA receiving the schedule code release good progress was made to meet hard dead-line.

We'd love your feedback!