Half-Day Tutorials

Double your learning experience with half-day tutorials. Tuesday is “two’s”-day. Choose two tutorials from ten opportunities to learn from the best.

Connecting Better with Customers and Employees for Improved Results

Jennifer Bonine

Have you ever felt the disconnect between your desired result and the requirements you have given to your employees or customers? Or been in a performance review where the majority of time was spent discussing your need to improve your communication skills or results? If you have ever wondered what your core communication competencies are and how to build on and improve them, Jennifer Bonine shares a toolkit to help you do just that. This toolkit includes a personal assessment of your communication competencies and strategies such as mind maps to improve communication and connectedness. Join Jennifer as she explores a set of eight dimensions of successful communicators , provides suggestions on how you can improve competencies that are not in your core set of strengths, and describes techniques for leveraging and building on your strengths. These tools can help you become a more effective and valued leader in your organization. Exercises help you gain an understanding of yourself and strive for balanced leadership through recognition of both your strengths and your “development opportunities.”Learning Objectives:

  • Effective communication strategies to connect teams
  • Activities to enhance connectedness of the team
  • Understanding and removing your blind spots

Tutorial Outline:

  • Connectedness
    • What is connectedness
    • Why is it important for employees and customers
    • Activities to enhance connectedness
  • Communication
    • Bridging communication gaps
    • Leveraging visuals and pictures to communicate messages
    • Four different communication styles
    • Eight dimensions of successful communication

A Whole New Level: Transforming and Scaling Agile Teams

Susan Brockley

It is one thing to say you are “Agile”; it is another thing to say you have consistently adopted and implemented it across your organization. Yet, industry surveys show that companies that master Agile and DevOps adoption see up to 60% higher revenue and profit growth! (…and who wouldn’t want to be a part of that???)

In this tutorial you will examine ways to enhance your Agile adoption from many perspectives – from team members to executives. Through experiential learning you will discover how to motivate your teams to “be Agile” rather than “do Agile”. You will also learn how to begin scaling your organization and the traps and pitfalls to avoid along the way. Finally, you’ll better understand the role you play as a quality assurance professional in your company’s Agile transformation journey.

Learning Objectives:

  • Understand the difference between “doing Agile” and “being Agile” and why that is important to mastering Agile adoption
  • Discover tips on how to transform and quickly stabilize your Agile teams so that scaling is possible
  • Determine the triggers for scaling Agile teams
  • Learn how to choose an appropriate scaling approach
  • Understand how a mix of Scrum and Kanban teams influence the scaling process
  • Enhance your role as a quality professional in your company’s Agile transformation

Tutorial Outline:

  • “Doing” vs. “Being” Agile
    • Mindset, Values, Principles, and Practices
    • How the wrong focus can lead to very different adoption results
    • How organizational structure can hinder Agile adoption
  • Establishing Predictability and Cadence on Agile Teams
    • Engaging Agile Coaches
    • Holding Immersive Launches
    • Writing Guardrails and Guidelines
    • Supporting Agile Champions – grass-roots, organizational groups, and executives
    • Promoting Teams with Success Stories
    • Setting Realistic Expectations
  • Factors that can Trigger Scaling Discussions
    • Dependencies between Teams
    • Product Releases Involving Multiple Teams
    • Specialty / Niche Services (e.g. UX/UI, Database Administrators, Architects)
    • Enabling technologies
  • An Overview of Scaling Approaches and Pro’s / Con’s of Each
    • Large Scale Scrum (LeSS)
    • Scrum of Scrums (SoS)
    • Disciplined Agile Delivery (DaD)
    • Scaled Agile Framework (SAFe)
  • Scaling your Organization with a Mix of Scrum and Kanban Teams
    • Sprints vs. Cycles
    • Pulled work vs. Planned Work
    • Bridging the Differences
  • The Quality Professional’s Role in an Agile Transformation
    • The Flight Attendant
    • The Team Player
    • The Sports Announcer
    • The Scientist

Do you speak DevTestOps? Your 3Cs Journey into Continuous Testing, Quality, & Delivery

Sara Joseph
Are you ready to learn how to immerse yourself into the sights and sounds of the DevTestOps culture? With today’s rapid release cycles and shift left approaches, it is essential for quality professionals to understand their seat in the DevTestOps transformation. However, do we know how to speak the language of DevTestOps so we can walk the talk? The 3Cs is your grammar guide. Allow for Continuous Testing to provide Continuous Quality by ensuring requirements are met and stable systems perform during Continuous Delivery.

