Letter from the Editor – March 2015

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 still expected to carry the heaviest burden of quality and customer satisfaction for the company. It’s the lack of easy access to skills and lack of input on team’s process that is the most disheartening.

Most testers/test engineers/quality engineers have a real desire to be the best they can be at their job; find great bugs, be a team player through project problems and create satisfied customers. Unfortunately, many people who get into testing come from various backgrounds with little to no prior formal testing training. The most common training is on the job “doing what we have always done.” This is where I came in.

There are real project and quality issues facing test teams these days. Teams are dealing with all kinds of problematic issues like Development “handoffs” to test teams while still calling themselves Scrum teams, lack of quality practices and methods, lacking automation, or lacking effective automation trying to have Continuous Integration (CI). It’s common to find teams who have never been trained in scrum using totally scrumbut practices—double standards where the documentation load has been reduced on other team members while testers must still document every test and write large test plans. If you think “You may be a Scrumbut,” check out this great description from the Scrum Alliance: https://www.scrumalliance.org/community/articles/2013/february/you-may-be-a-scrum-but

Many test teams need help with the basics. There are also rare occasions where efficient, effective teams need help moving to the next level, for example, teams that have graduated from Scrum and moved to Kanban for their SDLC. My best recommendation in most situations I have described above is to learn as much as possible and strive for incremental change. Change one thing at a time. Change how you do things, learn one new thing and share it with the team.

Our job at LogiGear magazine is to provide you with quick access to high quality great new ideas for testing and quality. In this issue we present you with two rising test methods, BDD and ABT. We also have great pieces on strategically managing risk and effective requirements analysis. And Clemens Reijnen writes a very timely article on testing in Scrum. We have also done methods and strategy issues in the past, the last from just a year ago, February 2014. Our fully searchable archives are full of great articles on various test methods that you can apply from mobile testing to test automation.

From all over the world- we seek out stories and thought work to best benefit teams thrive today. We want to provide one-stop shopping for testing and quality improvement. It is my earnest hope that you can learn something to help you and your team in this issue and have a positive effect on your job satisfaction, daily work, team, product, and customer satisfaction. Good luck!

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

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 ...
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 ...
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 ...
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.
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.
Test automation is a big topic. There are so many different areas to talk about: tool choice, jumpstart, cross platform, services, cloud… Each of these areas have changed so much in the recent past that they could each be worth their own magazine issue.
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 ...
Every year, LogiGear Magazine devotes one full issue to Test Automation. We could do more than one, and perhaps even that would not be enough. The problems around automation have become increasingly complex. And now, automation is much more integrated into the software development process. For over a decade teams have been faced with “do ...
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 ...
In our continuing effort to be the best source of information for keeping testers and test teams current, we have another issue to explore testing in Agile development. As Agile evolves, systemic problems arise and common rough situations become apparent. We want to provide solutions. For anyone who has worked on Agile projects, especially if ...
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 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 ...

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