Tag Info

One of the most common problems that I've faced is the role of the tester. Often times, teams/companies start to believe that an agile approach using TDD eliminates the need for testing. My first experience with it was when of my former teams was told that they were going to become an agile team. Agile Testing by Lisa Crispin and Janet Gregory helped me ...

The main challenge with any waterfall style testing is that you are increasing the time between the defect being introduced and the the defect being found, and the closer you can bring these points together, the cheaper the defect is to fix.
My recommendation would be that you split your testing and do some in the current iteration and some in the catch up, ...

I'd suggest you start by taking a look at some of the related questions and their answers, particularly this one and this one.
Also, if you don't have Crispin and Gregory's Agile Testing, get it.
Some things that I've found helpful include:
Test plans will still happen - but they tend to be much more lightweight and built as you test. Some tools support ...

Agile testing generally means the practice of testing software within the context of an agile workflow.
When testing in an Agile way, there are few, if any, rigid adherence's to requirements documents and checklists. The goal, instead, is to simply do whatever is necessary at any moment to satisfy a customer’s requests, replacing documentation with ...

Quite a few software projects have a tick-tock model of a feature version, then a stable version and I see this as similar on a smaller scail.
The key thing is not to test things that the devs know isn't really done but sort of works and is only pushed to testing because they've not got enough time. I don't think that really helps anyone.
The other thing ...