Join Sara to learn how to influentially speak to your development and operations teams advocating and measuring quality when deploying individual units with the efficiency of a service-based architecture. By using proper templates and checklists, your test execution will have the ability to scale up or down as your release cycle fluctuates. Sara will teach problem solving skills, test automation fundamentals, and cultural know-how to increase your fluency when speaking ‘DevTestOps’ with your peers and leadership. By observing case studies and workshop simulations, you will learn the different dialects of this space and integrate new vocabulary into your everyday DevTestOps experiences.


Learning Objectives

  • What is DevTestOps: Development, Testing, Operations
  • What are the 3Cs?: Continuous Testing, Continuous Quality, and Continuous Delivery
  • DevTestOps Cultural Experience: Articulation of the DevTestOps language and behaviors


Tutorial Outline:

  • Getting Started
    • What is DevTestOps
    • What are the 3Cs
    • Vocabulary
  • Problem Solving Techniques
    • ‘Think Test First’
    • Scaling testing activities
    • Testing assets
    • Addressing short development lifecycles


  • Automation fundamentals
    • Role of automation in DevTestOps
    • Translating manual tests to automated scripts
  • Building Culture Know-How
    • Measuring activities
    • Manifesto case study
    • Experience simulation
  • Family of Ops
    • ArchOps
    • BizDevOps
    • DataOps
    • DevSecOps

Mobile Visual Testing: Uphill Battle Of Mobile Visual Regression

Dmitry Vinnik

There are many types of testing that companies need to perform in order to have confidence in their product: security testing, integration testing, system testing, performance testing, and more. Often Mobile developers rely on frameworks like Appium, or Robotium to ensure that end-to-end flows of their applications work. However, in the Mobile domain, Visual Testing is essential as mobile devices differ drastically in capabilities, display dimensions and operating systems.Visual regression testing targets specific areas of visual concepts like layouts, responsive design, graphics, and CSS. Because modern mobile applications are built as both hybrid and native applications, there is no way to scale this sort of testing using manual resources. To accomplish this requires Visual Test Automation which should be a crucial piece of your testing stack.

In Dmitry’s tutorial, the class will learn about major Visual Testing Frameworks targeting both responsive web applications and native mobile applications.


Learning objectives:

  • Visual Testing: What, Why, How and When
  • Visual Testing in Practice: Visual Test Pyramid
  • Choosing the right Visual Testing Tool for Your Team

Tutorial Outline:

  • Visual Testing Overview
    • Motivation
    • Value
    • Limitation
  • Visual Test Pyramid Overview
    • CSS/DOM Unit Tests Overview
    • Visual Component Tests Overview
    • E2E Page Tests Overview
  • CSS/DOM Unit Tests
    • Motivation
    • Value
    • Challenges
  • Visual Component Tests
    • Motivation
    • Value
    • Challenges
  • E2E Page Tests
    • Motivation
    • Value
    • Challenges

Software Quality Metrics For Agile

Phillip Lew

When implementing software quality metrics, we need to first understand the purpose of the metric, who will be using it, and what decisions will be made based on it. Will the metric illustrate the level of quality in software products, or drive towards a specific objective? QA managers typically want to deliver productivity metrics to management while management may want to see metrics that support customer or user satisfaction or cost related (ROI) initiatives. With Agile development methods, we often lose sight that our primary objective is the same, quality. Many organizations are myopic on the objective of velocity. However, velocity means little without quality. You need to define quality for your organization through an agile looking glass with intermediate metrics that lead to both quality and velocity objectives. Join this tutorial to learn how to develop and implement software metrics with actions toward improving both quality and velocity. You will gain insight on how to develop and use metrics within an Agile framework that can be used throughout your development and QA organization. More importantly, you will be able to answer the key questions of your stakeholders and get them to stand up straight and pay attention to software quality.


Learning Objectives:

  • How to connect your metrics with agile related objectives to ensure your agile process is on track.
  • How to develop a measurement framework that measures not only typical test results such as defects, but processes and functions and their alignment with your agile objectives.
  • How to include measurements, metrics, objectives, questions and answers (for your stakeholders) to see if they really want to be agile or are just talking.
  • How to use metrics to not only evaluate, but also predict what could go wrong in your agile process.


Tutorial Outline:

