Scrum PO Zertifizierung

A big requirement with low level of detail which cannot be developed within one iteration (due to missing details or size)

A feature is a service provided by the system or product that addresses one or more user needs.

A piece of working product (mostly software) that adds new functionality / value to previously created Increments. The sum of all Increments forms the product. An Increment typically is the result of a Sprint.

Two of the three Scrum pillars – usually used together. Basis for the retrospective meeting

Describes a process for generally multiple repeating the same or similar actions for approaching a solution or goal.

Specific technique or agile estimation to avoid anchoring and reveal the different assumptions of the involved people

An ordered list of the work to be done in order to create, maintain and sustain a product. Managed by the Product Owner.

One entry (requirement) of any kind in the Product Backlog.

The activity in a Sprint through which the Product Owner and the Development Team add granularity to the Product Backlog.

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).

A Potentially Shippable Product is the sum of the Product Backlog Items delivered each Sprint.

A container (planning/development/releasing) for a bigger timeframe than a sprint (usually 3 months)

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.

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.

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. [Servant Leader]

A self-organizing team consisting of a Product Owner, Development Team and Scrum Master.

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.

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.

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.

Time-boxed event of 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.

Time-boxed event of 3 hours, or less, to end a Sprint. It serves for the Scrum Team to inspect the past Sprint and plan for improvements to be enacted during the next Sprint.

Time-boxed event of 4 hours, or less, to conclude the development work of a Sprint. It serves for the Scrum Team and the stakeholders to inspect the Increment of product resulting from the Sprint, assess the impact of the work performed on overall progress and update the Product backlog in order to maximize the value of the next period.

Story Points are an artificial measure for the size of a user story (requirement). They consist out of effort, complexity and risk for the implementation and are much more than the usual effort estimation.

Optional form of requirements which are a good practice in agile development. Uses the format: "As [role] I want [what] to achieve which [benefit]"

An optional, but often used, indication of the average amount of Product Backlog turned into an Increment of product during a Sprint by a Scrum Team, tracked by the Development Team for use within the Scrum Team.