The Latest

Conceptually, requirements management is about bringing products to market faster, improving team efficiency, and catching requirements defects earlier in the development process. It's these potential benefits that explain why 67 percent of teams said they will use or plan to use a collaborative requirements management solution in the next year, based on a recent "State of Requirements Management" survey.

Few things are more rewarding than working in a job that you love.

Kay Johansen has collected a list of "Top Ten Reasons to Love Agile Testing", which she's shared with the agile-testing mailing list.  It's inspirational and motivating to hear people who are passionate about their work talk about why they love their jobs.

Continuous Integration build tools are great: they help us ensure our product works after every commit, keep historical data and metrics, build our product for all target environments, and do many more useful things. But there's one key aspect that often gets overlooked: They're fun.

While there may be many ways to design a testing automation system, sqaMethods' goal has always been to deliver a solution that is easy, modular and where testers can create automation scripts that mimic the format of the manual test. This paper explains how we go about designing an automation system with the right level of abstraction and functionality.

It's impossible to pin down a universal definition of the term "change management," but what about at the business level? By incorporating executives and senior managers, key employees who are known for driving real change, perhaps we reach a more agreeable single definition.

One of the practices recommended by Extreme Programming (XP) is to keep a ten-minute build.  Kent Beck and Cynthia Andres write in Extreme Programming Explained (Second Edition): "Automatically build the whole system and run all of the tests in ten minutes.  A build that takes longer than ten minutes will be used much less often, missing the opportunity for feedback."

So what do you do when your build takes longer than ten minutes? 

Managers often use metrics to help make decisions about the state of the product or the quality of the work done by the test group. Yet, measurements derived from bug counts can be highly misleading because a "bug" isn't a tangible, countable thing; it's a label for some aspect of some relationship between some person and some product, and it's influenced by when and how we count ... and who is doing the counting.