Specifications

I hear very often when coaching teams that, we are doing agile so we don't write specifications.

One of the most common misconceptions around agile testing is that you do not create any documentation. This is because the main principal working software for comprehensive documentation is often misinterpreted as "do not write documentation." They're missing the whole point of the agile manifesto, where there is value in the items on the right; however, we value the items on the left more.

Agile testing is striving for a learning process in which you can adapt to it through a software development process. The error in the waterfall procedure is in trying to specify everything from the beginning because we can't know everything from the start. The domain is too complex, and we need to break it down into chunks and start with the most important ones. Once we've done this, we will also have learned new things that will let us re-evaluate how to tackle...