Module 1: Back to Basics

  • What metrics can and cannot do/show us
  • How metrics help us
  • Measurements
  • Metrics
  • Indicators
  • Questions
  • Answers and objectives


Module 2: Developing and Connecting the Framework for your Agile Process

  • Identifying stakeholders
  • Connecting questions with answers
  • Relating answers with metrics
  • Developing evaluation, prediction, and action based on indicators
  • Making a framework to drive towards quality rather than speed
  • Components of your framework
  • Connecting the Agile process into the framework
  • Connecting people/organization into the framework


Module 3: Applying Metrics within a Agile Quality Model

  • Defining a quality model within the agile framework
  • Where do metrics fit in quality models
  • Developing a Agile quality model
  • Connecting the metrics with quality and the end customer

Journey from Good to Great: Building High-Performing Teams

Frank Rios and Danka Grujicic

High-performing teams! Wishful thinking or reality? How do you know? As leaders, we talk about high-performing teams and how effective and engaging they are. As teams, we produce results, overcome challenges, and meet our deadlines. Because of this, we are a good team. However, does that makes us a performing or high-performing team? Creating an environment for a high-performing team is not easy, but it’s something we can all do.

During this tutorial, you’ll learn what research shows are the successful traits of high- performance teams, how to build emotional intelligence in groups, and learn the meaning of a term called “Ba”; and how “Ba” is energized with intentions, vision, interest, and mission. These learnings will be mixed with hands-on activities that will get you out of your comfort zone. You can then take these activities back to your teams where you will be able to see the greatest benefits.

Learning Objectives:

  • What researchers discovered while investigating high-performance teams
  • How to build Emotional Intelligence in groups
  • What “Ba” is and how it can lead to a high-performing team
  • How to facilitate these activities with your team


Tutorial Outline:

  • Starting the journey
    • Tuckman’s model
    • Getting to know the team, better
  • Activity: Journey Lines
  • Putting the fun in dysfunction
    • 5 dysfunctions of a team
    • How to do a team assessment
  • Going from good to great
    • Shu-ha-ri
    • Building emotional intelligence
    • Understanding high-performance
    • Creating the team’s “Ba”
  • Activity: What high-performance means to us

Value Chain and Process Mapping Techniques for Agile Organizations

Tom Cagley

Organizations of all size must continuously evolve through strategic process improvements. Process improvement requires a solid understanding of how teams transform ideas and knowledge into value that a customer can consume. Value Chain Mapping is a high-level representation of how an organization transforms raw materials into a product and then delivers that product to its customers. Value chains need to be decomposed into process maps to effectively implement agile or scaled agile approaches. Process maps are a critical step to reduce process burden and to shift quality activities left in agile.

In this tutorial Tom will provide insight to value chain concepts and how to use value chain mapping and process maps to evaluate process and value flow. You will learn what activities add value and those that support delivery within the process. Using a set of metrics, you will be able to identify waste, wait time, and other targets for improvement within your process, which developers, testers and scrum masters can act upon.

Learning Objectives:

  • Define value chain concepts
  • Understand Value Chain Mapping techniques
  • Review the differences between value chain and process maps
  • Introduce a set of measures to evaluate process and value flow
  • Learn the steps need to develop both a value chain and process map

Tutorial Outline:

  • Value Chains
    • Poter maps
    • Defining customers and products
    • Identify what adds value and what support delivery
    • Value chain development exercise
  • Process Mapping
    • Process mapping concepts
    • Transformation
    • Gemba walk.
    • Measuring transformation, wait time, and work in progress
    • Other Measures
    • Process mapping concepts
    • Process mapping exercise
  • Experimentation in Process Flow
    • Using process maps to identify process experiments
    • Experimentation in a business environment

Innovative Techniques for Achieving Continuous Delivery

Tanya Kravtsov

“It’s not the strongest of the species that survive, nor the most intelligent, but the one most adaptable to change.” ~ Charles Darwin

The most critical step in Continuous Delivery adoption is identifying the bottlenecks in the product development cycle. In this interactive tutorial, you will learn about tools and methods that facilitate the bottleneck discovery as well as ways to deal with the most common bottlenecks that cripple development process. I will demonstrate how treating automation as a silo causes it to fail or be shelved, and how automating “before” and “after” which includes build, environment, data, test results analysis and monitoring will help them to succeed. To solidify the concepts, you will play the “Continuous Delivery” game, competing with other Agile teams to deliver feature to production while improving your software delivery process. This game serves as a great tool to understand the importance of automating Quality Gates and investing into process improvement initiatives to achieve long-term success.

