TECHNICAL SKILLS:

Operating Systems/ Environments: PC, Mac, Ubuntu, MS - DOS, Windows (all), Eclipse IDE, IntelliJ, JIRA, Confluence, Rally, Git

Tools: Microsoft Remote Desktop, Team Viewer, putty, Apache Tomcat, Firebug, JMeter, J-Unit, MS Office, Evernote, Notepad ++, SVN, Selenium, Selenium Grid, TestNG, Toad for Analysts, SalesForce

PROFESSIONAL EXPERIENCE:

JIRA Administrator

Confidential, Portland, OR

Responsibilities:

• Hired to transfer 6 projects from an on-premise server to an already live JIRA cloud instance. The version of JIRA they were using had not been upgraded in 6 years.
• Hand created each project to be moved from the ground up to facilitate as smooth of a merge as possible. This ultimately prevented a clean backup and restore.
• In charge of installing and linking the “Salesforce & JIRA Cloud Connector” plugin to a Site Reliability Engineering project. Transferred all linkage from the previous plugin to the new one, as the one previously used was not cloud compatible. All Salesforce administration and configuring was self-taught.
• Worked with minimal supervision and coordinated with different teams to define project requirements. Each project was unrelated to the others with unique workflows and custom field configurations.
• Worked to optimize teams existing workflows and to standardize processes. This consisted of identifying unnecessary transitions or fields and removing or fixing the problems areas.
• Maintained numerous VM’s to update the old JIRA server to the current version so that the exports could be migrated to cloud.
• Maintained constant communication with the affected teams throughout the whole process.
• Migration required creation of import configurations and custom URLS for exporting tickets. JIRA limits ticket exports to 1k/migration and some projects had over 7000. Projects were imported 1k at a time.

Atlassian Support Engineer

Confidential, Portland, OR.

Responsibilities:

• Knowledge of the entire Atlassian stack; primarily JIRA and Confluence.
• Project management within JIRA, including scheming, custom fields/screens, permissions, workflows, and notification customization.
• Back-end administration mostly revolving around virtual hosts/guests and Linux/Ubuntu. Including backups, process monitoring.
• Excellent customer-facing skills. Easily able to communicate complicated concepts to individuals of all skill levels.
• Shadowed fellow coworkers on-site at Nike and Intel and was trained to administrate their JIRA systems. Only able to observe and ask questions. No actual contract work as I was laid off before I could be put with those clients.

Confidential, Beaverton, OR

Engagement Manager

Responsibilities:

• Helped to broker a contract between a small company in Portland named Quality Control Services (QCS) and Confidential .
• Worked with the client to elicit their business needs and to detail and plan out the work.
• Created a Statement of Work (SOW) which acted as a supplement to the contract between QCS and Catalyst. This detailed what either side could expect from the other for the duration of the contract and was signed by both parties.
• Established effective and ongoing client communications and providing timely status updates to the customer as well as scheduling and facilitating meetings as needed.
• Ensured that all necessary project resources were available for the developer and that all changes were properly tested and approved.

Scrum Master

Confidential, Portland OR

Responsibilities:

• Maintained the Scrum team's storyboard in Rally alongside the Product Owner.
• Attended two backlog grooming sessions a week to refine and validate story cards and acceptance criteria and prioritization.
• Participated in capacity planning meetings for the team to make sure every person had enough work to do for the sprint.
• Facilitated Sprint Reviews, Retrospectives, and Sprint Planning sessions. Made sure all required persons were invited accordingly and that any changes to the schedule or attendees were communicated as needed.
• Attended a weekly Scrum of Scrums and made known any blockers that the team or I had to other teams or the Project coordinator. All information was detailed in a community One Note and brought up in turn during these meetings.
• Made sure the team stayed on track for delivery of committed story cards throughout the sprint and kept the board updated.
• Attended planning sessions with project managers and business analysts to discuss and architect upcoming solutions which were captured in EPIC cards to later be split into smaller User Story cards
• Recorded sprint metrics for reporting and helped develop a system for tracking defects with QA (burn-down, burn-up charts, and bug tracker spreadsheet).
• Attended UAT hand-off meetings to make sure testers had the information they needed before and after deployment of code and alerted them when builds were ready to be tested.
• Developed a sprint checklist to maintain a consistent sprint structure. This provided a way to keep the team accountable to Cambia’s scrum process.
• Worked with Toad for Analysts during planning sessions for the purpose of Data Mapping. PDM documents came out of these sessions.

Scrum Master

Confidential, Beaverton OR

Responsibilities:

• Developed the scrum process for a Catalyst team working with the Confidential in Washington State.
• Maintained a Scrum Board in JIRA and Confluence, making sure cards had good acceptance criteria, the story is well written and the person who owns the card has no blockers hindering the cards completion.
• Responsible for running scrum meetings and adding all of the resulting artifacts in Confluence for the team to use.
• Facilitated between the developers and the project stakeholders through weekly meetings, sprint planning, backlog refinement and sprint review meetings.
• In charge of the project deployment process for the team: building branches for the 2 environments set up (staging and production) from a git repository.
• Responsible for making sure functionality is properly tested by QA as well as helping with branch testing each sprint.
• Created a broad testing document for manual regression testing.

Developer/SDET

Confidential

Responsibilities:

• Specialized as Software Development Engineer in Test (SDET) for an agile development team.
• Performed QA functions (white box/black box code review, user story adherence) and ran and maintained JMeter tests.
• As Nike was the largest client for Catalyst at the time my training cycle consisted of learning Nike’s stack (Java, Jira, Confluence, JUnit and JMeter)
• Wrote and maintained Selenium, JMeter and JUnit tests for various projects.
• Helped develop training material for Catalyst Tech Leads detailing roles within scrum and the responsibilities they have as per Catalyst policies.

Software Developer

Responsibilities:

• Worked with the Google Web Toolkit creating a program that crawls SVN repositories and gathers and stores information related to software projects and users contributions on a per language basis. This is used on-site at Catalyst for use in the training cycles.
• Developed a back-end web service, written in Java, that served an interface for a challenge based work-out web app where people could log and track their work-outs.
• Created JMeter tests for the “Challenge Engine” described above.
• Directed an open source project that edited JMeter test suites through a command line interface using pre-defined parameters.
• Worked to develop a Selenium training program for new employees based on testing the Nike website interface with Selenium. Used TestNG to run these tests on a remote computer in parallel.