Project Management System
DEMO »
App for Windows
App for Linux
Installation Guide
App for Windows
App for Linux
Installation Guide
The project implementation plan is represented by a hierarchical structure, the nodes of which are independent tasks. Each of the tasks can be decomposed into its own subtasks. The nodes of different branches of the structural plan can be interconnected by dependencies, which determine the possibility of starting the execution of one task only after the completion of another. When assigning a dependency, automatic control of planning errors is carried out, characterized by the uncertainty of the start time of the execution of the dependent task, taking into account its location in the hierarchical structure of the plan and the overall picture of relationships.
More about the structure of the project...
A kanban board is a way to display project tasks as cards organized by progress status. This allows you to control the progress of the tasks of the project or its separate branch as a whole, as well as to evaluate the employment of the participants involved in the process. Since only those tasks that do not have their own subtasks are displayed, and the overall structure of the project plan is hidden, attention is focused only on the completion of specific tasks. Kanban boards are most useful in team relationships where there is a leader who coordinates the actions of other team members.
More about Kanban boards...
Depending on the goals of the participants in a particular project, various role models or their compositions can be used. The “customer-implementor” relationship model is suitable for managing a project carried out under a contract, the “leader-team” model is suitable for the manager and the heads of his departments, who can independently act as customers or lead performers, and the “lead performer-employee” model is suitable for implementation of a set of specific tasks. Role models are assigned automatically depending on the goals and user actions aimed at achieving them.
More about relationship models...
The risks of delays in the execution of the project or its individual tasks are automatically assessed based on the time parameters of the tasks set by the user and the status of their execution. In addition, when assessing risks, time parameters and statuses of nested tasks and tasks defined as mandatory predecessors are taken into account. Pauses in the course of the project or its individual areas are taken into account as downtime and are also included in the risk assessment. Implementer`s risks are taken into account in the Customers' risks.
More about task status management...
The built-in Functional Calendar contains a calculator that allows you to calculate the number of days between two given dates and determine the date relative to the given number of days. Calculations can be made both in calendar days and in working days, taking into account a five-day working week, weekends and holidays. With the help of the calendar, it is convenient to keep track of changes in task statuses, as well as create your own calendar notes for one-time or periodic reminders.
Learn more about the functional calendar. ..
Changes of task parameters, the values of which are significant for other users (Implementers, Customers, Team members) generate automatic sending of appropriate messages to the interested party. Some messages, such as notifications about a change in a task parameter in a team project, are informational, while others, such as an invitation to interact or a proposal to correct a task, require a mandatory response.
More about messages...
The system monitors and proactively notifies the user of the imminent date of the scheduled start, resumption or completion of project tasks. In order for such a notification to be carried out, the project must be assigned the status "in progress", and the controlled time parameters must have absolute values. Additionally, the user can set milestone dates, about which he will also be notified.
More about reminders...
The progress of each task is represented by a horizontal track bar. The length of the track bar is proportional to the duration of the task, and the amount of its indent corresponds to the beginning of the task. Task duration takes into account the completion time of subtasks as well as the predicted completion time of tasks defined as mandatory predecessors. The track bar is color-coded to show the start delay, the scheduled period, and the period the task is due to exceed the set due date.
More about displaying tasks...
The start delay and predicted delay in the completion of nested tasks (subtasks) are displayed as vertical charts below and above the progress track bar of the subtasks that summarize them. At the same time, the lower part of the track bar shows a diagram of delays with the start, and the upper part shows the predicted or already accomplished delay in the completion of subtasks. The height of the bars in the chart is proportional to the number of subtasks that are delayed or late in completing within a given time period.
Read more about displaying time.. .