Glossary

A D K P Q S T
A

Agile project management

  • Available budget and schedule is fixed
  • Only high level vision of the deliverable is available
  • Concrete scope/objectives are defined based on the budget, resources and time planning derived
  • On the basis of constantly repeated iterations the scope is progressively refined and elaborated

Asana, Redmine, OpenProject oder Jira

Project management software applications to improve team collaboration and work management.

Classic project management

  •  Scope of the project/ deliverables clearly defined
  • Clear targets against which project success is measured
  • Budget and schedule varies as changes occur
  • Often slow and expensive to respond to changes possible

Classic project management

  •  Scope of the project/ deliverables clearly defined
  • Clear targets against which project success is measured
  • Budget and schedule varies as changes occur
  • Often slow and expensive to respond to changes possible
C

Classic project management

  •  Scope of the project/ deliverables clearly defined
  • Clear targets against which project success is measured
  • Budget and schedule varies as changes occur
  • Often slow and expensive to respond to changes possible
D

Daily Scrum

The Daily Scrum is a short, daily meeting in which the team exchanges information about the current status of the work. The target is to identify and solve blockades and problems at an early stage. The Daily Scrum always takes place at the same place and time.

P

PMBOK Guide

PM Bok Guide ( A Guide to the Project Management Body of Knowledge) is the project management standard of the Project Management Institute among others on the world’s leading project management methods.

Product Backlog

  • Documents the current status of requirements
  • Ordered and prioritized listing of all requirements
  • Central tool for capturingand management of requirements
  • Contains all (known) requirements that are realisedhave to be around that achieve project goal.
  • Is never fixed and changes during course of the project

Product Owner

  • Defines the product features
  • Determines delivery date and scope
  • Is responsible for the success of the project (ROI)
  • Modifies features and priorities as needed
  • Accepts or rejects deliverables
  • Is responsible for the product backlog
  • –> The Product Owner represents the functions of the Product Manager, Project manager and Requirements Manager
Q

Quality Function Deployment

To most effectively transcribe customer requests, the ‘House of Quality’ tool can be used.
Overview:
Comprehensive planning and communication method.
Used to coordinate and bring together the resources of the company.
The goal is the development, production and marketing of products and / or services in terms of customer orientation.
The special feature is that market and customer requirements are translated into internal company requirements and these are taken into account at every stage and in every area of service production.

S

Scrum

Scrum is an agile framework from software development, which is now also used in many other areas. Scrum uses a few rules and three standard parts (product owner, scrum master and development team) to make a complex process workable.

This process is based on the realization that, above a certain level of complexity, projects can no longer be planned in advance in a meaningful way and that it makes more sense to control them via intermediate goals and to leave as many decisions as possible to the judgment of the participants and to self-organization.

Empirical improvement is based on three pillars:
Transparency – progress and obstacles of a project are regularly recorded for all to see.
Review – product functionality is delivered at regular intervals and both the product and the approach are assessed.
Adaptation – product requirements, plans and procedures are not defined once and for all, but are continuously detailed and adapted.’SCRUM’ does not reduce the complexity of the task, but structures it into smaller and less complex components, the increments.

Scrum Tools

With the popularity and increasing spread of Scrum, the market now offers a number of agile tools that are used in Scrum or Kanban projects. These are for example Asana, Redmine, OpenProject or Jira.

Sprint

  • Time window in which a defined part of the product backlog is realized.
  • Starts with Sprint Planning, ends with Sprint Review and Sprint Retrospective
  • Duration 1-4 weeks but usually the same within the project

Time window must not be exceeded

Sprint Backlog

The Sprint Backlog is the plan for Sprint execution that the Scrum Team creates during Sprint Planning. It includes the entries selected from the Product Backlog that are to be implemented in the upcoming Sprint, supplemented by all the necessary information for achieving the Sprint goal.

Sprint Planning

Sprint Planning is a meeting to define a “valuable” sprint goal as a stage to achieve the product goal and to plan the backlog items to be implemented in the current sprint.

Sprint Retrospective

A sprint retrospective is a special meeting within the Agile framework where teams assess what went well and what could be improved for the next sprint.

Sprint Review

As one of the four Scrum ceremonies, the Sprint Review (also: Scrum Review) is an important practice of agile working methods. In this structured meeting segment, agile teams demonstrate their work results, talk about the status of their product and the next development steps.

T

Tasks of the Scrum Master

The Scrum Master operates primarily as a coach and change agent. The function changes in the process of the project and depending on the acceptance of Scrum within the organization

  • Organize support for Scrum
  • Enforce rules of the game
  • Remove obstacles from the way
  • Manage changes in the organization

Contact

Open questions?

+49 211 30187938
info(at)ifp-duesseldorf.de
To contact form