IREB RE@Agile Primer

• Basiert auf Lean Startup von Ries
• Verwandt mit Design Thinking, aber mit Fokus auf Entwicklung von Geschäftsideen, insbesondere mit schnellem und häufigem Feedback
• Der Produktentwicklungsansatz wird als „Build - Measure - Learn" (bauen, messen, lernen) bezeichnet, und der Schwerpunkt liegt dabei vor allem auf dem kontinuierlichen Lernen über die Bedürfnisse des Kunden. Mit Minimum Viable Product (MVP) ist sinngemäß eine Version eines neuen Produkts gemeint, die einem Team das Erfassen des maximal möglichen sogenannten validierten Lernens über Kunden bei geringstem Aufwand ermöglicht 

Minimum Viable Product (MVP) aus Lean Startup: Validiertes Lernen über den Kunden bei geringstem Aufwand.

Der Zweck eines Minimum Marketable Products (MMP) ist es, sofort Wert zu schaffen. Viele Produkte können bereits in einer einfachen „Version 1" genutzt werden, ohne dass diese Version alle gewünschten Funktionalitäten und Qualitäten umfasst; so erzielt das Produkt bereits Umsatz, mit dem die kontinuierliche Verbesserung (das sog. Continuous Improvement) des Produkts finanziert werden kann. 

The development capacity of a team in terms of the average amount of work that the team can complete in an iteration.

A description of a need from a user’s perspective together with the expected benefit when this need is satisfied.

User stories are typically written in natural language using a given phrase template. In ➔Agile development, user stories are the main means for communicating needs between a ➔Product Owner and the ➔development team.

Characterizes work or activities to be performed at the beginning of a development project, before ➔Agile development can start. 

A fixed, non-extendable amount of time for completing a set of tasks

A collection of related ➔user stories

A coherent set of actions or procedures for accomplishing a task or achieving an objective.

An agile technique for relative estimation of backlog items

An analysis approach to prioritize work. It refers to the picture of the letter T: The horizontal line suggests to analyze a topic in full breath first, while the vertical line suggests to dig deeper into selected parts.

A two-dimensional arrangement of ➔user stories. Helps to understand the functionality of the ➔product, identify gaps and plan ➔releases.

➔ User story 

A set of ➔Product Backlog items that is selected to be implemented in the current ➔sprint.

An ➔iteration in ➔Agile development, particularly when using ➔Scrum.

A task aimed at answering a question or gathering information, rather than at producing a product increment.

The coach of the ➔development team and the ➔Product Owner when using ➔Scrum, guiding them to apply Scrum properly. 

A popular framework for ➔Agile development of a ➔product. Scrum introduces the roles of ➔Product Owner, ➔Scrum Master and ➔development team. The product is developed in ➔time-boxed ➔sprints.

A high-level plan that describes how the product is likely to grow.

Breaking an item down into finer grained parts. 

A (well understood) ➔user story used as a reference for relative sizing of other ➔backlog items

The improvement of the internal quality of source code, particularly the structure of the code, without changing its observable behavior.

A person responsible for a ➔product in terms of functionality, value and risk. The product owner maintains and prioritizes the ➔Product Backlog, makes sure that the stakeholders’ requirements as well as market needs are elicited and adequately documented in the Product Backlog and represents the stakeholders when communicating with the ➔development team.

An ordered, typically prioritized collection of work items that a ➔development team has to work on when developing or evolving a ➔product. Items include requirements, bugs to be fixed, or ➔refactorings to be done.

A software-based system or service which is developed and marketed by a supplier and used by customers. 

An ➔ increment that has sufficient maturity to be released to the customer

An agile estimation technique 

In user-centered design and marketing, personas are fictional characters created to represent the different user types that might use a site, brand, or product in a similar way.

A minimal version of a new ➔product that allows the ➔development team to learn about customer acceptance of the product.

A MVP tries to maximize the return on investment in terms of customer feedback while minimizing the risk (in terms of development cost). 

A product with the smallest possible feature set that has a market value and can be shipped to customers / end users. 

1. The systematic study of ➔methods in a particular field, in particular, how to select, apply or evaluate methods systematically in a given situation.

2. A set of methods being applied in some combination.

The systematic application of one or more coherent ➔techniques to achieve a certain objective and/or to create an artifact. 

1. (General) The repetition of something, for example, a procedure, a process or a piece of program code.

2. (In Agile) A ➔timeboxed unit of work in which a ➔development team implements an ➔increment to the ➔product under development. In ➔ Scrum, the requirements to be implemented are given in the ➔Sprint Backlog.

A basic principle of ➔Scrum: After each ➔sprint, both the developed results and the development practices are inspected. Then, the product goals and development practices are adapted accordingly.

An addition to a system under development that extends, enhances or refactors (➔Refactoring) the existing parts of the system. In ➔Agile development, every ➔iteration produces an increment.