Letter from the Editor – May 2011

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, etc. Suggestions are generally evaluated based upon whether they are opinions, complaints, thoughtful, useful, possible or even mean-spirited.

A large part of my work over the past few years has been consulting on process improvement for entire software teams or specific test groups helping companies and teams achieve their goals. This all sounds great but I have to say─to achieve meaningful change is often painful! My process improvement work includes team skill assessments, team practice or tool use evaluations. What do I see? Lately, it is companies saying they are Agile when they are not; development teams not taking advantage of the recent huge growth in testing tools; and the traditional favorites: bad requirements dooming a project and unreasonable schedules.

We all want to improve but change is sometimes difficult. There are ways to do process improvement well and ways to set-off turf wars. This is why we included the theme of process improvement on the editorial calendar this year. We hope to provide you with insight and experience into how and what to do to make meaningful and beneficial changes leading to happier teams and customers along with less stress, lower costs and waste reduction.

Our test process improvement issue includes my piece centered on key tips on how to get high performance out of your test teams; two articles on Agile Retrospectives from New Zealand Agile consultant 3months and Mark Levison from England, who is also this month’s Spotlight Interview; an additional related article focused on Retrospectives and Post-mortems and whether or not they are more similar than different; Blogger of the Month Rob Lambert links test process improvement to his encounter at an electronic store; Bryan Pendleton reviews How We Test at Microsoft; and the fourth part of the 2010 Global Testing Surveys series with analysis on Test Process and SDLC.

LogiGear magazine continues to be a resource for your software development projects and company needs─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

“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 ...
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 ...
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 ...
The Greek philosopher Heraclitus of Ephesus (c. 500 BCE) is credited with saying, “The only constant is change.”   This is a statement that, more than 2,000 years later, still holds true. Today, we are in a time of great change. Everything is in flux. The fact is, we are always in a state of change even if ...
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 ...
Because of the type of work I do (consulting projects at different companies), I’ve been lucky in my Software Development career to have worked on a bunch of software projects specific to hardware devices or integrating new hardware into software systems. Starting with the Palm Pilot, I worked on some operating systems (OS) projects, firmware, ...
Testing Embedded systems and testing the Internet of Things could each have their own issue of LogiGear magazine. But these days they are referred to presupposing knowledge of the other, so we thought it would be a good idea to tackle the two together in this issue to give a broad understanding of the landscape ...
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 ...
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 remember the times when test teams sat in their own area and we were not allowed to “bother” developers.
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.

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news

Subscribe