Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Capital One: Bridging the Gap Between Quality Engineering and Product Management [webinar]


Published on

** Full recording: **

Learn how leading global bank Capital One is successfully bridging the gap between quality engineering and product management – with a quality-first mindset!

Have you ever thought about how you can continuously enhance and improve customer experience? In today's hyper-competitive environment -- you should!

Competing apps and services are just a click away, which means quality cannot be an empty promise to your customers -- it must be fully engrained into your products, your software, your entire Dev-Test-DevOps processes -- but how can you help create this "quality-first" environment in your organization?

Recently, Evan Wiley has transitioned from quality engineering to product management, and concluded that a mature agile organisation can effectively blend the two roles -- in order to guarantee the continuous release of superior software and quality products.

This change can be effectively done when you have done the following: colleagues who are ready to grow their own skills past their current roles, product management is valued at your organisation, and product managers are willing to learn technical skills related to enhancing customer experience with their own products.

In this webinar, Evan discussed the following topics:
* What is Quality Engineering?
* Which is More Important? Quality vs. Quantity
* How to Cross-train Product Managers with Quality Engineers
* Introducing Quality Engineers to Product Management

Published in: Software
  • Be the first to comment

  • Be the first to like this

Capital One: Bridging the Gap Between Quality Engineering and Product Management [webinar]

  1. 1. Introducing Quality Engineering to Product Management Evan Wiley Senior Product Manager at Capital One
  2. 2. Introduction About Myself ● Quality Engineer for six years at Capital One. ● Started product management around six months. ● Walking dog Gatsby the golden and listening to podcasts
  3. 3. Agenda ● Overview of Quality Engineering ● Cross train product management and quality engineering ● Cross training quality engineering with product management
  4. 4. Why I chose this topic? ● Engineering culture. ● Commercial Card Tech – quality engineer - product manager ○ Empathy Interviews
  5. 5. What is Quality Engineering? ● Quality Engineering is the discipline of finding the bugs within functional products early and often! ● Work encompassing quality engineering: ○ Manual vs. Automation ○ Production Testing ○ Test Case Design ○ Test Execution ○ Penetration Testing ○ Accessibility Testing ● ^^^ Work always changes across organizations!
  6. 6. What is Product Management? ● Empathy interviews with customers that give pain points of the application. ○ Driving themes based upon each interview ● Voice of the customer ● KPIs that measure the results of the product.
  7. 7. Quality Over Quantity ● Users want products that do what they want ● Transparency to the quality engineering process ● Bringing quality engineers into the product fold allows for high quality ● Delivering an exceptional experience to our end users ● Giving product new skill sets that enable an overall enhanced experience
  8. 8. Cross Train Product Managers with Quality Engineers ● Bringing both disciplines together will raise the bar for our end customers ● Bridging skill gaps: product managers will become more technical and quality engineers more insights given to the end users!
  9. 9. Introducing Quality Engineers to Product Management ● Invite Quality Engineers to empathy interviews ● Allow them to have discussions on future roadmaps ● Usability testing involvement with design, product, quality engineers, and end users. ● The more quality engineers are invited to product meetings, the more insights will be given to team members.
  10. 10. Demo ● Walkthrough of Gherkin scenarios (Given, When, Then) ● Walkthrough of visual validations
  11. 11. Gherkin Example Scenario: Validating the look and feel of the Google Search page Given I am on the Google home page When I enter a search for “product management” Then I will see the look and feel for the Google results page
  12. 12. Utilization of Applitools Visual Validation ● Use of screenshots with Applitools for visual validation. ● Use of manual testing skillset.
  13. 13. Company Culture ● Ties back to tenents within own organization. ○ *We value quality over velocity.* Good engineering doesn't happen overnight. Prioritizing delivery over engineering excellence will be a highly considered and documented decision.
  14. 14. Recap of Introducing Quality Engineering and Product Management ● Recap of Quality Engineering role ● Quality versus quantity in delivering value to the enterprise. ● Cross training enhances skills to both disciplines. ● Gherkin and Selenium IDE demo ● Company culture
  15. 15. Reap the Rewards!