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

Software development projects are multifaceted. There is staffing and budget work. There are communication and team dynamics. There are project and process issues from what the customer wants, when they want it, revenue projections, and production dates. As part of my work in helping people deliver software, I get involved in all aspects mentioned above. ...
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?
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 ...
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.
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, ...
Everything is mobile. What else can we say? Everything. If your product or service is currently not, it will be very soon. As Apple says: “There’s an app for that.” There is an app for everything. The race for mobile apps has consumed the software development world. I did a few projects at Palm Computing in the ...
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 ...
I remember the times when test teams sat in their own area and we were not allowed to “bother” developers.
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 ...
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 ...
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 ...
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.

Leave a Reply

Your email address will not be published. Required fields are marked *

Stay in the loop with the lastest
software testing news