Release and Iteration Planning CT-AT Practice Questions (Page 2)

Questions 6–10

1. 6foundation · easy

   During release planning, the development team's primary responsibility is to:

   • AProvide estimates and technical feasibility input
   • BApprove the release budget
   • CDefine the business priorities for the release
   • DFacilitate the release planning meeting
   Reveal Solution Discussion Select an answer first
2. 7foundation · easy

   Which technique is used during iteration planning to ensure the team commits to a feasible amount of work?

   • AVelocity-based estimation
   • BStory mapping
   • CCritical path analysis
   • DCapacity planning
   Reveal Solution Discussion Select an answer first
4. 8foundation · easy

   What is a typical output of release planning?

   • AA release plan with estimated timelines and scope
   • BA list of defects to be fixed in the next iteration
   • CA retrospective report with lessons learned
   • DA detailed task list for each developer
   Reveal Solution Discussion Select an answer first
5. 9expert · hard

   A team is in the middle of an iteration and discovers that a critical bug requires immediate attention, reducing their capacity for planned work. The product owner wants to add a new high-priority feature to the iteration. What should the team do to maintain the agile principle of continuous adaptation?

   • AAsk the product owner to decide which work to remove, without team input.
   • BAdd the feature without removing anything and work overtime to complete all work.
   • CRefuse to add the feature because the iteration backlog is committed.
   • DAdd the new feature and remove an equal amount of lower-priority work from the iteration backlog.
   Reveal Solution Discussion Select an answer first
6. 10expert · hard

   A company is planning a release for a regulatory compliance feature that must be delivered by a fixed date. The team's velocity is 25 points per iteration, and the feature is estimated at 100 points. The product owner wants to include additional non-critical features in the same release. Which approach best balances flexibility with stakeholder expectations?

   • AInclude all features and extend the release date to accommodate the full scope.
   • BCommit to the compliance feature and defer non-critical features to a later release.
   • CAsk the team to work overtime to deliver all features by the fixed date.
   • DRemove the compliance feature and deliver only the non-critical features.
   Reveal Solution Discussion Select an answer first