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 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 ...
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 ...
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 ...
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 ...
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.
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. ...
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 ...
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 ...
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.
“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 ...
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 ...
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 ...

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