This glossary can be used as a reference book of Scrum-related terms. Not all terms are mandatory in Scrum, I have also added those that are commonly used in Scrum.
Burndown chart: showing the decrease of remaining work against time.
Burnup chart: showing the completed work compared with its total scope.
Daily Scrum (DS): is a 15-minute time-boxed event held each day for the Development Team to inspect the Sprint progress (towards the sprint goal) and adapt their daily work and the Sprint backlog.
Definition of Done (DoD): a shared understanding of expectations that the Increment must live up to in order to be releasable into production. It is managed by the Development Team.
Development Team: Role within a Scrum Team accountable for managing, organizing and doing all development work required to create a potential shippable Increment of the product every Sprint.
Emergence: the process of the coming into existence or prominence of new facts or new knowledge of a fact, or knowledge of a fact becoming visible unexpectedly.
Empiricism: The act of making decisions based on what is. By this, I mean that we do the best we can with what we have.
Forecast (of functionality): the selection of items from the Product Backlog a Development Team deems feasible for implementation in a Sprint.
Increment: Scrum Artifact that defines the complete and valuable work produced by the Development Team during a Sprint. The sum of all Increments forms a product.
Product Backlog (PBL): A Scrum Artifact that consists of an ordered list (priorities) of the work to be done in order to create, maintain and sustain the product. It is managed by the Product Owner.
Product Backlog Refinement (PBR): an activity in a Sprint through which the Product Owner and the Development Teams refine the Product Backlog items.
Product Owner: Role in Scrum accountable for maximizing the value of a product, primarily by incrementally managing and expressing business and functional expectations for a product to the Development Team(s).
Ready: a shared understanding by the Product Owner and the Development Team regarding the preferred level of description of Product Backlog items introduced at Sprint Planning.
Scrum: a framework to support teams in complex product development. Scrum consists of Scrum Teams and their associated roles, events, artifacts, and rules, as defined in the Scrum GuideTM.
Scrum Board: a physical board to visualize information (transparency) for and by the Scrum Team, often used to manage Sprint Backlog. Scrum boards are an optional implementation within Scrum to make information visible.
Scrum Master: Role within a Scrum Team accountable for guiding, coaching, teaching and assisting a Scrum Team and its environments in a proper understanding and use of Scrum.
Scrum Team: a self-organizing team consisting of a Product Owner, Development Team and Scrum Master.
Scrum Values: a set of fundamental values and qualities underpinning the Scrum framework; commitment, focus, openness, respect and courage.
Self-organization: the management principle that teams autonomously organize their work.
Sprint: The heart of Scrum is a Sprint, a time-box of one month or less during which a “Done”, useable, and potentially releasable product Increment is created.
Sprint Backlog: Scrum Artifact that is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal. The Sprint Backlog is a forecast by the Development Team about what functionality will be in the next Increment and the work needed to deliver that functionality into a “Done” Increment.
Sprint goal: is an objective that will be met within the Sprint through the implementation of the Product Backlog, and it provides guidance to the Development Team on why it is building the Increment.
Sprint planning: Scrum Event that is time-boxed to 8 hours, or less, to start a Sprint. It serves for the Scrum Team to inspect the work from the Product Backlog that’s most valuable to be done next and design that work into Sprint backlog.
Sprint Retrospective: Scrum Event that is set to a time-box of 3 hours, or less, to end a Sprint. It is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.
Sprint review: Scrum event that is at most a four-hour meeting for one-month Sprints. For shorter Sprints, the event is usually shorter. It is 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 collaborate about what was done in the Sprint.
Stakeholder: a person external to the Scrum Team with a specific interest in and knowledge of a product that is required for incremental discovery. Represented by the Product Owner and actively engaged with the Scrum Team at Sprint Review.
Technical debt: or code debt, but can be also related to other technical endeavors) is a concept in software development that reflects the implied cost of additional rework caused by choosing an easy (limited) solution now instead of using a better approach that would take longer.
Velocity: is a measure of the amount of work a Team can tackle during a single Sprint and is the key metric in Scrum. Velocity is calculated at the end of the Sprint by totaling the Points for all fully completed User Stories.