Contact

Glossary

3C

According to Ron Jeffries, the 3Cs are a mnemonic device for the characteristics of user stories. 

  • Card: User stories should summarize the most important agreed-upon points concisely. An index card is used for this purpose. 
  • Conversation: A user story is discussed at least once, usually several times, between the parties involved; a purely written note is not sufficient. 
  • Confirmation: Before implementation begins, binding acceptance criteria for later approval are defined for each user story. 

The 100-point method developed by Dean Leffingwell and Don Widrig is a cumulative voting technique. Each participant has 100 points that can be distributed among individual work units or requirements to make their prioritization visible.

James Macanufo established the 7Ps for preparing goal-oriented meetings and workshops: 

  • Purpose – What is the purpose of the meeting?
  • People – Who should be there and what roles will they play?
  • Product – What exactly should the outcome be and how does this outcome serve the purpose of the meeting?
    Process – What should the agenda and approach look like?
  • Pitfalls – What are the potential pitfalls and how can they be avoided?
  • Preparation – What preparations are useful, and should participants prepare anything?
  • Practical Concerns – Logistics: When and where, necessary equipment, catering, etc.

A

Agile

Agile means nimble, mobile, maneuverable. In business, agility describes a modern form of work organization and stands for flexibility and rapid development. Agility is intended to achieve better and more efficient adaptation to changing requirements during an ongoing project or during ongoing business operations. 

In the Agile Manifesto (Manifesto for Agile Software Development), software development experts published the fundamental principles and values of agile software development. In addition to software development, it can also be applied to other projects and production processes. 

Agile methods are systematic approaches using agile tools that are designed to reduce bureaucracy and increase performance in teamwork. The focus is on adapting to change, focusing on the customer, and maintaining high-quality standards. 

The agile mindset is a way of thinking and acting based on the Agile Manifesto and its principles. 

Agile values originate from the Agile Manifesto. They form a fundamental value system that represents the common basis for decisions, strategies, and practices of agile teams. The applicable agile values can be tailored individually to the individual, a team, or an organization. 

The acceptance criteria, also known as conditions of satisfaction, form a list of criteria that are essentially defined by the product owner to express their expectations. This is a project-accompanying process of requirements gathering. The acceptance criteria can be used to determine whether a user story or product backlog has been implemented correctly. Acceptance criteria that appear repeatedly for each product backlog item should be considered for transfer to the Definition of Done (DoD). 

A work unit or work item is a self-contained task that goes through the processing steps on the Kanban board and is represented as a ticket. The project team itself also forms a work unit. 

In the agile Scrum method, three standardized project management products are referred to as artifacts. The artifacts are the product backlog, sprint backlog, and increment. 

B

Backlog

Agile means nimble, mobile, maneuverable. In business, agility describes a modern form of work organization and stands for flexibility and rapid development. Agility is intended to achieve better and more efficient adaptation to changing requirements during an ongoing project or during ongoing business operations. 

A burndown chart is a graphic that serves as a planning, monitoring, and control tool. It can be used to visually represent the remaining work in relation to the remaining time. 

Business value points can be used to prioritize product backlog items. The higher the financial business value of an individual item, the more points are assigned to it. 

C

Change Request

A changed requirement represents a disruption in the process that requires a change request. The formal change request process addresses the changed requirement and ensures the stability of the project process by making the appropriate adjustments. 

Canvas means canvas.
The canvas method was introduced in 2004 by Alexander Osterwalder and Yves Pigneur in Business Model Canvas. It is a graphical representation of complex projects and issues, in which a topic is clearly divided into individual sections.
See also Project Canvas.

Commitment means obligation, dedication, binding agreement. 

In business, it refers to the positive identification of employees with their employer or project; a voluntary commitment or bond. The inner attitude of “commitment” leads to a strong will to succeed in the project and thus to proactive involvement, greater satisfaction, and loyalty among employees. 

D

Daily Scrum

A daily scrum is a short meeting that takes place every working day and serves as a forum for the team to exchange the latest information about the project. This allows them to respond quickly to short-term events and requirements. A daily scrum lasts a maximum of 15 minutes and usually takes place at the same time every day. 

