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

What is testing in Agile? It’s analogous to three blind men attempting to describe an elephant by the way it feels to them. Agile is difficult to define and everyone has their own perspective of what Agile is. When it comes to testing and Agile the rules are what you make them. Agile is ideas ...
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 ...
As fast as Mobile is growing, the platform is still immature and is evolving at a very rapid pace. While there are whole countries that have migrated large government services to mobile, countries ranging from Estonia to Turkey to Kenya have many longtime mobile users have yet to use mPay or other mobile payment systems. ...
A while ago, I helped start a Software Quality Certificate Program as a part of the Software Engineering Program at the University of California, Santa Cruz Extension in Silicon Valley. I was on the Board of Advisors. While putting the curriculum together, a few people suggested a Measurement and Metrics course. Since I was teaching ...
The Greek philosopher Heraclitus of Ephesus (c. 500 BCE) is credited with saying, “The only constant is change.”   This is a statement that, more than 2,000 years later, still holds true. Today, we are in a time of great change. Everything is in flux. The fact is, we are always in a state of change even if ...
Automation is a mantra in testing. Anyone associated with software development wants more test automation, but it’s often misunderstood. People who do test automation know how difficult it can be. But some people do not understand that automation is code, and that it needs to have architecture and design just like production code. They do ...
If you are reading this issue, you are probably aware of the impact on the business world of cloud computing. Most people do not have a good grasp on what the cloud is or how people and products can use it. BTW, you are already a cloud user. If your email is stored somewhere “on ...
This is LogiGear magazine’s first issue on the big world of DevOps. DevOps is a very large topic. Just when you thought you were safe from more process improvement for a while—not so fast. There’s DevOps, Continuous Testing, Continuous Delivery and Continuous Deployment. In this issue, we are focusing on Continuous Testing, the part most ...
“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 ...
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 ...
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 ...

Leave a Reply

Your email address will not be published. Required fields are marked *

Stay in the loop with the lastest
software testing news

Subscribe