App for Windows
App for Linux
Installation Guide
The project can be carried out independently, or you can entrust its implementation, both in full and in a separate direction, to another user. At the same time, the task is coordinated between the user who instructed (Customer) and the user who assumed the execution of project tasks (Implementer). A task is a set of project tasks, the parameters of which are essential for both the Customer and the Implementer. During the course of the project, the task may be supplemented or changed by agreement of the parties.
More about agreements on the performance of tasks...
To complete a project or its separate direction, you can form a Team - involve a user or a group of users who, like the user who invited them (Leader), can manage the progress of the completed project. Any member of the Team may, as a Customer, involve other users (Implementers) in the implementation of certain areas of the project. The Leader has the privilege of both adding users to the Team and kicking out any member of the Team.
More about Project Participation Agreements...
For the project as a whole, the user can be the Implementer on the assignment, and for certain areas of this project, he can act as the Customer for other users. Thus, for the same task, the user can have a task with the Customer and at the same time a task with the Implementer. At the same time, if the user has a need to change the parameters of such a task, then the changes will need to be coordinated sequentially, first with the Implementer, and then with the Customer.
More about approval of offers...
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.. .