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

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 ...
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 ...
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.
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 ...
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.
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 ...
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 once consulted for a company to give a week-long course on testing and QA. It was a survey course covering a wide range of topics. I was setting up and chatting with students in the room. One man came over to me and said: “I have been testing for 6 months and I am completely ...
“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 ...
I have been training testers for about 15 years in universities, corporations, online, and individually – in both a training, managing and coaching capacity. So far, I have executed these various training efforts in 16 countries, under good and rough conditions – from simultaneous translation, to video broadcast to multiple sites, to group games with ...
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 ...
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, ...

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