Scrum is founded on empirical process control theory, or empiricism. Empiricism asserts that knowledge comes from experience and making decisions based on what is known. Scrum employs an iterative, incremental approach to optimize predictability and control risk. Three pillars uphold every implementation of empirical process control: transparency, inspection, and adaptation.
Scrum is not a process, technique, or definitive method. Rather, it is a framework within which you can employ various processes and techniques. Scrum makes clear the relative efficacy of your product management and work techniques so that you can continuously improve the product, the team, and the working environment. The rules of Scrum bind together the roles, events, and artifacts, governing the relationships and interaction between them.
Scrum tells values of commitment, courage, focus, openness and respect that provides the pillars of transparency, inspection, and adaptation and makes the team stronger.
The Agile SCRUM Structure:
The Scrum is very flexible and specifically defined to follow correctly. The Scrum introduces, Events and Artifacts to take place at right time and right place with the right person i.e. Scrum Team, Product Owner and the Scrum Master.
Scrum Master makes sure all the events, artifacts are taking place and all rules are being followed. The Scrum Master is responsible and makes sure that Scrum is understood and enacted by every team members.
Whereas the Product Owner is responsible and sole owner for maximizing the value of the product and the work of the Development Team. The Product Owner is the sole person responsible for managing the Product Backlog.
The Development Team consists of professionals who do the work. Development Teams are structured to organize and manage their own work. They are self-organizing. No one (not even the Scrum Master) tells the Development Team how to turn work into releasable and shippable product.
Events are one of the core part of Agile Scrum, these are used in Scrum to create regularity and to minimize the need for meetings not defined in Scrum. All events are time-boxed events, such that every event has a maximum duration. Though some of the events may end whenever the purpose of the event is achieved, ensuring an appropriate amount of time is spent without allowing waste in the process.
The events give the opportunity to inspect and adapt the things for further betterment. Events provides much more flexibility to projects run smoother.