Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

ISTQB-CTFL Exam - Topic 3 Question 48 Discussion

Posted by Tresa on Jul 31, 2025 at 02:43 PM

Which of the following statements is true?

Suggested Answer: A

This answer is correct because in Agile software development, work product documentation, such as user stories, acceptance criteria, or test cases, tends to be lightweight and concise, as the focus is on working software and frequent communication rather than comprehensive documentation. Manual tests tend to be often unscripted, as they are often produced using experience-based test techniques, such as error guessing or exploratory testing, which rely on the tester's skills, knowledge, and creativity to find defects and provide feedback. Reference: ISTQB Foundation Level Syllabus v4.0, Section 3.1.1.2, Section 3.2.1.2


Get Premium ISTQB-CTFL Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
21 comments · newest first
ME
Mee 10 months ago
C seems off. Testing isn't exclusive to the first iterations in Agile.
MA
Mari 10 months ago
I disagree with B. Experience-based techniques can still be used in sequential models.
JE
Jerry 10 months ago
D is interesting, but I thought entry and exit criteria were more defined in V-model.
EA
Earnestine 10 months ago
Wait, are we really saying Agile doesn't document much? That sounds surprising!
GR
Gracia 11 months ago
A is spot on! Agile really focuses on lightweight documentation.
TH
Thersa 11 months ago
D sounds plausible since I've read about overlapping test levels in both Agile and V-models, but I can't quite recall the specifics about entry and exit criteria.
VE
Veronika 11 months ago
C seems off to me; I don't recall Agile dedicating the first iterations solely to testing. It’s more about continuous testing, right?
RH
Rhea 11 months ago
I feel like I've seen a question similar to B before, but I thought experience-based techniques could still be used in sequential models.
KE
Kelvin 12 months ago
I remember studying that Agile focuses on lightweight documentation, so I think A might be true, but I'm not entirely sure.
SU
Sue 12 months ago
Ugh, testing approaches are not my strong suit. I'm a bit lost on the differences between Agile and sequential development when it comes to testing. I'll have to read through the options carefully and try to eliminate the ones that don't sound right, but I'm not sure I have a clear strategy for this type of question. Guess I'll just have to do my best.
KR
Kris 12 months ago
Ah, I've got this one! In Agile, the documentation tends to be lightweight and the testing is more experience-based, as opposed to sequential models which are more systematic. Option A nails it - that's the true statement here. I feel confident about this one.
LE
Leonie 1 year ago
Hmm, this is a tricky one. I'm a bit confused about the differences between Agile and sequential development when it comes to testing. I know Agile is more iterative, but I'm not sure about the specifics around documentation and test techniques. I'll have to think this through carefully and try to eliminate the options that don't seem quite right.
MA
Magdalene 1 year ago
This question is asking about the differences between Agile and sequential development models when it comes to testing. I think the key is to focus on the characteristics of each approach - Agile tends to have lightweight documentation and more unscripted testing, while sequential models are more systematic. I'll need to carefully read through the options to determine which one best captures these differences.
JO
Jonelle 1 year ago
I'm not sure, but I think C could also be a valid option.
RA
Rana 1 year ago
I disagree, I believe the answer is A.
JO
Josphine 1 year ago
I think the answer is B.
CA
Casie 1 year ago
Option B is definitely true. Acceptance criteria should cover all the details about the data, including format, allowed values, and defaults.
MA
Marica 1 year ago
↳ replying to Casie
I agree, option B is correct. Acceptance criteria should definitely include details on data definitions.
EL
Elza 1 year ago
↳ replying to Casie
Acceptance criteria for user stones should focus on positive scenarios, while negative scenarios should be excluded
BE
Bettina 1 year ago
↳ replying to Casie
Acceptance criteria for user stories can include details on data definitions, for example by describing the format, allowed values, and default values for a data item
AN
Anika 1 year ago
↳ replying to Casie
User acceptance tests are usually automated and aim to verify the acceptance criteria for user stories
0/2000 characters

Save Cancel