Agile Foundation guidance clearly identifies Scrum as an iterative and timeboxed approach to product delivery, making option A the correct answer. Scrum is built around fixed-length iterations called sprints, which are typically one to four weeks long. These timeboxes create a regular cadence for planning, development, review, and improvement, enabling teams to deliver usable increments of a product frequently and predictably.

Scrum emphasizes iterative delivery by breaking complex work into smaller, manageable pieces that can be completed within a sprint. Each sprint begins with planning, where the team selects work from the product backlog, and ends with a review and retrospective. This structure supports frequent inspection of both the product and the team’s way of working, allowing for continuous adaptation based on feedback and learning. Agile Foundation documents highlight that timeboxing is a key mechanism in Scrum, helping teams focus, limit work in progress, and reduce risk.

Option B, Kanban, is not timeboxed. Kanban focuses on continuous flow, visualizing work, and limiting work in progress rather than delivering in fixed iterations. Option C, the Agilometer, is an assessment tool used to evaluate suitability and risks of Agile adoption, not a delivery approach. Option D, Lean, is a broader philosophy focused on eliminating waste and optimizing value flow; while it can influence Agile delivery, it is not inherently iterative and timeboxed in the way Scrum is.

Agile Foundation materials stress that Scrum’s iterative and timeboxed nature supports transparency, predictability, and early value delivery. By delivering small increments regularly, teams can gather feedback early, reduce uncertainty, and adapt priorities as needs change. This makes Scrum particularly effective in environments where requirements evolve and learning is essential.