See also Standup Meeting. 

In the agile Scrum method, the Definition of Done is a list of binding criteria that must be met in order to define a user story or an entry from the product backlog as “done.” The development team is responsible for ensuring that these criteria are met. Restrictions and non-functional requirements may also be included in the Definition of Done. 

The Definition of Ready defines whether a product backlog item is sufficiently described to be included in the team’s current sprint. Unlike in the DoD, the responsibility here lies with the product owner, who formulates the necessary user stories. 

E

Unitless Estimation

Unitless estimation is used to evaluate effort without resorting to conventional units such as currency or time. Instead, story points or business value points can be used. 

An epic is very similar to a user story. If, during the further processing of a user story, it becomes clear that it needs to be formulated in more detail or that it cannot be implemented within a sprint, it is split up and an epic is created. An epic is therefore a more comprehensive requirement that requires a larger structure and is less finely broken down than a user story. 

F

Fail Fast

Fail Fast is intended to reveal at an early stage whether a project is promising or whether it may not work. To do this, work on the project is started and reviewed shortly thereafter. If difficulties become apparent, a decision is then made as to whether adjustments are necessary or whether the project should be abandoned before more time and financial resources are invested. 

H

Hybrid

A hybrid is a mixture of components from different sources. In the case of individuals, this is also referred to as a mixed breed or a crossbreed. 

Hybrid project management is composed of different approaches. It usually includes procedures from classic and agile project management in order to combine the advantages of both systems. The entire project or only parts of it can incorporate elements of another management system. 

I

Impact Mapping

Impact mapping is a strategic planning method. The goal is to develop a project or product that has a specific effect (an “impact”). Clear communication of the goals should enable better decisions to be made. In the impact map, the core of a topic is answered by these questions: 

  • Why should something be done? → Business objective 
  • Who are the actors/stakeholders? 
  • What should the impact look like? 
  • What should the result be? 

Impediment means obstacle or hindrance. Backlog is a list of open tasks. An impediment backlog is therefore a list of possible project-related obstacles and disruptions. 

In the agile Scrum method, the Scrum Master is responsible for recording potential disruptions in the impediment backlog in order to ensure the smooth running of the project by eliminating them. 

Increment comes from Latin and means growth; incremental means building on each other. 

In the agile Scrum method, an increment is the potentially deliverable result of a sprint, which is continuously supplemented and, if available, builds on increments from previous sprints. 

Short for product backlog item, see there. 

Iteration comes from Latin and means repetition; in general, iteration is understood to be a process that repeats itself multiple times. 

In the agile Scrum method, iteration is synonymous with a sprint. 

J

Jobs-To-Be-Done (JTBD)

JTBD describes a mechanism for how innovations are accepted by customers. The assumption is that a product or market emerges or develops as soon as the customer seeks a solution for a job-to-be-done – a task that needs to be completed. The JTBD can represent a wide variety of requirements. A genuine solution, an offer that is useful and therefore functional for the customer, can only be created if the requirement has been fully and correctly identified. 

K

Kaizen

The term Kaizen describes a Japanese concept of corporate management. It is based on the desire to consistently improve processes within a company and to make this objective part of the corporate philosophy. Masaaki Imai is considered the originator of the term Kaizen. 

Alongside Scrum, Kanban is one of the most widely used methods of agile project management. These methods aim to optimize existing processes quickly and effectively. Kanban can be combined with other agile and classic project management methods. 

The Kanban board is a visual aid in the agile Kanban method for clearly displaying project processes and tasks. It is a key component of this method and can be created digitally or physically. 

M

Milestone

Milestones are intermediate goals of a project phase or events of particular importance in the course of the project. They are also defined as checkpoints. Their structuring function helps to maintain an overview of the entire project. When a milestone is reached, a stage can be completed, a new stage can begin, or an important decision can be made. Milestones therefore often represent critical points in the overall project. 

