Answer : A
Scrum is fundamentally based on Empiricism, also referred to as Empirical Process Control. This means that Scrum recognizes that complex work, such as software development, cannot be fully understood or predicted upfront. Instead, decisions are made based on experience, observation, and evidence, forming a continuous closed feedback loop.
Empirical Process Control rests on three pillars: Transparency, Inspection, and Adaptation. Scrum provides a structured framework of roles, events, and artifacts that explicitly support and reinforce each of these pillars.
Transparency
Transparency ensures that all significant aspects of the process and product are visible to those responsible for the outcome. In Scrum, transparency is created through clearly defined artifacts such as the Product Backlog, Sprint Backlog, and Product Increment, each governed by a shared Definition of Done. Scrum Events further enhance transparency by creating regular opportunities to share progress, challenges, and current state. Without transparency, inspection would be misleading and ineffective.
Inspection
Scrum prescribes frequent and regular inspection of both the product and the process. Each Scrum Event serves as an inspection point:
The Daily Scrum inspects progress toward the Sprint Goal,
The Sprint Review inspects the Increment and adapts the Product Backlog,
The Sprint Retrospective inspects the team's ways of working.
These inspections are intentionally timeboxed and lightweight to avoid excessive overhead while still enabling timely feedback.
Adaptation
Inspection is meaningful only if it leads to adaptation. Scrum explicitly enables adaptation by allowing changes to plans, processes, and backlog content based on what is learned. The Sprint Backlog may be adapted during the Sprint, the Product Backlog is adapted after the Sprint Review, and team practices are adapted following the Sprint Retrospective.
Closed Feedback Loop
Together, transparency, inspection, and adaptation form a closed feedback loop. Scrum's short iterations (Sprints) ensure that learning occurs frequently, enabling the Scrum Team and stakeholders to respond quickly to change, reduce risk, and improve outcomes over time.
All Official Question Types