Jim Mcintyre Email and Phone Number

QA Test Lead with PM responsibilities.

Doing gap analysis on current POS and back office system, against prospective replacement.Requirements gathering and documentation, done in requirement gathering sessions, by analyzing a sandbox environment provided for the RFP, and by interviewing the CEO, SME's, and other key stakeholders.Business Process analysis, and redesign. Done through stakeholder interviews, and discovery sessions.Working with Vendor on technical and integration details.

• Worked on a safety-focused dashboard with metrics that help people in the field work safely, pulling data from SAP HANA, which surfaced data from various 3rd party systems. This required learning HANA, and how data flows between the systems.• Responsible for requirements elicitation through meetings with the Business Representatives, Designer, and development team. Maintaining these relationships was vital to the team’s success.• Business and technical requirements were written in Jira stories for consumption by the development and QA team.• I Created a user story template and defined the Definition of Ready. Prior to this story were often vague single lines, or were overly detailed, prescriptive, and difficult to follow.• Worked closely with UX/UI Designer to brainstorm and create mockups for use by the development and QA team. Initial story details and wireframes were created by me prior to these sessions.• Created process flow charts, technical diagrams, a role matrix and other artifacts for the development team.• Worked closely with the developers and QA as I had to learn the product quickly to provide value to the team.• Filled in the Product Owner role while the role was vacant, 1 month into joining the team.• Answered questions, provided insight and guidance on requirements, and technical questions.• Empowered the team by returning agency to their roles. This was done by writing the stories in a way that described a problem for them to solve. Leaving the solution up to them.• Lead requirement gathering, story refinement, story estimation, and other such sessions.• I handled the backlog prioritization and management with the Scrum Master and Project Manager.• I joined another team at Nutrien. My responsibilities included training their team in using Jira, creating a story and documentation process, coaching their Project Manager in Scrum, and advising my Lead on challenges faced by the team.

• Worked on a medium-sized agile software development team, as 1 of 5 QAs with standard Scrum test process.• Responsible for leading the data migration process in QA. This involves analyzing import files, loading them into the database, analyzing the data in the database, and validating the data on the front end. • Also responsible for front end, back end (API), data, and some automated testing using SpecFlow and Postman.• Using my previous experience and analyzing the team's strengths, I helped improve the team's story writing and Scrum process. By doing this, I assisted the team in enhancing their skills and delivering better stories to the development team. Some examples of simplifying work include: - Writing concise and clear acceptance criteria. - Using Jira templates with distinct sections to make reading and writing stories more predictable. - Recommending mid-sprint reviews to decide which tasks will be finished by the end of the sprint.• Worked directly with Business Analyst, UI Designer, and Product Owner to clarify stories prior to and during development cycles.• Help the development team by diagnosing and resolving software and business rule issues. Also, log the results as bugs in Jira.

• Worked on small agile squad (team) developing microservice software using the rapid deployment or continuous integration software development methodology• Role’s primary focus is creating automation test scripts using SoapUI to test acceptance criteria on user stories, and logging defects where there are issues or discrepancies• Completed test scripts are stored in a BitBucket repository and loaded into Jenkins to be executed each time a new build is run against the QA and UAT environments• Testing is done using the Data Driven testing methodology, where test steps in SoapUI are kept as simple as possible, and all test data is stored in a database or excel spreadsheet, which allows for rapid upkeep and execution• Role is heavy on data analysis and data creationLearning and applying API automation required a lot of trial and error to determine best way to approach specific test scenarios and issues that arise as the software becomes more complex

• Worked directly with Business Stakeholders, Executives, Product Owners, Subject Matter Experts, and outside Vendors to gather Requirements • Used Business Requirements to create User Stories that were consumed by the Development and Quality Assurance team members • Investigated possible business and software solutions, and provided guidance and feedback to the Business on what was best for what the Business needed to accomplish • While building stories, kept the overall picture and direction of the Business in mind to minimize tech debt, while also ensuring developers weren’t overbuilding or building functionality that wasn’t needed • Answered questions and provided feedback or guidance to development and QA team members to help clarify what the Business was asking for • Facilitated meeting with outside stakeholders • Led requirements gathering and road mapping sessions • Used communication skills to explain the same concepts to the Business and Development teams, using language each team could understand • Maintained weekly Product Owner meeting to give updates on the current sprint, and to talk about future stories• Met weekly with SCRUM master to organize backlog, and talk about the current processes and how they could be improved

• Worked on small agile iterative team, turning out large pieces of functionality in 2 week sprints• Worked with little to no Business Requirements, which required extensive problem solving, investigation, and conversations with Developers and Business members to ensure what was built is what was asked for • Second QA hired at the company; instrumental in developing the QA process, created QA documentation and SOP, advised on testing tools, built training material, and consulted on the overall company quality strategy • Acted as QA Lead for a time until I transitioned to a Business Analyst role • Due to working for a small Fintech startup, I filled and provided support for duties outside of the QA role. • Contributed to requirement and sprint planning sessions • Experience with API testing using POSTMAN, to test endpoints that were waiting for their front end components • Provided Business team members with guidance to help navigate the development process, and translated developer speak to business speak

• Worked with medium to large sized project teams, including the business and multiple outside vendors from Atlanta, Austin, and Toronto• Worked on several Salesforce projects, including a web portal with a content management back end system, as well as a google map integrated site for new hire onboarding with mobile components• Created and executed test cases based on the statement of work provided by the vendors, as well as User Stories created by the Business Analyst• Worked on 3 small Salesforce projects, handling all the testing activities• Worked with many business representatives to learn the various systems being tested.• Worked with outside vendors on cross company testing, problem solving, defect management, and requirements gathering• Worked on small projects with only a handful of people to deliver quick updates to applications and services, with the goal of rapid deployment to the business.• Built test plans, collected data, interviewed content and application experts in order to build requirements, and to ensure quality when delivering these small initiatives• Oversaw functional testing and UAT on small projects, with quality and turnaround time in mind• Worked with data provided by various sources within Husky, to determine the impact of system changes to the business and support staff• Coordinated with project managers to ensure testing results met project milestone dates, and outstanding defects were prioritized for future iterations. At times advising the PM that the quality of the software was lacking, and more development and testing time was needed• Often worked on three or more projects at once. Time management and prioritization was needed in order to ensure all work was completed on time• Built strong relationships and friendships with employees within IS and the business• Was involved in several initiatives within the QA team to help build the QA practice towards a more efficient and effective model

• Worked independently and in a team to create test cases in HP Quality Center, often times requiring an inventive solution to overcome road blocks• Managed and directed the daily operation of application testers; offering advice, answering questions, and responding when issues occurred• Responsible for learning the tools and applications applicable to fulfilling my role as a test lead, often times on my own through research or trial and error• Offered advice on how best to proceed on a project based on my knowledge of the testing process, requirements, and time restraints• Created test plans; detailing what needed to be tested, time frame for testing, and organizing testers and acquiring personnel• Led testing on project that required synchronized testing between the City of Calgary, and the Calgary Police Service.• Worked closely with software developers, and business representatives to ensure a quality product was being developed, and followed what the business envisioned.• Led daily testing scrums to keep business representative, Project Manager, and testing team up to date on the progress of testing, and any issues that were found from the prior day of testing.

• Worked independently to investigate, analyze and troubleshoot computer software and hardware problems as they arose with teachers and students at all grade levels. Made decisions as to what needed to be fixed and what could not, to help minimize the down time for students and teachers• Used working knowledge of different computer operating systems, hardware configurations, and network infrastructures to properly diagnose and repair hardware and software issues• Required excellent people skills, in order to build trust and relationships with teachers and students