QuestionQ43

VerifiedContinuous Improvement

Your TAS has operated successfully on a Windows/GUI-based SUT for several years. To maintain business as usual, the SUT has changed only minimally during that time, with six-monthly waterfall releases delivering minor enhancements and bug fixes.

The TAS has remained completely unchanged throughout this period. The current SUT project will use Scrum to deliver a more modern, competitive user interface. It is at the release-planning stage, with an agreed release backlog and an outlined set of sprints.

The shift from long waterfall releases to shorter sprints has prompted a review of the current TAS to ensure that it is robust and fully optimized for the timescale challenges of the new project.

What two steps would be BEST to undertake during the review?

Explanation

A test automation solution that has been stable for years under a slow six-monthly waterfall cadence is typically optimized for infrequent, large regression runs rather than for the rapid, incremental feedback that Scrum sprints demand. The review therefore needs to focus on whether the TAS's test data management and environment/configuration management can be refreshed quickly and repeatably for each sprint, and whether the test execution and adaptation layers of the architecture can keep pace with much more frequent builds and smaller, iterative increments of the new UI. These are the dimensions of a TAS that most directly determine whether automation can deliver timely feedback within a sprint timebox, which is the central risk introduced by moving from long waterfall releases to short sprints.

Community Discussion

No comments yet. Be the first to start the discussion!