Learning Objectives:

  • Learn to identify and prioritize the bottlenecks in the software delivery lifecycle
  • Leverage Tools available in the market to address above bottlenecks (e.g. test environments, manual regression)
  • Use innovative techniques to move towards Continuous Delivery

Tutorial Outline:

  • Continuous Integration vs. Delivery vs. Deployment
    • “CALMS” definition
  • 10 Steps
    • Identify Bottlenecks (Exercise: Map Delivery Pipeline , Speed Boat Game)
    • Common Repository for Artifacts
    • Automate Build and Deploy
    • Collect Code Quality Metrics
    • Automate Environments
    • Automate Testing (Exercise: Selecting Automation Candidates, Finding Unknowns)
    • Automate Performance
    • Automate Results Analysis and Reporting
    • Ensure Continuous Feedback (Exercise: Continuous Feedback)
    • Manage Unrealistic Expectations
  • Target State
    • Exercise: Mind Map
  • Play “Continuous Delivery” Game

RESTful API Testing in Ruby

Jamie Kelley

As automation testing suites mature, the need to create maintainable tests increase. Creating easy reusable test harnesses becomes imperative, otherwise the test suites become outdated and cumbersome to the software development process. Furthermore, applications continue to push forward into a more service level architecture. This growth in RESTful services means our automated testing suites need to be robust and maintainable enough for the demand.In this hands-on tutorial through a user story driven approach, you will learn how to create a robust RESTful API testing harness. You will learn guidelines on how to introduce good object-oriented design patterns for readable code. You will create common utility methods to wrap around third party libraries. Finally, you will build a data management layer for your calls’ payloads and parameters. Ruby and an existing local RESTful API will be used for training purposes, but the insights you gain are transferrable to any programming language and API.

Learning Objectives:

  • Review what a common RESTful API Testing suite can look like
  • Introduce good programming principles to the suite
  • Learning about key layers to build in the suite
  • Covering key design questions you will have to answer

Tutorial Outline:

  • In the Beginning
    • The basics of REST
    • The Why of API Testing
    • The How of API Testing
    • Showing the pitfalls of standard testing suites
    • Key programming patterns we will introduce
  • Bringing the Utility
    • Wrapping third party calls inside utility methods
    • Adding good error management
  • Adding Good Object Oriented Principles
    • Wrapping API endpoints into a Page Object pattern
    • Showing how OOP convention over configuration can add reuse and maintainability with added utility methods
  • Handling your Data
    • Creating a layer for data management
    • Combining it with your API Objects for dynamic data call creation
  • Extra Features to Add
    • Using Rake to make dynamic runs easier
    • Adding Cucumber and BDD
    • Making reusable steps

Note: Ruby installation (2.3.3 preferred)

Exploring Context Driven Testing & Exploratory Testing

Nancy Kelln

More and more, testers are using exploratory testing and context driven testing techniques in their organizations. However, as many testers start to embrace these testing methodologies, they are uncovering questions in their implementation.

In this half-day tutorial, we will explore the various aspects of testing including test planning, test design, test execution, and test reporting from the exploratory testing mindset. We will also cover how to prepare your organization for the shift from more traditional methods to exploratory testing methods. Testers who attend this session will leave understanding how to implement exploratory testing concepts through all the phases of test planning, design, execution and reporting and feel confident returning to their organizations to implement their changes.

Learning Objectives:

  • How the various aspects of the testing cycle (Test Planning, Design, Execution and Reporting) are different in Exploratory Testing than they are in traditional testing.
  • How to implement Exploratory Testing concepts through the various aspects of the testing cycle.
  • How to prepare their organizations for the shift from more traditional testing to Exploratory Testing.
  • How to deal with resistance to Exploratory Testing techniques.

Tutorial Outline:

  • Defining Context Driven and Exploratory Testing
  • The Exploratory Testing Approach
    • Test Strategies
    • Test Plans
    • Test Execution
    • Reporting & Metrics
  • Preparing Your Organization for Change

$ave a bundle with a Bundle!

You can register for QUEST Tuesday’s Tutorials or bundle the tutorials with the three day QUEST Conference and Expo to save BIG BUCKS on the conference week package. See the pricing page for significant savings!