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

Every organization goes through times when the internal, or home team, cannot execute the testing project easily or quickly enough. The reasons are many, from the lack of an effective test strategy to low automation engineering skill, to staff positions going unfilled due to a great job market. With everyone working and very few people ...
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 ...
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 ...
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?
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.
Testers need to learn their craft and hone in on their skill set. That means building skills, sharpening their tools, and becoming creative detectives. There is no cookie-cutter tester and no best practice. The best circumstance is a fully-skilled, aggressive tester mixed with curiosity, nimbleness, and agility.
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 ...
On the whole, everyone wants to do a great job, have a better work environment, happy clients and customers, and to be employed by a company earning lots of money. All great goals! But this is not always the case. When it is not, you can suggest process improvements, better tool use, different estimating techniques, ...
Our plan for the December LogiGear Magazine was to have a forward-looking Trends and Challenges issue. However, whilst assembling our September issue on SMAC, we realized the momentum SMAC was gaining in the industry. We had a large amount of content on our hands from a range of excellent contributors. Thus, we decided to split ...
Testing tools – very important, very often overlooked, and very often where mistakes are made. First, the most common mistake people make about tools is thinking tools are only about test automation! False. Automation tools are merely one type testing tool. We will try to balance this issue between test automation tools and other test ...
As part of my work, I spend a lot of time at client’s sites and talk to various software development organizations. I am beginning to see a problem arise regarding Test Automation. There is too much automation! Surprised? While there are still many teams struggling to make progress with Test Automation, many teams have been doing ...
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 ...

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news

Subscribe