Letter from the Editor – September 2021

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. Especially soft skills work- communication tools, communication infrastructure, regular check-in’s, the importance of face-to-face video rather than simply an email or a phone call check-in – having those tools in place, and using them for some time, made the working at home/everyone remote go more smoothly. Hopefully by now it’s easy for Agile/Scrum software development teams to keep working together smoothly – even when we’re not in the same room for a daily standup.

But what I’ve been thinking about more lately is the technology integration that goes along with team integration, or task distribution that goes along with integrating dispersed teams. The rise of Full-Stack Development. We take this wide skill set for granted today but it was not too long ago that we had UI designers, engineers and DBAs (database administrators) all doing separate tasks on the same project- and hopefully talking to each other. Full-Stack Development takes one degree of miscommunication or non-collaboration off the table. At the same time, the new distribution of testing tasks has expanded to:

• Developer Unit Testing

• New Functional Testing

• Manual Testing

• Maintaining the Automation

• Automating the new tests

• Executing for Regression suites

• End to End testing

Distribution of tasks we know about, and we also know about the importance of communication and collaboration- and now we’re doing it when everyone is remote. I still think Software Development practices are context-driven. There isn’t one profile for how Dev Teams work. For as many organizations with Full Stack Development that also have Full Stack Testing, where all of the Software testing tasks are consolidated into one team that does all of the new Functional Testing, manual, cross-browser, cross-device testing, maintaining Automation suites and frameworks end to end testing, there are probably more that have distributed the testing tasks across multiple teams, time zones tools and skill sets. Of course, different companies will try different solutions. A mix of internal staff, local staff, distributed staff, outsourcing – I know organizations where this discussion has become irrelevant due to COVID-19 and the staffing crunch happens in the aftermath.

Some organizations are taking any course possible to get the staff to do the job: their internal employees, individual contractors, or entirely outsourced teams. The key to making all this work:

– Working with flexible staffing solutions that even 2 years ago may have seemed undo-able.
– Collaboration is still the most important word. The power of video is stronger than a phone call or email.
– Communication infrastructure needs to be ready for anyone, and be ready for anything
– The most important thing is getting the job done these days, regardless of who does it.

Summary

As we look towards improving communication and adjusting to remote work, it’s a good time to bring up the change in LogiGear Service offerings. This is the start of a new direction for LogiGear Magazine, as we’ve become the LogiGear Group of companies, we look to serve you with content around Software Development, Software Testing and Salesforce CRM development from our own MK Partners. In this issue you’ll see a feature from Michael Larsen on what’s more important scalability or quality? Our blogger of the month features Slack and Salesforce and how to catch up on integrating both within your organization-even more important as we look towards improved communications/processes in this new paradigm. I’m rounding up the pack with a focus on Customer Experience and an example of how quickly bad CX can transform a gift into a burden, based on a recent experience I had. And as always, as we look towards the future if you’re looking for digital transformation assistance feel free to contact us.

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

In the November 2011 issue: Mobile Application Testing, I began my column with the statement, “Everything is mobile.” One year later the statement is even more true. More devices, more platforms, more diversity, more apps. It boggles the mind how fast the landscape changes. Blackberry has been kicked to the curb by cooler and slicker ...
Continuous Testing… what is it? When we first decided to do a magazine issue dedicated to the DevOps practice of Continuous Testing, I joked with someone: “It’s about testing continuously.” And their reply was: “Yeah. What else would it be?” I was joking, but clearly the joke didn’t land. Continuous Testing is about testing continuously, ...
I remember the times when test teams sat in their own area and we were not allowed to “bother” developers.
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?
“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 ...
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 ...
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.
There has been a tectonic shift in software development tools in just the past few years. Agile practices and increasingly distributed teams have been significant factors but, in my opinion, the main reason is a new and more intense focus on tools for testing driven by more complex software and shorter development cycles. There have ...
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 ...
Testing the Software Car. As usual with the LogiGear Magazine, we are tackling a big subject. With our goal of having single-topic issues, we have the ability to grab and disseminate as much information as we can related to a current topic that is interesting and also on the frontier of Software Testing.   Some ...
Hello everyone – I’m hoping each one of us is having a great October. This time of the year is always my favorite, with the changing of the seasons, Fall was always my favorite time of year; it signified change and renewal – but I don’t want to digress to much from what’s going on ...
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 ...

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