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

Questions 26–30

1. 26foundation · easy

   What is the purpose of aligning test processes between agile and non-agile teams?

   • ATo ensure consistency in test documentation, terminology, and quality expectations.
   • BTo make all teams follow the same development lifecycle, such as Scrum or Waterfall.
   • CTo eliminate the need for separate test plans for each team.
   • DTo ensure that all testing is performed by a single centralized team.
   Reveal Solution Discussion Select an answer first
2. 27expert · medium

   An agile team is developing a feature that requires a test environment that is managed by a non-agile operations team. The operations team has a change management process that requires a two-week notice for any environment changes. The agile team needs the environment configured differently for each sprint. What is the most effective way to manage this dependency?

   • APlan all environment changes at the beginning of the quarter and submit them in advance.
   • BAsk the operations team to prioritize the agile team's environment requests and process them within 24 hours.
   • CNegotiate a standing agreement with the operations team that allows for pre-approved, self-service environment changes within a defined scope.
   • DHave the agile team create their own test environments using cloud resources, bypassing the operations team.
   Reveal Solution Discussion Select an answer first
4. 28application · medium

   An organization has agile teams using behavior-driven development (BDD) with Gherkin scenarios, while the non-agile test team uses manual test scripts in a traditional format. The non-agile team often misunderstands the agile teams' automation results. What strategy would best align test processes between the teams?

   • ACreate a separate test management tool for the non-agile team to track their manual tests independently.
   • BHave the agile teams provide detailed step-by-step reports of their automation runs to the non-agile team.
   • CConvert the non-agile team's manual test scripts into Gherkin scenarios and integrate them into the agile teams' automation framework.
   • DAsk the non-agile team to manually execute the agile teams' automated tests to verify results.
   Reveal Solution Discussion Select an answer first
5. 29foundation · easy

   What is an important characteristic of effective communication channels between agile and non-agile test teams?

   • AThey use formal documents only, to ensure traceability.
   • BThey are established only after a problem occurs, to avoid unnecessary overhead.
   • CThey are restricted to test leads only, to avoid information overload.
   • DThey are accessible to all relevant stakeholders and provide timely information.
   Reveal Solution Discussion Select an answer first
6. 30expert · medium

   An organization has agile teams that report test results in real-time via a CI dashboard, while the non-agile team produces detailed test reports at the end of each release. Management wants to compare the quality of different releases, but the agile teams' results are not directly comparable to the non-agile team's reports because they use different metrics. What is the most effective way to integrate test results to enable meaningful comparison?

   • AHave the agile teams stop reporting real-time results and instead produce end-of-release reports like the non-agile team.
   • BDefine a common set of quality metrics that both teams report on, such as defect density and test coverage, and have them report these in a consistent format.
   • CConvert the non-agile team's reports into the same format as the CI dashboard.
   • DAsk management to interpret the different metrics without integration.
   Reveal Solution Discussion Select an answer first