Lernkarten

Karten 50 Karten
Lernende 16 Lernende
Sprache English
Stufe Andere
Erstellt / Aktualisiert 20.08.2020 / 30.09.2022
Lizenzierung Keine Angabe
Weblink
Einbinden
0 Exakte Antworten 31 Text Antworten 19 Multiple Choice Antworten
Fenster schliessen

What is a Burndown Chart?

A chart showing the evolution of remaining effort against time. Burndown charts are an optional implementation within Scrum to make progress transparent.

Fenster schliessen

Daily Scrum?

Daily, time-boxed event of 15 minutes, or less, for the Development Team to re-plan the next day of development work in order to achieve the Sprint Goal. Updates are reflected in the Sprint Backlog.

Fenster schliessen

What ist Definition of Done (DoD) ?

A shared understanding of expectations that software must live up to in order to be releasable into production.

Fenster schliessen

What is Definition of Ready (DoR)

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.

Fenster schliessen

What is a Developer?

Any member of a Development Team, regardless of technical, functional or other specialty.

Fenster schliessen

What is a Development Team ?

The role within a Scrum Team accountable for managing, organizing and doing all development work required to create a releasable Increment of product every Sprint. All work is called development.

Fenster schliessen

What is an Epic ?

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

Fenster schliessen

What is a Feature ?

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

Fenster schliessen

What is an Increment ?

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.

Fenster schliessen

What is Inspect & Adapt ?

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

Fenster schliessen

What is Iteration ?

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

Fenster schliessen

What is Planning Poker ?

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

Fenster schliessen

What is a 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.

Fenster schliessen

What is a Product Backlog Item ?

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

Fenster schliessen

What is a Product Backlog Refinement ?

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

Fenster schliessen

What is a 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).

Fenster schliessen

What is a Potentially Shippable Product Increment (PSPI) ?

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

Fenster schliessen

What is a Release ?

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

Fenster schliessen

What means 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.

Fenster schliessen

What is a 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.

Fenster schliessen

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

Fenster schliessen

What is a Scrum Team?

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

Fenster schliessen

What is a 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.

Fenster schliessen

What is a 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.

Fenster schliessen

What is a 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.

Fenster schliessen

What is a Sprint Planning

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.

Fenster schliessen

What is a Sprint Retrospective ?

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.

Fenster schliessen

What is a Sprint Review?

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.

Fenster schliessen

What is a Story Point ? 

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.

Fenster schliessen

What is a User Stories?

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