The goal of work package management is to establish transparency regarding the current status of all activities, set priorities for processing, and identify the resources needed at each stage. This was made possible by introducing methods and processes from the agile working world. Tasks are now processed and managed in sprints.
Scheduling rounds aimed at defining tasks for working on complex topics were established, as were regularly scheduled meetings for shared identification and allocation of further tasks within the project team. Project work is made easier through user-friendly visualization and navigation through project rooms for subprojects. Overarching views and individual dashboards are also available to provide an overview of the current degree of completion based on individual responsibility, trade or craft, or project. This means every employee is always kept informed of the relevant tasks and priorities and the status of each. The information shown also serves to prepare decision-making documents and calculate scenarios. Improvement measures are identified through retrospectives.
To better coordinate tasks in MS Project and Jira, Campana & Schott defined a number of guidelines as the first step. The schedule in MS Project acts as a form of reference, for example, and must be kept up to date at all times by the person doing the planning. Relevant adjustments must be imported into Jira.
As the second step, the schedules in MS Project were prepared for automatic reconciliation with the task planning in Jira. The forecast end dates of the tasks in Jira are now regularly compared against the schedule in MS Project. This makes it possible to manage the effects of day-to-day task management on how the entire project goes. Transfers of data in the other direction, from MS Project to Jira, also take place within the framework of automated synchronization. This enhances data quality and conserves resources.