Letter from the Editor – December 2017

A lot has changed since I began staffing test projects. From hiring college students and interns for summer testing programs, to building networks of offshore teams around the world, and from having 24-hour work schedules to having instant crowdsourced public beta or bug bounty testing—things have changed.

Development methods and technologies have changed drastically, and so have the variety of staff solutions for testing. What hasn’t changed is the need to do more with less. Go faster, but with smarter testing. By the way, “automate everything.”

The expectation for automation is as unrealistic as ever. In minimal time, we want to build “bug-free software” to exceed our customer’s expectations and to provide them with an amazing user experience. This is simply a herculean effort.

Building a team that has the skills to make this happen has always been challenging. In today’s global economy, with organizations fighting over fully-skilled staff, the challenge is even greater.

Deciding who gets hired as Quality Engineers or Testers in the US has always been part art and part science.  We have used this diagram in the past to look at which skills to build. It is also used to help you, as a manager, staff a team.

Technical skill, subject matter knowledge, QA/testing skills

Every test team requires technical skill(s):

  • Someone must be technically knowledgeable enough to test effectively. For automating and gray box testing, technicians must have knowledge of the development platform, technology (client server or IoT or mobile or medical device or browser or embedded system, etc.), as well as some coding and scripting skills.
  • Someone must be knowledgeable about browsers, operating systems, analytics, databases, etc.
  • Others need to be technological generalists, aka enough to be dangerous.

A successful team needs subject matter experts. If you are testing FinTech, the team doing the work must understand how asset management works, and how loans work—the origination, the payouts, what users need and do to get a loan, etc. I have seen this skill be the deciding hiring factor more than any other skill. It is often the tie-breaker.

The team you build needs to have excellent testing and quality assurance skills. This skill set is often taken for granted. Being able to write a complete and excellent bug report without relying on a screenshot and effectively communicating test coverage are valuable, overlooked skills.

Each member of the team must comprehend the need, purpose, and reason for test cases. In addition to being quality advocates, a few members of the test group need to know how to write a test plan and know why a Lean test plan is critical. Additionally, they must know what measures—with the inclusion of burn down and velocity—a team can look at for quality improvement, and understand an array of test methods and techniques to solve various testing situations.

Looking for all three of these diverse skill sets in one person is like looking for a purple squirrel; it is nearly impossible so when you find it, grab it and don’t let go! Most often, you’ll need to weigh and counterbalance these skills to fill a team, in hopes of obtaining the full array of skills needed across the team.

Getting this skill set through staffing will impact the method you use to staff your organization.  On one extreme, you can hire a subject matter expert, perhaps at a high salary, and train them to obtain the rest of the essential skills.

You could find subject matter experts internally and outsource testing and testing skill—a very common solution. On the other hand, you could crowdsource and get what you get.

Do not make the mistake of assuming that everyone working in technology has the necessary technical skills, and that individuals working in testing are equipped with great testing skills. With so few well-trained quality experts and such high demand for skilled technicians, staffing can be very difficult.

This December issue of LogiGear Magazine features a case study of LogiGear’s efforts to create an Innovation Lab for its offshore team, an infographic that covers 5 steps to a successful software testing service engagement, and a special Blogger of the Month on AI testing. We hope you enjoy perusing the articles, as our goal was to start a modernized discussion on staffing and outsourcing in the 21st century.

Michael Hackett
Michael is a co-founder of LogiGear Corporation, and has over two decades of experience in software engineering in banking, securities, healthcare and consumer electronics. Michael is a Certified Scrum Master and has co-authored two books on software testing. Testing Applications on the Web: Test Planning for Mobile and Internet-Based Systems (Wiley, 2nd ed. 2003), and Global Software Test Automation (Happy About Publishing, 2006). He is a founding member of the Board of Advisors at the University of California Berkeley Extension and has taught for the Certificate in Software Quality Engineering and Management at the University of California Santa Cruz Extension. As a member of IEEE, his training courses have brought Silicon Valley testing expertise to over 16 countries. Michael holds a Bachelor of Science in Engineering from Carnegie Mellon University.

The Related Post

Integrated teams Something we’ve learned in the Covid-19 pandemic is that we have to work together-whatever together means. Very few teams stayed co-located; even teams in the same town worked at home. We’re all working remote. Hopefully all the thinking, tools, work and effort we put into having offshore teams work together benefited us here. ...
Big and complex testing. What do these terms conjure up in your mind? When we added this topic to the editorial calendar, I had the notion that we might illustrate some large or complex systems and explore some of the test and quality challenges they present. We might have an article on: building and testing ...
How do you test software? How do you validate it? How do you find bugs? These are all good questions anyone on your project team or anyone responsible for customers may ask you. Can you articulate your test strategy─not your test process, but explain your approach to testing? I find that this can be a ...
I was just recently at a company that had a beautiful test architecture, framework, and Cucumber with tons of well-automated tests. But there was no good test management on top of the Cucumber tests, and they did not do a good job tagging the tests. Although almost everybody on the team could write and maintain ...
I have been training testers for about 15 years in universities, corporations, online, and individually – in both a training, managing and coaching capacity. So far, I have executed these various training efforts in 16 countries, under good and rough conditions – from simultaneous translation, to video broadcast to multiple sites, to group games with ...
There is a growing software development dynamic of teams without Testers. When I first went into Software Quality, I learned one thing right away: My role was user advocate. My main job was to find bugs. This is the Lean principle called Amplified Learning. We learn about behavior by testing. Even then, validation was not ...
Software development projects are multifaceted. There is staffing and budget work. There are communication and team dynamics. There are project and process issues from what the customer wants, when they want it, revenue projections, and production dates. As part of my work in helping people deliver software, I get involved in all aspects mentioned above. ...
I spend about half my work time in the role of a consultant assessing, auditing and examining software development team practices and processes for the purpose of process improvement. I am regularly surprised to find teams that lack basic skills, management support, tools, information, access to users, Product Owners and to developers. And yet they’re ...
Digital Transformation and IT Modernization projects have shifted into high gear during the COVID-19 pandemic. Tough on some teams is having to do more with less and speed up projects on reduced budgets due to the resulting COVID-19 business climate. On the other hand, other companies are adding funding and pressing the schedule under the ...
In every year since 2011, we have devoted one edition of our magazine to the topic of mobile testing. In this year’s issue on mobile, we focus on testing from the point of view of the user experience. Most teams start with UI testing, and it may seem basic — until you look at the ...
This is our third issue concerning topics of Continuous Delivery (CD) and DevOps with the inclusion of Continuous Testing. DevOps has been around for a while and I hope the period of buzz is over and companies moving towards building a development pipeline have begun their process, including changing their test strategies.
I led the Editor’s Note in our very first mobile issue with “Everything is mobile”, but it is now way beyond what we thought. Mobile has come to mean only the smart phone, mobility is the word that describes everything a smart phone enables you to do. Mobility is more than a device! Mobility is ...

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news

Subscribe