How To Test A System That Is Never Finished Introduction Agile Testing

My name is Nick Sewell and I work for Ivar Jacobson Consulting Ltd.as the European Managing Director.I have over twenty years’ commercial experience in the software industry–twelve of these ensuring that software teams deliver software successfully using a range of techniques.
In a fast-moving customer environment where requirements are changing all the time to support the user needs,the testing strategy has to be superagile.

For example,I have recently been working as a part of a team enhancing a large business critical information system that needs to be updated every six weeks to keep pace with an ever-changing variety of information sources and analytical needs.Traditional test approaches are not suitable in this kind of situation; the test strategy must be agile for the project to survive.
As we worked to develop and test the software, we needed to meet the challenges of:

keeping the relevant documentation up to date,

communicating the frequent changes to all members of the team,

ensuring that the changes are thoroughly tested,

ensuring that the changes don’t compromise or break the existing system,and

delivering a system that works and meets the customer needs every six weeks.

This case study identifies the issues faced by the project and discusses some of the solutions that were explored to address those issues,such as

developing the test cases alongside the requirements,

pairing testers and developers through an iteration,

ensuring that all the documentation was updated as we went along,

relaying information to the team by means of a daily Scrum,and

employing automated testing tools to assist with the testing load.

It concludes with a review of what parts of our testing strategy actually worked and what clearly didn’t.