Skip to content
DE
← All CTFL learning objectives

CTFL 5.1.2: Recognize how a tester adds value to iteration and release planning

K1

Syllabus section 5.1.2

4 original PrepBench practice questions for learning objective 5.1.2 of the CTFL 4.0 syllabus. Try the examples below and check each answer against its syllabus reference.

Practice questions

Question 1

Which activity do testers perform when they take part in iteration planning?

  1. Breaking user stories down into tasks, particularly testing tasks
  2. Defining and re-defining the product backlog for the coming release
  3. Refining larger user stories into a set of smaller user stories
  4. Determining the test approach and planning the testing for the release
Show answer
  • Correct answer: Breaking user stories down into tasks, particularly testing tasksBreaking stories into tasks, particularly testing tasks, is iteration planning.
  • Defining and re-defining the product backlog for the coming releaseDefining and re-defining the product backlog belongs to release planning.
  • Refining larger user stories into a set of smaller user storiesRefining larger stories into smaller ones belongs to release planning.
  • Determining the test approach and planning the testing for the releaseDetermining the test approach for the release belongs to release planning.

Testers involved in iteration planning participate in the detailed risk analysis of user stories, determine the testability of user stories, break user stories down into tasks — particularly testing tasks — estimate test effort for all testing tasks, and identify and refine the functional and non-functional aspects of the test object. The other three options are all release planning activities.

Syllabus section 5.1.2

Question 2

Which activity do testers perform when they take part in release planning?

  1. Determining the testability of the individual user stories in the iteration backlog
  2. Estimating test effort for all of the testing tasks in the current iteration
  3. Participating in the detailed risk analysis of the user stories in the iteration
  4. Writing testable user stories and acceptance criteria, and determining the test approach
Show answer
  • Determining the testability of the individual user stories in the iteration backlogDetermining the testability of user stories is an iteration planning activity.
  • Estimating test effort for all of the testing tasks in the current iterationEstimating effort for the iteration's testing tasks is an iteration planning activity.
  • Participating in the detailed risk analysis of the user stories in the iterationThe detailed risk analysis of user stories is an iteration planning activity.
  • Correct answer: Writing testable user stories and acceptance criteria, and determining the test approachWriting testable stories and determining the test approach are release planning.

Testers involved in release planning participate in writing testable user stories and acceptance criteria, participate in project and quality risk analyses, estimate the test effort associated with user stories, determine the test approach, and plan the testing for the release. The other three options are all iteration planning activities.

Syllabus section 5.1.2

Question 3

In iterative SDLCs, what distinguishes iteration planning from release planning?

  1. Iteration planning is carried out by the team, while release planning is carried out by management
  2. Iteration planning covers only test activities, while release planning covers all development work
  3. Iteration planning looks ahead to the end of a single iteration and its iteration backlog
  4. Iteration planning replaces the need to refine the product backlog during the release
Show answer
  • Iteration planning is carried out by the team, while release planning is carried out by managementThe syllabus distinguishes the two by horizon and backlog, not by who performs them.
  • Iteration planning covers only test activities, while release planning covers all development workBoth kinds of planning cover the work as a whole, not testing alone.
  • Correct answer: Iteration planning looks ahead to the end of a single iteration and its iteration backlogA single iteration's horizon and its iteration backlog.
  • Iteration planning replaces the need to refine the product backlog during the releaseRefining the product backlog is part of release planning and still takes place.

Release planning looks ahead to the release of a product, defines and re-defines the product backlog, may involve refining larger user stories into smaller ones, and serves as the basis for the test approach and test plan across all iterations. Iteration planning looks ahead to the end of a single iteration and is concerned with the iteration backlog.

Syllabus section 5.1.2

Original PrepBench practice material, not official exam questions or exam dumps. PrepBench is independent and is not affiliated with or endorsed by ISTQB®.

Glossary terms in this chapter

Practice chapter 5Take a CTFL mock exam