Letter from the Editor – December 2020

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 idea to “innovate or die.” No one questions the immediate need for this work, but one thing is for sure: Test Teams need to be at the center of these projects.

“Digital Transformation” and “IT Modernization” are broad terms for big projects. A Digital Transformation (DT or DX) is the adoption of digital technology to transform services or businesses, through replacing non-digital or manual processes with digital processes, or replacing older digital technology with newer digital technology. Digital solutions may enable—in addition to efficiency via Automation—new types of innovation and creativity, rather than simply enhancing and supporting outdated ways of doing things. IT Modernization aims to bring legacy IT infrastructure up-to-date and focuses on addressing operational challenges, including efficiency, access, security, and agility.

There are many reasons why these projects or paradigm shifts can overwhelm a company, including:

  1. Software Development practices have changed significantly.
  2. Toolchains have grown rapidly thanks to DevOps’ influence on quality, automated delivery and deployment, and speed.
  3. Staffing models and changes.
  4. Adoption/modernization of new technologies, hardware, and devices.
  5. Legacy systems.

Why specifically are these projects happening now? Multiple reasons: Business models and processes have changed, demand for full mobility, users’ demand has taken control, taking advantage of new technology, etc. How can Test Teams help here? No matter the exact cause, the situation at hand is a rapidly changing need, not well understood, and evolving use cases, new technologies, and speed. This is a typical strong suit of Test Teams––if it isn’t, then you may not be using your Test Team correctly.

In my experience with new products, workflows, or transformations like these, the Product Owners (POs) may not understand the customers or have a great projection of how their users will actually use the product. The Team may also get incomplete user stories without a lot of understanding of how a new feature is expected to be used.

What is often lacking here is alternative uses and alternative workflows––specifically, workflows from various personas who have different needs and goals. At the speed that most development teams work today, these are often not defined. An example of this is not thinking through error conditions, where the user needs more help or may become more frustrated as error conditions push the system into more unstable states.
It’s understandable that these issues happen––particularly with new technologies, new business models, and demanding customers. But, this situation is a strong suit for Test Engineers. A Test Team’s core skills are the magic intersection of knowledge of the user, knowledge of the technology, and knowledge of quality and testing practices. It’s the knowledge of how to test that is particularly useful here.

A three-way Venn Diagram, depicting the intersection of "Knowledge of the User," "Knowledge of the Platform/Technology," and "Knowledge of Testing & Quality Practices"––the magic intersection of a Tester's core skills.

Figure 1 – Skills Testers need.

If you are using your Test Team merely for acceptance criteria validation and UI Automation, you are under-using them, tasking them wrongly, or not aware of what great benefit Tester exploration and spending time in a new system can be. Key skills for testing that any trained and skilled Tester must possess is the ability to explore alternative paths, discover other workflows by spending time in the system, and doing “the Tester Thing.”

Put to the right task, Test Teams are a valuable asset on transformation and modernization projects with developing and evolving use cases and user stories. Core testing skills are designed just for these situations. Good Test Teams bridge the technical system to deliver a product with customer value.

This issue brings together an array of content to help you succeed in a Digital Transformation initiative. Our cover story is part 2 of my series Developer Testing? What is QA and Testing’s Place? and strategizes how managers can succeed in Developer Testing initiatives. Another part 2 piece, Using Agile Testing Quadrants to Solve Quality Assurance Headaches, was written by our SVP of Sales Clayton Simmons and explores the need for Automation in Agile, as well as how to use the quadrants to your success. This issue’s Blogger of the Month, 6 Things to Consider When Choosing an RPA Vendor, provides guidance for organizations looking to implement RPA––a foreseen key-enabler of Digital Transformations in the near future. Our infographic, LogiGear’s Winter 2020 Reading Guide, aims to help you solve common testing problems by recommending related eBooks. We’ve also collected the Best of LogiGear Magazine 2020, where you can learn some testing tips and tricks from our best-performing magazine articles of the year. Finally, we also wanted to share the latest and greatest features of TestArchitect Gondola in TestArchitect Corner: Greetings from Gondola!

From all of us at LogiGear, Happy Holidays and Happy Testing!

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?
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 ...
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 ...
For everyone still celebrating holidays: Happy Lunar New Year! At this time of the year many teams and companies are starting new projects, new initiatives, and hiring new staff. LogiGear Magazine will continue to be the resource for you for better testing with much less stress! We are excited about the focus of this month’s ...
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.
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 ...
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 ...
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. ...
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 ...
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 ...
Hi everyone and welcome to our fourth edition of LogiGear Magazine. This month we finish Michael Hackett’s piece on “Agile in Testing” with part five, Tools.
Testing Embedded systems and testing the Internet of Things could each have their own issue of LogiGear magazine. But these days they are referred to presupposing knowledge of the other, so we thought it would be a good idea to tackle the two together in this issue to give a broad understanding of the landscape ...

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