KOHEI KUROKAWA

Currently, if there is any error in the schedule tab, you will not be able to add, delete or edit tasks, the following OOtB message will be displayed, and refreshing will undo your changes. "Recent changes you've made couldn't be saced. Refresh the page to undo your changes and continue working. Correlation ID: xxxxxxxxxxxxxxxxxxxx" There are various cases where this error occurs, and it is detected that an error occurs when the required information of the project task is missing, the efforts are empty, or the task name is too long. However, the user does not know what caused the error in this OOtB message and cannot deal with it. Please be able to display a custom message when an error occurs on the Schedule tab.

Currently, if user set multiple tasks so that they start at the same time and work in parallel, user can make assignments that exceed the user's capacity. For example... Suppose three 9-hour tasks start tomorrow at the same time, and one person working 9 hours a day works at the same time parallelly. If you think about it normally, each task will be completed in 3 days by proceeding for 3 hours per day. However, in the same situation with the current system, one person works 27 hours a day and is assigned to complete all tasks in one day. For example, in the above case, be able to schedule all tasks in parallel for 3 hours to complete in 3 days, just as normally schedule.

Task Master function that collectively manages task information of each project. There are 3 main function. 1. Define standard task information ・Name ・Effort 2. Bulk update of tasks on the project The task information of a project that has not started yet can be changed in a bulk by changing the task master. Ex. ) Task Master - TASK A, Effort = 30H revised to Effort = 40H The efforts of TASK A on the actual project will be revised to 40H at once. *Excludes projects that are already in progress 3. Aggregate achievements and utilize for analysis When the task associated with the Task Master is completed, the actual efforts required and troubleshooting time are totaled, and analyze whether the defined standard efforts are appropriate or not. Ex.) Task A on Project1~10 completed. Then aggregate the actual efforts. Average actual effort = 40H Average trouble shooting hours = 3H -->User consider if ... ・the standard effort should be revised or not. ・this trouble hours is applicable, if not, revise the task process.

There are tasks for which it is not possible to simply divide the efforts by the number of resource to calculate the duration. By setting this schedule calculation type for each task, the duration is automatically calculated by the calculation method according to each type. I think there are 4 pattern to calculate the schedule. 1. Effort based calculation. (Default) Duration = Effort / Resource * Work hours a day Efforts = 40 H Resource = 1 Work hours = 8H per day. Then, Duration = 5 Days 2. Fixed Duration Duration is fixed regardless of efforts, resource and work hours. For example, in the case of a task such as setting a machine, turning on the switch, and then waiting for a certain period of time. 3. Zero Effort Effort is zero, and duration can be defined regardless of efforts, resource and work hours. For example, if you have requested a customer and do not use the resources of your team, but you want to set only the duration because it affects the subsequent tasks. 4. Fixed End Date When the task is delayed and the end date of the task is revised regardless of efforts, resource and work hours.