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

Methods and strategy have been my favorite topics since I started working in testing. It’s essentially engineering problem-solving. It’s both looking for efficiency and attempting to measure effectiveness. So, how do we develop a set of practices to solve our Software Testing engineering problems?
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. ...
Change is constant. What’s different today is the rate of change. Moore’s law resulted from the observation that that the rate of change in computing power is exponential. The products, services and software landscape appears just as dynamic. At the same time, we pretty much take for granted the ubiquitous presence of software running our ...
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 ...
This is a very special issue of LogiGear Magazine. When we were putting together the Editorial Calendar for this year, we decided that instead of a technology issue, we would focus on the human side of quality and test engineering. We want to focus on individual Test Engineers and their jobs. We talked to a ...
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 ...
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.
We launched the first ever software testing conference in Vietnam, VISTACON. It was a resounding success, with well over 200 participants and 20+ speakers from around the globe; each speaking on a wide range of cutting-edge testing topics. In this month’s magazine, we have uploaded several video recordings of event presentations – giving our readers ...
“Why do we need to understand a bunch of test methods? I write test cases from user stories or requirements, automate what I can and execute the rest manually, and its fine.” If this is your situation: good for you. If you are time crunched, if your automated tests have lost relevance, are hard to ...
Everything is mobile. What else can we say? Everything. If your product or service is currently not, it will be very soon. As Apple says: “There’s an app for that.” There is an app for everything. The race for mobile apps has consumed the software development world. I did a few projects at Palm Computing in the ...
API testing– an old school technology gets way cool again. APIs and testing them is nothing new; the technology has been around for decades. The most basic definition of an API is an exposed function— a producer (person or company) writes a function and exposes it so that others, consumers, can use it. We copy ...
I remember the times when test teams sat in their own area and we were not allowed to “bother” developers.

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news

Subscribe