Embracing and keeping up with change
Even when a product has reached a “good enough” state – the minimum viable product – and has met the Definition of Done, the Agile team must recognise that work is never really truly done, and that enhancements can still be made. It is not uncommon for Agile projects to be deep in technical debt, given the need to deliver the product increment in a fortnight. There is always room for improvement, and Agile knows this fact. It was designed to keep up with the ever-changing trends in market demands and technology.
Changes are therefore to be expected in Agile projects. Requirements could be revised, new tools could be introduced, and critical roadblocks could be identified mid-project. Even processes that were once working could become subject to change as improvements are made to other processes. The shorter time-boxes allow Agile teams to inspect and adapt the product and their processes, while their customer-centric nature allows them to get the data relevant for the project.
Transitioning to an Agile project is not an easy feat, but by understanding the above, testers will be a able to adjust accordingly and do what they were meant to do, along with the rest of the Agile team: build the product right, build the product well.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: