Coordinate Test Efforts Across Agile and Non-Agile Teams CT-ATLAS Practice Questions (Page 2)

Questions 6–10

1. 6application · medium

   A company has multiple agile feature teams that release independently every two weeks, and a separate non-agile system test team that runs a full regression suite once a month. The system test team frequently finds defects that agile teams have already fixed in their latest iterations, causing duplicate work and confusion. What is the most effective coordination strategy to address this challenge?

   • AAsk the agile teams to delay their releases until the system test team completes their monthly regression.
   • BCreate a shared defect-tracking tool so both teams can log and view defects in real time.
   • CHave the system test team run their regression suite on the latest integrated build from each agile team before the monthly cycle.
   • DInstruct the system test team to focus only on new features and skip regression testing.
   Reveal Solution Discussion Select an answer first
2. 7foundation · easy

   Which practice supports the alignment of test processes between agile and non-agile teams?

   • AAgreeing on a common set of test levels and entry/exit criteria.
   • BAllowing each team to define its own quality metrics without any cross-team review.
   • CUsing different defect severity scales for each team to reflect their context.
   • DHaving non-agile teams adopt agile ceremonies such as daily stand-ups.
   Reveal Solution Discussion Select an answer first
4. 8foundation · easy

   Which of the following is a typical coordination challenge when agile and non-agile test teams work together on the same product?

   • AAgile teams often deliver increments frequently, while non-agile teams may follow longer, phase-based cycles, causing mismatched timing of test readiness.
   • BNon-agile teams are not allowed to communicate with agile teams due to organizational policies.
   • CAgile teams do not perform any testing, so all testing must be done by non-agile teams.
   • DAgile teams always use automated testing, while non-agile teams always use manual testing, making it impossible to compare results.
   Reveal Solution Discussion Select an answer first
5. 9foundation · easy

   What is a key dependency between agile and non-agile test efforts that must be managed?

   • ANon-agile teams may need stable builds from agile teams to perform system testing.
   • BAgile teams always need test data from non-agile teams before they can write any test cases.
   • CNon-agile teams must wait for agile teams to finish all unit testing before starting any testing.
   • DAgile teams cannot run any tests until non-agile teams provide the test environment.
   Reveal Solution Discussion Select an answer first
6. 10application · medium

   A company has multiple agile teams that test independently, and a central non-agile test team that performs end-to-end testing. The central team often finds integration issues that could have been caught earlier. What coordination strategy would most effectively reduce these late integration defects?

   • ACreate a detailed test plan that is updated at the end of each release.
   • BAsk each agile team to perform their own end-to-end testing in isolation.
   • CIntroduce continuous integration and have the central team run end-to-end tests on every integrated build.
   • DHave the central team wait until all agile teams have completed their features before starting end-to-end testing.
   Reveal Solution Discussion Select an answer first