Letter from the Editor – July 2012

What is testing in Agile? It’s analogous to three blind men attempting to describe an elephant by the way it feels to them. Agile is difficult to define and everyone has their own perspective of what Agile is. When it comes to testing and Agile the rules are what you make them.

Agile is ideas about software teams working together with no details. SCRUM is a framework for managing software projects. Extreme Programming (XP) has practices about making the product and coding. Agile says nothing about testing. SCRUM definitely says nothing about testing. There is no role in SCRUM called Tester, QA, or QE! Extreme Programming comes the closest, but the focus of testing is on developer focused TDD (test driven development) through unit testing. The work of traditional testers is not defined by any of these famous practices or frameworks. We are making it up as we go.

While Agile evokes images of happy, self-directed teams working well together, there are problems. The Agile manifesto has been around over 10 years. SCRUM has also been around long enough to have been tried, failed, succeeded, abandoned, and tried again.

Two dirty words to describe the practices of any team are Agilefalls and Scrumbuts.

Agilefalls is a practice that badly mixes agile and waterfall. Scrumbuts is the famous descriptor coined by Ken Schwaber (co-creator of SCRUM) of people adapting SCRUM as a loose process to suit whatever needs they have. SCRUM is anything but a loose process. As the 2011 Update (available at www.scrum.org) says, “The Scrum Guide is the definitive rule book of Scrum and the documentation of Scrum itself.”

No one can tell you there is a definitive way to test in Agile projects. There simply isn’t a best practice here. The better practices for your team are going to be based on many things. Among them; how much you automate, to how you implement Lean and the type of documentation your team writes, to the definition of done. How you test and how much you validate will probably be left up to you! Here is where we come in. We asked some insightful thinkers to share their perspective on testing in Agile to help you put together a test strategy or improve the one you have.

In this issue, IBM’s Scott Ambler discusses the role of discipline in your Agile testing strategy; Pankaj Nakhat talks about the paradigm shift test teams must undertake for successful Agile projects; Ralph van Roosmalen looks at how to better organize and track the Agile process; I address the misconception that Agile is about speed; John Roets presents alternative office layouts that can promote knowledge sharing on Agile teams; Madhu Venantius Laulin Expedith examines aspects of traditional testing that must be unlearned when switching to Agile development; Gunnar Peipman reviews the book Clean Code: A Handbook of Agile Software Craftsmanship written by Robert C. Martin; and finally, I’ll look at the manager-specific responses from our 2010-2011 global survey.

Whether a true-believer or late adopter, there is no arguing that the tasks test teams used to do in traditional projects are not defined. So, what do we do? In true SCRUM style, we try things. Hopefully we fail fast. To fail fast is to try something full-speed. If it works, great. If not, recognize it failed and try something else.

Testing in Agile projects is evolving. What we do, how and when we do it, is maturing. We need to constantly reflect on our practices. Keep what works, discard what does not. Share experiences and continuously improve. I hope this issue gives you food for thought and that other opinions and experiences help improve your practice of testing in Agile projects.

Michael Hackett
Senior Vice President
Editor in Chief

LogiGear Corporation
LogiGear Corporation provides global solutions for software testing, and offers public and corporate software testing training programs worldwide through LogiGear University. LogiGear is a leader in the integration of test automation, offshore resources and US project management for fast, cost-effective results. Since 1994, LogiGear has worked with Fortune 500 companies to early-stage start-ups in, creating unique solutions to meet their clients’ needs. With facilities in the US and Viet Nam, LogiGear helps companies double their test coverage and improve software quality while reducing testing time and cutting costs.

The Related Post

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 ...
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?
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 ...
I led the Editor’s Note in our very first mobile issue with “Everything is mobile”, but it is now way beyond what we thought. Mobile has come to mean only the smart phone, mobility is the word that describes everything a smart phone enables you to do. Mobility is more than a device! Mobility is ...
This is a very special issue of LogiGear Magazine. When we were putting together the Editorial Calendar for this year, we decided that instead of a technology issue, we would focus on the human side of quality and test engineering. We want to focus on individual Test Engineers and their jobs. We talked to 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 ...
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 ...
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 ...
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.
As we settle into autumn, we’re taking the time to start some new traditions. This is LogiGear magazine’s first issue on SMAC. SMAC—social, mobile, analytics and cloud. We will be doing more issues in the next few years on these topics since so much of the product world is moving to this development stack.
API testing– an old school technology gets way cool again. APIs and testing them is nothing new; the technology has been around for decades. The most basic definition of an API is an exposed function— a producer (person or company) writes a function and exposes it so that others, consumers, can use it. We copy ...
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, ...

One thought on “Letter from the Editor – July 2012

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news

Subscribe