Glossar-Begriff: T206 Modernes Projektmanagement

A short description of a requirement from the user’s perspective, often written as “As a [role], I want [goal], so that [benefit].”

The person accountable for establishing Scrum and helping the team and the organization work effectively with it.

The person accountable for maximizing the value of the product, mainly by managing and ordering the product backlog.

An ordered list of everything that might be needed to improve the product; the single source of work for the Scrum team.

A fixed-length iteration of one month or less in which a Scrum team turns backlog items into a usable increment.

A lightweight agile framework in which a small team delivers value in fixed-length iterations called sprints, with three accountabilities, five events and three artifacts.

An iterative approach that delivers results in short cycles, collects feedback early and often, and adapts the plan as the team learns. Also called adaptive project management.

A short declaration written in 2001 by 17 software practitioners, stating four values and twelve principles for adaptive, collaborative development.

A development model in which every specification and design level on the left side of a “V” is paired with a matching test level on the right side.

A sequential approach in which each phase (for example requirements, design, implementation, testing, operation) must be completed before the next one starts.