Benefits Review

A benefits review is used to assess whether the expected benefits of a project have actually been achieved.

Depending on the project, benefits may become measurable during the project, immediately after project completion, or at a later point in time.

It is therefore important to define at an early stage which benefits are expected, how they can be measured, and who is responsible for evaluating them.

Define benefits and measurement criteria

For each expected benefit, criteria should be defined that can be used to assess whether the benefit has actually been achieved. The following questions can help:

• What specific benefit should be achieved through the project?
• How and when can the expected benefit be measured?
• Who is responsible for evaluating the benefit?
• Which measures are required to verify the benefit?

This ensures that the basis for the subsequent evaluation is already defined before the actual benefits review takes place.

Document the benefits review in the project

A dedicated Nutzenrevision folder can be created for the benefits review. Each benefit to be evaluated is captured as a separate task and can be identified using the Nutzenrevision label.

The result of each benefits review can be documented using the Nutzenstatus Flavor. The following values are available:

• in Prüfung
• Nutzen bestätigt
• Nutzen nicht bestätigt

The expected benefit and the basis for its evaluation can be described in more detail in the task. Any measures required for the review can be documented directly and tracked through to the final evaluation.

Evaluate benefit status in the List view

In the List view, multiple benefits can be compared in a compact format. The Nutzenstatus Flavor can be displayed as a separate column. Together with the Nutzenrevision label, this makes it easy to see how the individual benefits have been evaluated.

The view can also be filtered by the Nutzenrevision label and by specific values of the Nutzenstatus Flavor. This makes it possible, for example, to display only benefits that are still under review.

Best Practice

• Define the expected benefits and suitable measurement criteria as early as possible.
• Determine when the benefits can be meaningfully evaluated and who is responsible for the evaluation.
• Capture the benefits to be reviewed in a structured way in a shared folder.
• Identify the tasks consistently using the Nutzenrevision label.
• Document the evaluation using the Nutzenstatus Flavor.
• Record any measures required for the review directly with the respective benefit and track them through to the evaluation.
• Use the List view to compare the status of multiple benefits and filter them as needed.