Mindset refers to the basic attitude that includes personal values, beliefs, and principles. An individual’s mindset determines how they behave, act, and react. Mindset is largely shaped by experience and determined by the subconscious, but it can also be consciously trained and changed. 

Minimum Marketable Feature is the smallest possible package of features that must be implemented in order to offer the customer significant added value. It is therefore a quickly implementable position that can be marketed individually. 

The Minimum Marketable Product is the marketable product in its smallest possible form. It is fully functional, but has limited features compared to the planned final version. The strategy behind it enables new products to be launched on the market particularly quickly. 

The Minimum Viable Product is a testable product with the smallest possible scope, which enables a maximum of empirical values. User feedback can be used to influence the further development of this product at an early stage. 

The MuSCoW method can be used to prioritize requirements: 

  • Must have (must be present) 
  • Should have (should be present) 
  • Could have (may be present) 
  • Won’t have (will not be considered) 

P

Pain-Gain Map

A pain-gain map shows which things cause a person difficulty (pain) or pleasure (gain). 

Prime Directive 

“We assume that all parties involved have acted to the best of their knowledge, conscience, and ability at all times.” Based on this fundamental principle of the Prime Directive, we strive for solution-oriented discussions even on sensitive topics, without assigning blame. 

The product backlog is a dynamic list of all requirements for the product to be created. The product owner is responsible for the product backlog. They prioritize the requirements, maintain the backlog throughout the entire project and develop it further. 

Every requirement recorded in the product backlog is a product backlog item, regardless of its size. 

In the continuous process of product backlog refinement, the product backlog is maintained and further developed. The product owner and development team work on the product backlog items by specifying, evaluating, and prioritizing them. Once prepared, they can then be used for sprint planning. 

The Product Owner is a defined role in the project team, a single person who bears responsibility for the product. The Product Owner acts as the link between the Development Team and the specialist departments. Among other things, they are responsible for the Product Backlog. 

Project Canvas is a communication tool that uses a clearly structured template to visualize the basic components of a project in a clear manner. Interdisciplinary teams in particular benefit from Project Canvas, as it allows them to quickly gain a common understanding of complex projects. 

See also Canvas. 

R

Reference Story

A user story can be made into a reference story after it has been jointly evaluated by an estimation team with a medium size. This reference can then be used to compare the estimated size of other user stories. The larger a compared story is, the more it deviates from the reference story, and the more its estimate loses accuracy. 

A release is a new or modified product that is delivered to customers for use. 

The release burndown is displayed as a graph. It illustrates the amount of work required for each sprint in relation to the time remaining until release. The release burndown chart can be used to monitor whether the release will take place on schedule or be delayed. 

Release sprints include the final work for a release in a separate sprint. However, since every sprint should generate an increment, this frequently used practice is controversial. 

The Retromat website provides a random selection of suggestions for retrospectives, serving as inspiration for retrospective planning.  

https://retromat.org/en/?id=143-89-145-73-83 

Retrospective means looking back.  

In agile project management, this refers to a team meeting at the end of each sprint, during which the team looks back to learn from the completed sprint. The focus is on collaboration, reflecting together on where things went well and where measures for improvement can be implemented. 

Review means evaluation.  

It is an evaluative assessment in the form of a meeting. It can, for example, concern the results of a (sub)project, a completed sprint, or a product. 

 

The aim of risk management in a project is to use various processes and tools to identify potential risks at an early stage and organize how to deal with them. 

S

Scope

Scope means extent. 

In project management, it refers to the total scope of the project. 

Scrum was developed by Ken Schwaber and Jeff Sutherland in the 1990s, and the Scrum Guide is available for free download on the Internet. Originally originating in software development, Scrum is now one of the best-known agile approaches. The term Scrum (English for “scrum”) is derived from the short daily team meetings that serve to exchange information and coordinate the project. 

The Scrum Guide describes the agile Scrum method and is available for download online. The guide is continuously maintained and updated. 

