The Development Team comprises of professionals who do the work of delivering a potentially releasable Increment of 'Done' product at the end of each Sprint. A 'Done' increment is required at the Sprint review. Only members of the Development Team create the Increment. They are structured and empowered by the organization to organize and manage their own work.

The Scrum Master is key to utilizing the Scrum framework correctly. They serve as a facilitator for both the Product Owner and the development team, making sure the team adheres to Scrum theory, practices, and rules. The Scrum Master helps the team to understand the need for clear and concise Product Backlog items. They work towards removing any obstacles that the development team may be facing in order to help them achieve their sprint goals. Notable for being a servant-leader, the Scrum Master fosters an environment where the team can be most productive and nurtures the team’s ability to self-organize.

Stakeholders in Scrum are anyone with an interest in the project. They could be customers, vendors, executives, sponsors, among others. Stakeholders don't directly participate in the Scrum, but they significantly influence it by providing feedback, financial support, and key inputs. Keeping Stakeholders engaged is crucial, as their input informs the direction of the project and the value it delivers. Stakeholders typically work closely with the Product Owner to help shape the project’s vision and goals.

Scrum relies on transparency. Decisions to optimize value and control risk are made based on the perceived state of the artifacts. To the extent that transparency is complete, these decisions will be better, benefiting the project as a whole. Transparency of artifacts means that the artifacts – including Product Backlog, Sprint Backlog, and Increments - are open and visible to all, and also that common language is used to describe them. This shared understanding is vital to the Scrum Team’s and stakeholders' success.

Expected to bring about a potentially releasable Increment of 'Done' product at the end of each Sprint, the Scrum Team is self-organizing and cross-functional, implying that it is in full control of its work and that it has all the competencies required to accomplish the work without depending on others not part of the team. It optimizes flexibility, creativity, and productivity.

Scrum artefacts represents work or value. They are designed to maximize transparency of key information. Key elements of Scrum Artefacts include Product Backlog, Sprint Backlog, and Increment. They are explicitly identified during the Scrum process to give a formal identity to often-understated key elements.

Sprint Planning is an event in Scrum that defines what can be delivered in the upcoming Sprint and how that work will be achieved. Sprint Planning answers the following: What can be delivered in the Increment resulting from the upcoming Sprint? How will the work needed to deliver the Increment be achieved? The input to this meeting is the Product Backlog, the latest product Increment, projected capacity of the Development Team during the Sprint, and past performance of the Development Team.

The Product Owner in Scrum is responsible for the maximization of the value of the product and the work of the development team. This role frequently interacts with stakeholders and the development team to ensure the goals are clearly understood. The Product Owner is the sole person responsible for managing the Product Backlog which includes activities like backlog items, ordering them, and ensuring it is visible and clear. This role requires a deep understanding of the business, market, customer perspective and the vision for the product. They have to be technical enough to understand the feasibility and challenges of execution while managing stakeholders' expectations.

Scrum describes four formal events for inspection and adaptation, as prescribed by the Scrum Guide. These are the Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. These events are time-boxed events, such that every event has a maximum duration to provide enough time to meet the goal, but ensuring efficiency. These events enable transparency, inspection and adaptation on a regular basis. They are critical elements within Scrum aimed at providing clear roles, artefacts, rules, and support to the development teams in managing dynamic and complex development scenarios.