Burn-down chart: a chart showing the decrease of remaining work against time.
Burn-up chart: a chart showing the increase of a parameter, like value, against time.
Daily Scrum: a daily event, time-boxed to 15 minutes or less, to re-plan the development work during a Sprint. The event serves to plan the work for the next 24 hours based on the actual progress and update Sprint Backlog accordingly.
Definition of Done: the set of expectations on quality that a product Increment must exhibit to make it usable and releasable, which means fit for a release to the product’s users.
Development standards: the set of standards and practices that are identified as needed to create releasable Increments of product no later than by the end of a Sprint.
Developers (team of): the people accountable for the evolutionary development work needed to create releasable Increments during and no later than by the end of a Sprint. Also referred to as ‘Development Team’.
Emergence: the process of the coming into existence or prominence of unforeseen facts or knowledge of a fact, a previously unknown fact, or knowledge of a fact becoming visible unexpectedly.
Empiricism: the process control type in which decisions are based on observed results, experience and experimentation. Empiricism implements regular inspections and adaptations requiring and creating transparency. Also referred to as ’empirical process control’.
Forecast: the anticipation of a future trend based on observations of the past, like the selection of Product Backlog deemed deliverable in the current Sprint or in future Sprints (for future Product Backlog).
Impediment: any hindrance or obstacle that is blocking or slowing down the development work and cannot be solved through the self-organization of the team itself. Raised no later than at the Daily Scrum, the Scrum Master is accountable for its removal.
Increment: a candidate of releasable work that adds to and changes previously created Increments and–as a whole–forms a product.
Product (n): a tangible or non-tangible good or service providing immediate value to specific consumers (1); the outcome of specific actions or some defined process (2). Defines the span of Product Owner, Product Backlog and Increment.
Product Backlog: an ordered, evolving list of all work deemed necessary by the Product Owner to create, deliver, maintain and sustain a product.
Product Backlog refinement: the recurring activity in a Sprint through which granularity is added to future Product Backlog.
Product Owner: the person accountable for optimizing the value a product delivers, primarily by managing and expressing all product expectations and ideas in a Product Backlog.
Scrum (n): a simple framework for complex product development (1); a simple framework for addressing complex challenges (2); a simple framework that enables people to derive value from complex challenges (3).
Scrum Master: the person accountable for fostering an environment of Scrum by guiding, coaching, teaching and facilitating one or more Scrum Teams and their environment in understanding and employing Scrum.
Scrum Team: the combined accountabilities of Product Owner, (team of) Developers and Scrum Master.
Scrum Values: a set of 5 fundamental values and qualities underpinning the Scrum framework: commitment, focus, openness, respect and courage.
Self-design: the expression of self-organization where only the Scrum Team decides what skills are or are not needed and present within the team.
Self-management: the minimal expression of self-organization in Scrum, holding that only the Scrum Team decides who performs what work within a Sprint.
Self-organization: the process of people forming organized groups around problems or challenges without external work plans or instructions being imposed on them.
Sprint: an event that serves as a container for the other Scrum events, time-boxed to four weeks or less. The event serves getting a sufficient amount of work done, while ensuring timely inspection, reflection and adaptation at a product and strategic level. The other Scrum events are Sprint Planning, Daily Scrum, Sprint Review and Sprint Retrospective.
Sprint Backlog: an evolving plan of all work deemed necessary to achieve a Sprint’s goal.
Sprint Goal: a concise statement expressing the overarching purpose of a Sprint.
Sprint length: time-box of a Sprint, which is four weeks or less.
Sprint Planning: an event marking the start of a Sprint, time-boxed to eight hours or less. The event serves for the Scrum Team to inspect the Product Backlog considered most valuable at that time and design a selection from it, the forecast, into an initial Sprint Backlog against the Sprint Goal.
Sprint Retrospective: an event marking the closing of a Sprint, time-boxed to three hours or less. The event serves for the Scrum Team to inspect the Sprint that is ending in order to consider the way of working for the next Sprint.
Sprint Review: an event marking the closing of the development work of a Sprint, time-boxed to four hours or less. The event serves for the Scrum Team and its stakeholders to inspect the Increment(s), the overall progress and strategic changes in order to allow the Product Owner to update the Product Backlog so that it best reflects the current priorities.
Stakeholder: a person external to the Scrum Team with a specific interest in or knowledge of a product that is required for the further evolution of the product.
Time-box: a container in time of a maximum duration and potentially a fixed duration. In Scrum all events have a maximum duration, except for the Sprint itself which has a fixed duration.
Velocity: popular indication of the average amount of Product Backlog turned into an Increment of releasable product during a Sprint by a specific (composition of a) team.
Get new content delivered directly to your inbox.