The Scrum Master is one of the three roles in the agile Scrum method. In this role, they are responsible for the correct implementation of the method. They act as a mediator between the different roles and as an advisor and supporter of the team with regard to their competence and cooperation. They keep an eye on obstacles and ensure that everyone involved can work effectively and without disruption. 

The Scrum Guide defines three roles in the agile project environment: 

  • Product Owner 
  • Scrum Master 
  • Development Team 

The Scrum Team consists of all Scrum role holders: Product Owner, Scrum Master, and Development Team. 

The Significant Objective formulates the goal that is to be achieved with the next release from an operational or customer perspective. The idea arose as a solution to the discussion about the differences between MVP (Minimum Viable Product), MMF (Minimum Marketable Feature), and MMP (Minimum Marketable Product). 

Scaling is a variable order of magnitude. The term is often used in business in connection with the expansion of business processes. For example, (usually highly automated) production can be scaled to generate more revenue. When scaling the Scrum team, several teams are deployed to work on a larger project. 

Speed boat games or workshops can have different motivations. In general, they are used to work out, figuratively speaking, “drive engines” and possible “brake pads” in teamwork, which cause the project (boat) to reach its destination faster or slower. 

Sprints are central elements in the Scrum method. They are time-limited workflows in which the development team works out a specified interim project result, an increment. Sprints have a predetermined duration of usually one to four weeks and build on each other. 

All entries from the product backlog that are to be processed in the next sprint are transferred to a sprint backlog. The entries are supplemented with all additional information necessary for the sprint goal. The sprint backlog is maintained by the development team. 

The sprint board is a visual aid for sprint planning, similar to the Kanban board. 

The sprint goal formulates the increment to be produced – the desired result of a sprint – which is derived from the underlying sprint backlog. 

Sprint Zero precedes the actual sprints. It serves to create the right working conditions for the following sprints. For example, workplace equipment, hardware, and software requirements, and necessary materials are considered. 

Sprint planning is a meeting of the Scrum team at the beginning of a sprint. During this meeting, the result (increment) of the sprint, the sprint goal, and the sprint backlog are defined. 

Standup meetings are short team meetings that take place daily, if possible, and are held standing up. 

See also Daily Scrum. 

Story mapping is a visualization method for representing requirements. It helps to clearly display a large number of entries in the backlog (user stories and epics). The visualization highlights temporal sequences, connections, and dependencies, and reveals gaps in the backlog. 

T

Timebox

The timebox is a time limit for the maximum duration of meetings and sprints. 

U

User Story

A user story describes in short sentences a user’s expectations of the finished product or the requirements placed on the product. The wording is expressed in natural language and follows the pattern “As … I want to … so that …”. 

Synonym for product backlog. 

V

Velocity

Velocity refers to the individual speed of a Scrum team in terms of the amount of work completed per sprint. Over the course of the project, an average is calculated, which can be used for further planning. 

Drive governance, clarity and performance

We establish and evolve Project Management Offices(PMOs) that provide strategic alignment and operational transparency. With the right governance, portfolio management, and executive dashboards, we help you turn complexity into clarity.

** Key benefits **
• Stronger prioritization and resource focus
• Faster, data-driven decision cycles
• Clear governance and measurable impact

Deliver with precision, safety and reliability

We combine PMI Construction standards with Lean Construction and Takt Planning principles. Our Focus: safety, cost control and predictable delivery through transparent planning and strong stakeholder management.

** Key benefits **
• Increased schedule reliability
• Reduced cost and claim risks
• Higher construction quality and safety

Balance structure and flexibility for success

Hybrid Project management merges the best of structured and agile approaches. Stage-gates provide predictability; sprints and adaptability – enabling reliable delivery and creative problem solving.

 

** Key benefits **
• Reliable timelines with flexible delivery
• Greater transparency and risk control
• Enhanced collaboration across departments

Empower teams with agility and adaptability

Agile project management accelerates innovation through short cycles, early feedback and visible results. We apply scrum, Kanban or hybrid frameworks tailored to your environment – ensuring teams deliver value continuously and adapt effectively.

** Key benefits **
• Faster time-to-market
• Early risk detection
• Improved collaboration & ownership