Scrum is a lightweight, iterative and incremental framework for managing complex work. It defines a flexible, holistic product development strategy where a development team works as a unit to reach a common goal. This framework challenges traditional sequential or 'Waterfall' project management because it emphasizes empiricism, agility, and team collaboration. There are three pillars that uphold every implementation of empirical process control: transparency, inspection, and adaptation. Scrum arranges work in cycles called Sprints, these are time-boxed iterations of one month or less, at the end of which the team should be in a position to deliver a potentially releasable Increment of 'Done' product.

Scrum recognizes three specific roles: Product Owner, Scrum Master, and Development Team. The Product Owner is responsible for maximising the value of the product; the Scrum Master is responsible for promoting and supporting Scrum and helping everyone understand and enact Scrum theory, practices, rules and values; and the Development Team does the work of delivering a potentially releasable Increment of 'Done' product at the end of each Sprint. These roles represent a team composed of multiple functional areas working in collaboration to deliver a product increment within each sprint.

Scrum's artifacts represent work or value to provide transparency and opportunities for inspection and adaptation.Artifacts defined by Scrum are specifically designed to maximize transparency of key information so that everybody has the same understanding of the artifact this includes: Product Backlog, Sprint Backlog, and Product Increment. The Product Backlog is an ordered list of everything that is known to be needed in the product; the Sprint Backlog is the set of Product Backlog items selected for the Sprint and a plan for delivering the product Increment; and the Increment is the sum of all the Product Backlog items completed during a Sprint and all previous Sprints.

Scrum prescribes four regular meetings to inspect and adapt the product, process, and progress: Sprint planning, Daily Scrum, Sprint Review, and Sprint Retrospective. Sprint Planning is intended to plan the Sprint, and the Sprint Goal, and how it will be achieved. Daily Scrum is a 15-minute meeting for the Development Team to synchronize activities and make plan for the next 24 hours. Sprint Review is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog. The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.

The Scrum Guide attaches explicit importance to the five values of commitment, courage, focus, openness, and respect. When these values are embodied by the team and lived by scrum team, they build trust among team members which is essential for the team to work effectively and deliver valuable product increments. These five values give direction to the work, behavior and actions. They tie directly to the concepts of empiricism and the way Scrum is structured.

The Product Backlog is a crucial element in Scrum methodology. It refers to a prioritized list of everything that is needed in the product and is the single source of requirements for changes to be made to the product. It's owned by the Product Owner, who is responsible for its content, availability, and ordering. The items can be features, functions, enhancements, or fixes. This dynamic artifact is never complete and evolves as the product and the surrounding environment evolves. It's essential for transparency and for providing a clear view of the work to be done.

The Sprint Backlog consists of items selected from the Product Backlog that the Team commits to complete during a Sprint. It's a forecast made by the team about what functionality will be available in the next increment. The Sprint Backlog makes visible all of the work that the Development Team identifies as necessary to meet the Sprint Goal. It offers flexibility for the Development Team to reorganize the work as necessary, and improves visibility by tracking the development progress.

The Sprint Goal is an objective set for the Sprint that can be met through the implementation of a chosen set of Product Backlog items. It provides guidance to the Development Team on why it is building an Increment. It creates focus and flexibility, provides a consistent direction, and encourages the team to work together rather than on separate initiatives. Also, it provides a clear aim for the team to strive towards over the Sprint, and a benchmark for reviewing the Sprint's outcome.

An Increment is the sum of all the Product Backlog items completed during a Sprint and all previous Sprints. It is a body of inspectable, done work that supports empiricism at the end of the Sprint. The Increment must be in a usable condition, regardless of whether or not the Product Owner decides to release it. It's important as it allows the Scrum Team and stakeholders to inspect what was done during the Sprint and to adapt the backlog for future Sprints.

The Definition of Done (DoD) is a clear and concise list of requirements that software must adhere to for the team to call it complete. It ensures transparency and quality. DoD is used to assess when work is complete on the product Increment. A shared understanding of done helps the team know how many Product Backlog items it can select during Sprint Planning, and when it is time to finish an ongoing Sprint. The Definition of Done provides clarity and ensures transparency, in terms of quality and completeness.