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.

A well-recognized challenge when merging traditional project management with Agile approaches is the use of different terminology, making option B the correct answer. Agile Foundation materials highlight that traditional project management and Agile have evolved from different perspectives, each with its own language, concepts, and assumptions. When these approaches are combined within the same organization or project, misunderstandings often arise due to terminology differences rather than fundamental conflicts in intent.
Traditional project management commonly uses terms such as scope, milestones, deliverables, baselines, and change control, while Agile uses concepts like backlog, iterations, increments, velocity, and value delivery. Even when the underlying goals are aligned, different terminology can create confusion among stakeholders, project managers, Agile teams, and senior leadership. This confusion may lead to misaligned expectations, incorrect reporting, or resistance to Agile practices, as people may interpret the same words differently or assume conflicting meanings.
Option A, lack of clear processes, is generally not a common issue because both project management and Agile provide structured approaches, albeit in different forms. Option C, lack of guidance at the project level, is also not accurate, as Agile Foundation guidance increasingly addresses how Agile can operate at team, project, and organizational levels. Option D, the use of a flexible framework, is actually a benefit of Agile rather than a challenge.
Agile Foundation documents emphasize that overcoming terminology differences requires education, shared understanding, and alignment rather than choosing one approach over the other. By establishing a common language, clarifying roles and expectations, and focusing on value delivery rather than labels, organizations can successfully integrate Agile ways of working with project management governance. Addressing terminology differences early helps reduce friction, improves collaboration, and enables a more effective hybrid or Agile-informed project environment.