A chart which shows the amount of work which is thought to remain in a backlog. Time is shown on the horizontal axis and work remaining on the vertical axis. As time progresses and items are drawn from the backlog and completed, a plot line showing work remaining may be expected to fall. The amount of work may be assessed in any of several ways such as user story points or task hours. Work remaining in Sprint Backlogs and Product Backlogs may be communicated by means of a burn-down chart.

A chart which shows the amount of work which has been completed. Time is shown on the horizontal axis and work completed on the vertical axis. As time progresses and items are drawn from the backlog and completed, a plot line showing the work done may be expected to rise. The amount of work may be assessed in any of several ways such as user story points or task hours. The amount of work considered to be in-scope may also be plotted as a line; the burn-up can be expected to approach this line as work is completed.

The Daily Scrum is a 15-minute event for and by the Developers of the Scrum Team, taking place each working day of the Sprint. The Daily Scrum is for realignment between Developers on the Sprint work progress and plan adjustments. The purpose of Daily Scrum is for the Developers to inspect progress toward the Sprint Goal, highlight any impediments, and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work. Developers only highlight the impediments, challenges, and problems during the Daily Scrum, as this is not a problem-solving event. The Daily Scrum improves team collaboration and enables faster decision-making. To simplify complexity, the Daily Scrum is held at the same time and place.

“Definition of Done” describes the quality goal/commitment for the
Increment. The Definition of Done is a formal description of the state of the Increment when it meets the appropriate quality measures/standards required for the product in that context.

An Increment is created when a Product Backlog item fulfills the Definition of Done. The Definition of Done promotes transparency by presenting everyone with a shared understanding of the work accomplished as part of the Increment. A Product Backlog item cannot be released or even presented at the Sprint Review if it does not fulfill the Definition of Done.

Any Scrum Team member dedicated to creating any aspect of a useable increment each Sprint, regardless of their skillset or capabilities. “Developers” is a joint accountability, not an individual.

"Done" refers to the state of the Increment when it meets the quality measures required for the product to be usable (at a minimum). While referring to Increment in Scrum, “Done” means “Usable” at a minimum. If something can’t be used, it’s not done yet.

Evolution. The process through which new facts or understanding about a fact appear or become evident unexpectedly. Scrum supports emergent requirements, architecture, design, and all supporting processes and team structures.

The concept that all knowledge comes through experiences and observations. Empiricism in Scrum refers to the belief that addressing complex issues or performing complex tasks can only be accomplished through an empirical approach rather than overly depending on preconceived plans. In complex environments, what will happen is unknown. Only what has already happened may be used for forward-looking decision-making. Forecast: the selection of items from the Product Backlog Developers deems feasible for
implementation in a Sprint.

An Increment is a thing of value, a working piece of the product that can be used. An Increment is some concrete stepping-stone toward the Product Goal. Each Increment is an improvement in the value of the product. The product is the sum of all Increments. Increment raises transparency about work Done or value created through a working (usable and valuable) product. An Increment is created when a Product Backlog item fulfills the Definition of Done. Each Sprint requires at least one Increment to enable Empiricism or the feedback loop.

An ongoing activity or set of activities to prepare the top-order items in the Product Backlog for selection in the next Sprint Planning. Through regular Product Backlog Refinement, the Product Owner and Developers enhance the transparency and level of detail in the Product Backlog. Product Owner: Product Owner is the Product Success Owner. In Scrum, this accountability is responsible for maximizing a product's value by progressively managing and optimizing the Product Backlog while managing the expectations of the product’s stakeholders. Like the Captain of a Sports Team, the Product Owner steers the team toward product success and decides where the product should be heading.