Change requests are closely related to status reports: While a status report provides information on where a project stands in relation to its objectives, a change request is a possible consequence of unsatisfactory project progress. Hardly any project achieves all of its impact and execution objectives. If objectives are endangered or, at the latest, if they are no longer achievable at all, there is no way around adjustments. Such goal changes can concern the project execution (more money, more time, etc.), or also the expected impact (smaller scope, smaller effect, etc.).

A project is sent on its way with an order. The client defines what is to be achieved with the project impact goals. Along the way, it therefore makes sense to regularly ask oneself whether the project is still on the right track and whether the goals are still realistic. During project execution, the project management status report periodically shows the health of the project. To enable us to now compare projects in a portfolio and get a quick overview, traffic lights are a proven way to do this. In this webinar, we will go into such methods and other aspects.

Every project involves risks. Things go wrong that were not planned and certainly not wanted. Such eventualities cannot always be prevented, but they can at least be mitigated. An important question is which risks are more critical and therefore require more attention. Which risks cause the greatest damage when they occur? And how likely are they to occur in the first place? In this webinar, we will explore such questions and discuss how to identify and best manage the "relevant risks" for a project.

As a project manager or project member, you have countless smaller and larger tasks to complete. Often, there doesn't seem to be enough time for everything. And with most tasks, there are stakeholders who want to see the tasks completed as quickly as possible. Deadlines overlap, you don't know anymore how to organize yourself best. In this webinar we will give you tips and tricks to get better organized in your project, to have your task list under control and to meet your deadlines at any time.

Goals and requirements - two supposedly quite different concepts. But appearances are deceptive. There are clear connections. Unfortunately, the bridge between goals and requirements is not built often enough in many projects. With a systematic approach in project initialization and in the concept phase, many misunderstandings that may arise in later phases can be avoided. Conscious design decisions in the early project phases help.

In PQFORCE there are many users and each of them works differently with the system, depending on their function and tasks. This is what the user roles are for. They assign permissions to the users, with which they can then perform their tasks and see and edit the respective data - or not. In this webinar, we will show how the authorization system works conceptually, how roles and their authorizations are defined, and also how the concrete authorizations of users can be retrieved.

Every now and then it happens that an employee forgets to fulfill his duties and, for example, enters important information for others in PQFORCE. Hours worked are forgotten to be recorded. Requested resources are not released. Or change requests are not checked and approved. In such cases, a system that periodically reminds users of outstanding tasks can help. Such e-mail notifications can be set up in a customer-specific and role-appropriate manner. Here we show how it can be done.

The PQFORCE server contains extremely valuable data about projects and resources. This can be used to generate many types of summaries, so-called reports, which serve as a basis for management decisions. In this webinar we will show how JavaScript automations can be used to compile such customized reports from the raw data and send them periodically or even ad hoc by e-mail. From this, any further evaluations or charts can then be generated, e.g. in Excel or other data processing and visualization programs.

The PQFORCE server is programmed in Java. Nevertheless, it also understands the programming language JavaScript (JS). Thus, customer-specific automations can be programmed in JS and injected into the server via the API. This results in an almost inexhaustible number of use cases. In this webinar, we'll use the simplest examples to show how this can be done without having to be a JS crack. We'll take the case where a field is to be automatically calculated and populated. From this we can then derive any similar cases.

PQFORCE has an open, documented interface. This rather technical webinar is about this PQFORCE interface, the so-called API (Application Programming Interface). We will show how a third party application, such as an ERP system, can log into PQFORCE with a Bearer Token and use the API to get data from PQFORCE or even pass data to PQFORCE. But also from Excel you can log on to PQFORCE with some programming know-how (keyword VBA) and get data and process it in Excel as you like. We will show you an example of how this works.

In this webinar, we will show how to easily create data entry screens with input fields on different object types via the customer portal. Such input fields have a type and can thus accommodate different data such as text, a date or even a value from a selection list. Also the selection lists can be defined arbitrarily. Furthermore, various options are available with which the fields can be arranged and thus an own layout can be created.

Here we demonstrate how project status reports can be designed in PQFORCE and equipped with status indicators. We show how such status reports can be filled out and submitted via a workflow for review and approval. In addition, we see how an overview of the status reports available in the projects is called up at the portfolio level ("traffic light overview").

How can project costs be recorded and planned as cost items? How is a planned cost history created? And how are target and actual costs compared in the project? Here we also show aspects such as cost types, payment plan and the recording of residual values or plan variances. In addition, we show how cost items can be linked to the Gantt plan.

In this webinar, we will show what PQFORCE can do for project planning with a Gantt plan. How is the project structure created? What is the importance of tasks in planning and how can they be related to each other via dependencies? We also go into the many details of the presentation and show how the task details can be maintained in tabular form.

How is a project initialized? When does a project "begin"? With an idea? Or a customer order? We will go into the project lifecycle as well as the project charter and show what kind of configuration options PQFORCE offers.

We show how resources can be allocated to tasks in projects. What types of allocations are there? How does an allocation appear in the workload diagram? What happens if a task is postponed or extended? We also show the interaction between project managers as demand generators and resource managers as resource providers.

We show how a project phase model such as HERMES can be mapped in PQFORCE. We will go into the configuration options of the PQFORCE Enterprise Edition and demonstrate how phase transitions can be controlled using the release workflow.