ScrumGlossary Flashcards
Term: Burn-down Chart
a chart showing the evolution of remaining effort against time. Burn-down charts are an optional implementation within Scrum to make progress transparent.
Term: Burn-up Chart
a chart showing the evolution of an increase in a measure against time. Burn-up charts are an optional implementation within Scrum to make progress transparent.
Term: Daily Scrum
daily time-boxed event of 15 minutes, or less, for the Development Team to re-plan the next day of development work during a Sprint. Updates are reflected in the Sprint Backlog.
Term: Definition of Done
a shared understanding of expectations that software must live up to in order to be releasable intro production. Managed by the Development Team.
Term: Development Team
the role within a Scrum Team accountable for managing, organising and doing all development work required to create releasable Increment of product every Sprint.
Term: 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.
Term: Empiricism
process control type in which only the past is accepted as certain and in which decisions are based on observation, experience and experimentation. Empiricism has three pillars: transparency, inspection and adaptation.
Term: Engineering standards
a shared set of development and technology standards that a Development Team applies to create releasable Increments of software.
Term: Forecast (of functionality)
the selection of items from the Product Backlog a Development Team deems feasible for implementation in a Sprint.
Term: Increment
a piece of working software that add to previously created Increments, where the sum of all Increments -as a whole - form a product.
Term: Product Backlog
an ordered list of the work to be done in order to create, maintain and sustain a product. Managed by the Product Owner.
Term: Product Backlog refinement
the activity in a Sprint through which the Product Owner and the Development Team add granularity to the Product Backlog.
Term: Product Owner
the 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).
Term: 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.
Term: 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 Guide™.
Term: Scrum Board
a physical board to visualize information for and by the Scrum Team, often used to manage Sprint Backlog. Scrum boards are an optional implementation within Scrum to make information visible.
Term: Scrum Guide™
the definition of Scrum, written and provided by Ken Schwaber and Jeff Sutherland, co-creators of Scrum. This definition consists of Scrum’s roles, events, artifacts, and the rules that bind them together.
Term: Scrum Master
the 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.
Term: Scrum Team
a self-organizing team consisting of a Product Owner, Development Team and Scrum Master.
Term: Self-organization
the management principle that teams autonomously organize their work. Self-organization happens within boundaries and against given goals. Team choose how best to accomplish their work, rather than being directed by others outside the team.
Term: Sprint
time-boxed event of 30 days, or less, that serves as a container for the other Scrum events and activities. Sprints are done consecutively, without intermediate gaps.
Term: Sprint Backlog
an overview of the development work to realize a Sprint’s goal, typically a forecast of functionality and the work needed to deliver that functionality. Managed by the Development Team.
Term: Sprint Goal
a short expression of the purpose of a Sprint, often a business problem that is addressed. Functionality might be adjusted during the Sprint in order to achieve the Sprint Goal.
Term: Sprint Planning
time-boxed event of 1 day, 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.
