A manager tells a team that being Agile means it should stop producing any documentation. What is wrong with this instruction?
ISTQB Agile Tester โ Question Bank
ISTQB_CTFL_ATReady to test yourself?
A timed, blueprint-proportional exam drawn fresh from this bank โ with a per-domain score report.
๐ Free preview: showing 10 of 120 questions. Unlock the full bank โ every question, explanation, and reference.
Unlock all 120 questions โ10 questions across 3 topics. Choose an answer for each question, then check it to see the correct answer and explanation.
Filter by topic
All 10 questions
Agile Software Development
8 questions in topicThe fundamentals of Agile software development including the Agile Manifesto's values and principles, the whole-team approach, and early and frequent feedback; and aspects of Agile approaches covering Scrum, Kanban and Extreme Programming, collaborative user story creation, retrospectives, continuous integration, and release and iteration planning.
A Scrum master assigns tasks to individual team members each morning at the stand-up. What is the problem?
A team holds retrospectives but the same impediments appear in every one. What does this most likely indicate?
A team commits to more work each iteration than it completes, and the shortfall grows. Management responds by asking for firmer commitments. Why will this not work?
Developers on a team work on separate long-lived branches, merging near the end of each iteration. Testing is repeatedly compressed into the final two days. Which change addresses the root cause?
A Kanban team raises its WIP limits whenever a column becomes blocked, so work keeps flowing. What is the consequence?
A team is told its velocity must increase by 20% next quarter. What is the predictable outcome?
A product owner is unavailable for most of the iteration and answers questions by email within two or three days. What is the principal effect on the team?
Fundamental Agile Testing Principles, Practices and Processes
2 questions in topicThe differences between testing in traditional and Agile approaches including test activities, work products, test levels, and testing and configuration management; the status of testing in Agile projects covering communication of test status and managing regression risk; and the role and skills of a tester in an Agile team.
A team reports test status only in a document circulated at the end of each iteration. What is the weakness?
A tester says they cannot start until the developers have finished coding all the stories. What is wrong with this position?