The Product Goal is a long-term objective for the Scrum Team. It describes the future state of the product which can serve as a target for the Scrum Team to plan against. The Product Goal is the direction for all the sprints and is derived from the product vision. The Product Goal is created and maintained by the Product Owner and is a commitment for a Product Backlog.

The Sprint Burndown is a graphical representation of work left to do versus time. The horizontal axis represents time, and the vertical axis represents work remaining, typically it is updated every day. The Sprint Burndown provides a simple view of the Sprint progress and typically includes a line showing work completed to give a graphical representation of the discrepancies between the ideal and the real, highlighting any problems.

The Product Backlog is an ordered list of everything 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. The Product Backlog evolves as the product and the environment in which it will be used evolves. The Product Backlog is dynamic; it constantly changes to identify what the product needs to be appropriate, competitive, and useful. As long as a product exists, its Product Backlog also exists.

The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and achieving the Sprint Goal. The Sprint Backlog is a forecast by the Developers of what functionality will be in the next Increment and the work needed to deliver that functionality into a 'Done' Increment. The Sprint Backlog is a plan with enough detail to understand changes in progress during the Sprint. The Developers modify the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint.

When a Product Backlog item or an Increment is described as 'Done', everyone must understand what 'Done' means. Although the Scrum Guide doesn't prescribe a single universal definition of Done, the understanding of what Done means should be consistent across the Scrum Team. Every Increment must meet the team's current definition of 'Done'. This ensures that the quality of work is high. Any one Product Backlog item can be 'Done' only when it fits into the Increment, thus the definition of 'Done' becomes part of the convention of the Scrum Team.

The Scrum Board is a visual tool that displays the progress of the Scrum team's work during a Sprint. It includes all the Product Backlog items being worked on, categorized into to-do, work in-progress, and done. This artifact promotes transparency and helps the team to track their progress towards the Sprint Goal. The Scrum Board is updated continuously throughout the Sprint by the development team to reflect the real-time state of their work.

The Sprint Review is an informal meeting held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed. During the Sprint Review, the Scrum Team and stakeholders discuss what was done in the Sprint, taking into account the market, potential capabilities, and timelines. The Product Backlog may also be adjusted to meet new insights. The presentation of the Increment is key to providing transparency and receiving feedback.

The Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog items. It provides guidance to the Development Team on why it is building the Increment and brings coherence to their work. The Sprint Goal is decided during Sprint Planning and gives the Team a way to collaborate towards a shared goal instead of perceiving the work to be done as a collection of separate Product Backlog items. Having a clear Sprint Goal gives direction and offers room for flexibility and creativity.

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. It is held after the Sprint Review and before the next Sprint Planning. The Sprint Retrospective is crucial to the principle of inspection and adaptation that are central to Scrum framework. Reflection on the process allows for the identification of strengths and weaknesses, and fosters continuous improvement.

The Product Owner is responsible for maximizing the value of the product resulting from work of the Development Team. The Product Owner is the sole person responsible for managing the Product Backlog. This includes clearly expressing Product Backlog items and Ordering the items to best achieve goals and missions. The Product Owner needs to ensure the development team understands items in the Product Backlog. The Product Owner may delegate certain responsibilities but remains accountable for the overall success of the product.