Agile Glossary
GlossaryP
NEXUS
A framework based on the Agile Manifesto and Scrum, which was extended by some roles
and events. The focus is on identifying and displaying interdependencies in the workflow.
NEXUS INTEGRATION TEAM
The team coaches, coordinates and ensures the correct execution of the parallel
development work and the correct use of the practices and tools in the Nexus Framework.
Planning Poker
A playful team-building activity to achieve consensus within a group. Usually, this playful
form of effort estimation is used by agile software development teams to estimate the
approximate time required for a particular project work or sub-project.
Product Backlog
The product backlog collects requirements that the team has to meet in order to develop
the product. The backlog is dynamic and constantly evolving. The tasks for each sprint
have their origin in the product backlog.
Product Increment
The product increment is the sum of all product backlog entries completed during the
current and previous sprint.
product owner
Is a role in scrum that can also be described as a requirements manager. He is responsible
for the development and success of the product. He is also responsible for the
development of product visions and capturing requirements as stories in the backlog.
Project Management Office (PMO)
It's a staff department that handles projects. The PMO offers advisory support to the
specialist department and decides on project proposals. In addition, progress is monitored
directly by the PMO in the project.
PULL mechanism (Kanban)
As part of the Kanban board, the cards from the subordinate “done" columns are "dragged
into” the next columns as required regarding WIP.
retrospective
Retrospectives are team meetings for a review of the past sprint (iteration). It is evaluated
what has gone well and what went badly (learning from the past). In addition, measures to
improve the next iteration will be defined.N
R