Alright, folks, let’s dive into this topic and see how QA can be your knight in shining armor during times of uncertainty. You know, those days when a layoff looms like a dark cloud, threatening to disconnect you and your team from your beloved office space. But don’t worry, we’ve got a plan.

Picture this: The layoff-riper has visited a few times already. It’s like that one friend who visits your place just a bit too often, takes great buds with him, leaves a mess each time and you’re starting to wonder if your hospitality knows no bounds.

Now, let’s get down to business and figure out where we stand, both in terms of the organization and the state of things. I’m going to walk you through a scenario that might make you feel like you’re in a comfy spot, but bear with me; there’s always more to learn.

Let’s roll up our sleeves and get started.

Time, Place, Project:

Picture this: We’re in the midst of a project dedicated to delivering the ultimate user experience for video content enthusiasts. It’s all about making your binge-watching sessions smoother and more enjoyable.

Now, let’s talk about the “Time” part of our story. We’re right in the middle of what we’ll call the “Great IT Layoff” era. And it’s not just the layoffs; it’s also dealing with the aftermath of an epidemic and emerging world wars. So, we’re talking about 2023 stretching into 2024. It’s like the script of a blockbuster movie, but it’s our reality.

As for the “Place” well, we happen to find ourselves in the entertainment hub of the USA — Los Angeles.

Now, WHY does all of this matter? It’s pretty simple. LA is the heart and soul of content creation in the USA. It’s where the magic happens, where new content keeps rolling out. Even though the content industry has been pretty solid for over a decade, there’s always an audience, even when people are on a tight budget. But here’s the twist: the layoff reaper has knocked at our door too. We won’t delve into the why for now; that’s a whole different story. The main point is that our company focuses on consumer TV viewing and new shows, and the IT sector plays a supporting role within the company. That’s why the development and QA teams felt the impact of the layoff cycles.

Now, let’s add a splash of color to our story. Over the past year, as we all know, the backlog of tasks has been piling up. It’s like having a never-ending to-do list.

So, to sum it up:

• We’ve got an ever-growing backlog.
• Team members have been let go.
• Processes are playing catch-up with every change.
• There’s a cloud of uncertainty hanging over our heads.
• And the layoff reaper is lurking, a feeling that just won’t go away.

That’s the vibe around here. Now, let’s dive into the role of QA in this challenging landscape.

QA in the Trenches: Navigating Chaos with Expertise

Let’s introduce you to a typical QA, someone who’s not just your average tester but a general SDET (Software Development Engineer in Test). This person is a seasoned quality assurance pro, having saved not just one but multiple releases from disaster.

Now, picture this QA in a project hit by recent layoffs mentioned above and a never-ending list of tasks. It’s like having a massive pile of homework that never seems to shrink.

Here’s what they’re dealing with:

Too Many Cooks in the Kitchen: The QA has a bunch of stakeholders, each pulling them in a different direction with their own set of bugs and issues. It’s like juggling flaming torches.

• Managerial Handoffs: Their direct manager keeps sending automation-related tasks their way. It’s like receiving surprise packages every day.
• Silent Developers: Developers around them aren’t updating task statuses. It’s a bit like trying to catch a ninja; you never know where they are.
• Daily Scavenger Hunt: To find out what tasks are dev-completed, the QA needs to attend daily meetings. It’s like a daily scavenger hunt without any clues.
• Documentation Dilemma: With so many tasks, documentation is often left in the dust and is mostly incomplete. It’s like trying to follow a recipe with half the ingredients missing.
• Memory Struggles: The functionality of tools and features can slip through the cracks in just a couple of sprints. It’s like trying to hold sand; the tighter you grip, the more slips through your fingers.
• Too Many Chefs: Prioritizing tasks is a puzzle because there are too many developers for just one QA, let’s say about 7 or more. It’s like trying to lead a team of wild horses.

Now, you might be wondering, how can this QA keep going when the backlog is growing like an unstoppable avalanche, and the more steps they take, the murkier the tool’s functionality becomes?

Support is taking longer with each passing iteration, and it feels like being stuck in quicksand. But fear not, we’re about to explore how they manage to tackle this Herculean task.

Quiet on the Set… Lights, Camera… Action:

Now, how does this incredible super QA SDET pull off the magic? Allow me to introduce you to two of my new pals: Vision and Mission.

In short, Vision is like looking through a crystal ball, showing us the future with our current product in mind. Every company’s VP has a unique vision, but its Mission is like the map, showing us how to reach that vision.

With these two by our side, it’s time to roll out the solutions and overcome the challenges in this QA adventure.

‍

Mission: The GPS for Chaos

Now, when you’re in the midst of chaos and uncertainty, it’s time to focus on the features that will have the most impact on delivering your manager’s vision. Let’s break it down:

What to do:

• Define Your North Star (Mission and Vision): It’s like setting your destination in your GPS before a big road trip.
• Confirm Your Mission Matches Your Manager/Product: Ensure your map (mission) lines up with where your manager wants to go.
• Define and Formalize Your Functions: Think of it as listing all the roles in your movie’s credits.
• Define Your Limitations: Just like setting boundaries for your character in a game.
• Keep an Eye on the Pipeline: Watch those tasks flowing through, and pay extra attention to ones that are part of the big picture (vision).

Now, let’s take an example:

Case: Your manager has set the vision for the next six months:

1. No Bugs in Backlog with P0-P1: It’s like saying, “Our mission is to have a smooth journey without any roadblocks.”
2. Product X Monetization: This is the treasure chest we’re aiming for, and our mission is to find the key to unlock it.

So, your mission will be to:

1. Enhance Documentation for Bugs: It’s like preparing a detailed map for a bug-free journey.
2. Handle P0/P1 Tickets Efficiently: Think of it as clearing the highway for smooth traffic.
3. Work on Clearing the Backlog: No one likes a pile of dirty clothes.
4. Communicate with Stakeholders: Keep everyone in the loop about the treasure hunt for Product X’s monetization.
5. Define and Track Monetization Tasks: It’s like tracking the clues that lead to the treasure.

With this clear mission, we’re all set for action in this chaotic world. Let’s make the magic happen!

One other way to address this would be to go from the risks perspective…

But that is a different article…

‍