ISTQB Exam ISTQB-Agile-Public Topic 1 Question 16 Discussion

Actual exam question for ISTQB's ISTQB-Agile-Public exam

Question #: 16
Topic #: 1

You are working on an Agile project and have been asked to implement exploratory testing for the current sprint. Which one of the following is a correct approach to adopt?

SELECT ONE OPTION

AAllocate independent testers to design exploratory tests using test charters in time boxed sessions. Plan to run all sessions in parallel with each session lasting more than 5 hours.

BAsk experienced testers to prepare test charters for time boxed sessions lasting no more than 2 hours. Tests should be designed and executed within each session using heuristics, creativity and intuition.

CAsk experienced testers to try and find new defects by using the system without the constraint of documentation and tools.

DUse testers who have not been involved in the sprint to write new test cases from the user stories. These test cases are then executed in a time boxed session for the sprint.

Show Suggested Answer

Suggested Answer: C

Risk-based testing is a strategic approach to testing that prioritizes testing activities based on the level of risk associated with various features or components of the software. In Agile development, this approach aligns well with the iterative and incremental nature of Agile methodologies. During both release and iteration planning, Agile teams assess and prioritize work based on risk, value, and other factors. This double layer of risk analysis allows teams to focus their testing efforts more effectively on areas that pose the greatest risk to the project's success, thereby enhancing the quality and reliability of the deliverables. This approach is consistent with Agile principles, which emphasize adaptability and the delivery of value to the customer.

by Virgilio at Jul 09, 2024, 03:43 AM

Limited Time Offer

25%

Off

Get Premium ISTQB-Agile-Public Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Erinn

10 months ago

Option C is the way to go. Agile's iterative nature actually makes risk-based testing more effective. It's like a superhero team-up, but with bugs instead of villains.

upvoted 0 times

...

Sophia

10 months ago

I'm going with B. Identifying risks through user stories is a great way to implement risk-based testing in Agile. This option seems the most logical to me.

upvoted 0 times

Novella

9 months ago

Definitely, it ensures that testing efforts are prioritized based on the potential impact of risks on the project.

upvoted 0 times

...

Lorriane

9 months ago

Agreed, it helps in focusing testing efforts on areas that pose the highest risk to the project.

upvoted 0 times

...

Kiley

9 months ago

I think B is the correct option too. It makes sense to identify risks through user stories in Agile development processes.

upvoted 0 times

...

Rosendo

10 months ago

D is the correct answer. Risk-based testing doesn't work well in Agile, where each iteration has a limited scope. How can you assess risks properly in such a short time frame?

upvoted 0 times

Santos

9 months ago

I agree with you, C seems to make more sense in the context of Agile development processes.

upvoted 0 times

...

Dahlia

10 months ago

I see your point, but I still believe C is the correct answer. Risk-based testing fits well in Agile development processes because risks are analyzed twice - during release and iteration planning.

upvoted 0 times

...

Nicholle

10 months ago

But D is the correct answer. Risk-based testing doesn't work well in Agile, where each iteration has a limited scope.

upvoted 0 times

...

Ceola

10 months ago

I think B is the correct answer. Risk-based testing fits well in Agile development processes because risks are easy to identify when the work is divided into user stories.

upvoted 0 times

...

Sherell

11 months ago

I see your point, Shay. I also think C is the correct answer because it aligns with Agile principles.

upvoted 0 times

...

Shay

11 months ago

But in Agile, risks are constantly changing, so it makes sense to analyze them during release and iteration planning.

upvoted 0 times

...

Lindsey

11 months ago

I agree with Jamie. Option C is the correct answer. Risk-based testing is a perfect fit for Agile, as it allows teams to focus on the most important areas.

upvoted 0 times

...