The Scrum Master is a pivotal role in Scrum framework. They serve as a facilitator for both the product owner and the team. They don't manage the team, but help to remove obstacles and distractions that stand in the way of the team achieving the goals of the sprint. They protect the team from external interferences and help them to reach consensus at each stage of development. The Scrum Master also helps to promote communication and cooperation between the team and the product owner, and encourages the team's self-organization and self-management.

The Product Owner is responsible for optimizing the value of the product resulting from the work of the development team. They manage the product backlog and ensure the team understands items in the product backlog to the level needed. They are responsible for the product's business and functional requirements and for deciding the release date and content. They have the power to accept or reject work results, and they own the profitability of the product (ROI).

The Scrum Team is composed of the Scrum Master, Product Owner, and the development team. The team's tasks are determined during a sprint in which they select product backlog items, transform them into the 'Definition of Done', and design and deliver incrementally viable products. The development team in Scrum is self-organizing and cross-functional. They are also responsible for any failures or successes of the project.

Sprints are fixed-length iterations, which usually last between one to four weeks, in which the team creates a potentially shippable product increment. They include the planning of tasks, the development of those tasks and the review and retrospective when those tasks are complete. Sprints help in time management, maintaining product consistency and meeting deadlines.

The Product Backlog is an ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made to the product. The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering. Backlog items have the attributes of description, order, estimate and value. It makes clear what the development team should be working on and their respective priorities. It also provides a way for stakeholders to influence and see the development process.

The Daily Scrum is a short, time-boxed event for the Scrum Team to sync. Often held at the start of each day, typically lasting 15 minutes, its key purpose is to inspect progress toward the Sprint Goal and adapt the day’s work accordingly. The Scrum Team, together with the Scrum Master, discusses the work that was done the previous day, the plan for the forthcoming day, and identifies any obstacles that might impede progress. Despite its centrality for coordination and collaboration, the daily Scrum is not a status meeting, but a ceremony to make new commitments in the sprint backlog in response to change.

The Sprint Review is a feedback-driven meeting at the end of each Sprint where the Scrum Team and stakeholders collaborate on what was done in the Sprint. Demonstrations of the new features help to inspect, adapt, and potentially adjust the Product Backlog. The product increment is presented and everyone involved is encouraged to give feedback, which is then used by the Product Owner to update the backlog. This review maintains transparency, alignment, and promotes continuous improvement.

The Sprint Retrospective is the last event of the Sprint, which allows the Team to look back on how well Scrum was implemented, and create a plan for improvements for the next Sprint. They inspect the people, relationships, processes, and tools, and discern what went right, what went wrong, and how they can implement improvements in their work. This promotes a culture of continuous process improvement and enables teams to adjust and become more effective in delivering high-quality products.

Scrum Artifacts represent work in various stages of development or value. They include the Product Backlog, the Sprint Backlog, and the Product Increment. Artifacts are designed to maximize transparency of key information. They give everyone a shared understanding of everything involved in delivering successful outcomes and create visibility into the work done, work in-progress, and future work. Each artifact is inspected and adapted to support ‘Done’ outcomes.

The Scrum Values are core principles that guide the decision-making process and ensure alignment in a scrum team. They include Commitment, Courage, Focus, Openness and Respect. Each of these values plays a key role in the way the team operates. Commitment refers to the dedication of the team to achieve the goals of the project. Courage is required to tackle difficult issues and make tough decisions. Focus is about paying attention to what’s most important and prioritizing tasks effectively. Openness pertains to transparency and honest communication within the team. Respect involves recognizing and appreciating the abilities and contributions of all team members.

Scrum Events or Ceremonies are staple activities that happen at regular intervals throughout a Scrum project. Aside from the already mentioned Daily Scrum, Sprint Review, and Sprint Retrospective, the Sprint Planning Meeting is equally important. During this meeting, the team discusses the product backlog items for the incoming sprint and plans how to accomplish them. Scrum events are time-boxed, meaning they have a maximum duration to ensure efficiency.

The Definition of Done (DoD) is a clear and concise list of requirements that a software increment must meet to be considered complete. This agreed-upon criteria ensure that everyone on the team has the same understanding of what it means for work to be complete and ensures that the quality is consistent. The DoD is used to assess when work is complete on the product backlog items and the increment of product.

Product Increment is the sum of all the Product Backlog items completed during a Sprint and all previous Sprints. Ideally, the product increment should be in a usable condition regardless of whether the Product Owner decides to actually release it. It’s a step toward a vision or goal, providing tangible proof of progress and ensuring that a potentially useful version of the product is always ready if needed.

User Stories are a tool used in Agile development to capture a description of a feature from an end-user perspective. The user story describes the type of user, what they want, and why. A user story helps to create a simplified description of a requirement, providing a clear understanding of who, what, and why in terms of a needed feature. These are typically written by the product owner and are part of the product backlog. They provide a user-focused framework for daily work, which helps developers stay focused on why what they're doing matters.