Letter from the Editor – July 2013

In our continuing effort to be the best source of information for keeping testers and test teams current, we have another issue to explore testing in Agile development. As Agile evolves, systemic problems arise and common rough situations become apparent. We want to provide solutions.

For anyone who has worked on Agile projects, especially if you have worked at more than one company or for a few clients, you know “testing in Agile” can be an adventure. Remember there are no “rules” or best practices for Agile testing. There are better practices. Every team and Scrum implementation is unique. This is still evolving.

The varieties of Agile implementations, most commonly Scrum, have a nontraditional concept of testing. Yet, most organizations still want someone to do the tasks associated with traditional testing, such as validation, regression testing, bug hunting, exploratory testing, scenario testing, data driven testing, etc. These words have different connotations in Scrum and Agile.

This month we are tackling more Agile topics with a specific focus on how these practices impact testing. As Agile matures and comes of age we are learning more, adjusting our practices, modifying our strategies and hopefully communicating better; we are being Agile.

In this issue, Emily Bache highlights principles to help you plan your testing strategy; I warn teams about the implications of technical debt; David Taber explains that if your team is set up to handle it, Agile can greatly benefit your projects in the cloud; Larry Maccherone looks at why Agile is becoming a vital strategy for small and large businesses; Joel Semeniuk breaks down his predictions on current and future Agile trends and what they mean for testing teams; John Turner reviews A Practical Guide for Testers and Agile Teams by Lisa Crispin and Janet Gregory.

As always, we hope this information is helping you solve problems and release higher quality products. September’s issue is on Mobile Testing.

Happy Summer!

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

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 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 ...
DevOps can be a big scary thing. Culture change, constant collaboration— whatever that means— a big new set of tools… it’s a lot. What most teams want is to have a smooth running software development pipeline. I have stopped using the phrase “DevOps,” and now I say “Continuous Delivery.” There are many reasons for this.
There is a growing software development dynamic of teams without Testers. When I first went into Software Quality, I learned one thing right away: My role was user advocate. My main job was to find bugs. This is the Lean principle called Amplified Learning. We learn about behavior by testing. Even then, validation was not ...
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 ...
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 ...
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.
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, ...
Big and complex testing. What do these terms conjure up in your mind? When we added this topic to the editorial calendar, I had the notion that we might illustrate some large or complex systems and explore some of the test and quality challenges they present. We might have an article on: building and testing ...
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, ...
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, ...
I remember the times when test teams sat in their own area and we were not allowed to “bother” developers.

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news

Subscribe