Scrum is a simple framework designed to help teams to generate value through cycles of adaptations based on empirical decisions. Its main philosophy is founded on empiricism and lean thinking, in which meaningful decisions are made based on experience and focus is made on the essential to reduce waste. The framework defines three pillars in order for that to occur: transparency, inspection and adaptation. Along side that, it also states that the best way to optimize inspection and adaptation is through an iterative and incremental approach to product development, called sprinting. (SCHWABER, 2020)

The framework says that a product should be develop through sum of increments giving enough space for inspections intended to provoke changes in solutions in order to reduce wasteful future maintenances whenever problems arrive. To optimize those adaptations, it defines an iteration, called sprint, with short duration for the development each of those product increments, in which teams will have the opportunity to inspect the results produced and processes used during the sprint, thus supporting empiricism. (SCHWABER, 2020)

The three pillars of transparency, inspection and adaptation has a clear dependency between one another within the framework. Scrum emphasizes an importance to adaptation, which in itself depends on inspection of what is produced and processes used. However no inspection are well made if not done on transparent information, given that inspection without transparency is wasteful and misleading (SCHWABER, 2020).

Scrum formalizes all information needed in the product development with three formal artifacts where important decisions are based on: the product backlog, sprint backlog and product increment. Scrum’s artifacts are designed to both represent work and maximize transparency, they are a source of truth for inspection and adaptation accessible to all members of the team, each containing a commitment to a goal to reinforce empiricism and provide measurement for progress. (SCHWABER, 2020)

Scrum also formalizes the cadence to which the team inspect and adapt the artifacts, the product and the process used within the sprint. It defines five formal events: the sprint, sprint planning, daily meetings, sprint review and sprint retrospective.
They are designed to enable the transparency required by the framework and to create regularity through a schedule for them to occur defined by the framework.
A Sprint in itself enables predictability when it has short duration and a precise goal.