Task management system, task management method, and program

Abstract

To enable motivation of a user who repeatedly performs same work to be increased.SOLUTION: A task management system includes: a reception unit 11 which receives completion of any one of a plurality of tasks included in one work, each of the tasks being performed by a different user; and a scenario progression unit 12 which makes progress of avatars of the plurality of users according to a scenario allocated to each of the avatars. The scenario progression unit 12 makes progress of each of the avatars for the completion of any one of the tasks in order of a plurality of scenes included in each one of the scenarios. The number of scenes included in each one of the scenarios is set so as to be different depending on the users.SELECTED DRAWING: Figure 1

Description

[Background technology]

[0001] There have been production line progress information display systems that display the production efficiency in an easy-to-understand manner and can manage the production line (see, for example, Patent Document 1). The production line progress information display system described in Patent Document 1 calculates the current actual process number based on process completion information and outputs it to a monitor.

[0002] The production line progress information display system can display the progress status on the inserting machine monitor installed at each production site. This allows the inserting machine operator to be prompted to speed up the work pace if the progress is behind the target. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2012-174019 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, when workers on a production line are required to repeatedly perform the same tasks, which are often simple tasks, they tend to lose motivation and lose concentration.

[0005] In a production line progress information display system such as that described in Patent Document 1, workers can be encouraged to speed up their work pace if they are behind schedule, but this has little effect on increasing worker motivation.

[0006] The present invention has been made in consideration of the above circumstances, and has an object to provide a task management system, a task management method, and a program that can increase the motivation of a user who repeatedly performs the same task. [Means for solving the problem]

[0007] A task management system of one embodiment of the present invention comprises a reception unit that receives the completion of one of multiple tasks included in a single task performed by each user, and a scenario progression unit that progresses the avatars of multiple users according to a scenario assigned to each avatar, wherein each time a task is completed, the scenario progression unit progresses each avatar in sequence through multiple scenes included in one scenario, and the number of scenes included in one scenario is set to a different number depending on the user.

[0008] A task management method according to one embodiment of the present invention includes a reception step for receiving that one of multiple tasks included in one work performed by each user has been completed, and a scenario progression step for progressing avatars of multiple users according to a scenario assigned to each avatar, wherein the scenario progression step progresses each avatar in sequence through multiple scenes included in one scenario each time a task is completed, and the number of scenes included in one scenario is set to a different number depending on the user. A program according to one aspect of the present invention is a program for causing at least one processor to execute each step of the task management method described above. Effect of the Invention

[0009] The task management system, task management method, and program according to the above aspects of the present invention have the advantage that they can increase the motivation of a user who repeatedly performs the same task. [Brief description of the drawings]

[0010] [Figure 1] 1 is a block diagram of a system including a task management device (task management system) according to an embodiment of the present invention. [Diagram 2]1A is a block diagram of an event generating unit according to an embodiment, and FIG. 1B is a block diagram of a calculation unit according to an embodiment. [Diagram 3] 5 is a flowchart illustrating an example of an operation of the task management device according to the embodiment. [Figure 4] 5 is a flowchart illustrating an example of an operation of the task management device according to the embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] <Embodiment> Hereinafter, the task management system according to the present embodiment will be described in detail with reference to the accompanying drawings.

[0012] The task management system according to this embodiment is a system that can increase the motivation of a user to complete a task by progressing a scenario assigned to the user's avatar when the completion of one task among the user's work is input. As shown in Fig. 1, the task management system according to this embodiment includes a reception unit 11 that receives the completion of one task, and a scenario progression unit 12 that progresses the user's avatar according to the scenario.

[0013] Here, each scenario includes multiple scenes. When one task is completed, the scenario progression unit 12 can progress one scene. The number of scenes included in one scenario is set to a different number depending on the user.

[0014] By completing one task, the user can progress through the scenario with the avatar scene by scene, which increases the motivation to complete the task, and since the number of scenes included in one scenario is set to be different for each user, the difficulty of completing the scenario can be adjusted by the number of scenes. In other words, the difficulty of completing the scenario can be adjusted by setting fewer scenes than usual in one scenario for a user who performs a highly difficult task, and by setting more scenes than usual in one scenario for a highly skilled user.

[0015] This can increase motivation and improve concentration on work, even for users who only perform simple tasks repetitively. As a result, users can increase the speed of their work and can expect to improve their productivity.

[0016] In this specification, a scenario means a story line assigned to each avatar. As described above, a scenario includes multiple scenes. The multiple scenes have contents related to each other, and it is preferable that the story develops by progressing through the scenes in order. By displaying multiple scenes in order, a single story line is completed as a scenario. One scenario is executed by going through all the scenes, and after one scenario is accomplished, the scenario is executed again from the first scene.

[0017] Examples of scenarios include the following. That is, an example of a scenario is a hotel work scenario. Hotel work includes, for example, front desk clerk, bellboy, housekeeper, driver, restaurant, etc. In this embodiment, each of the avatars of multiple users is assigned one of these roles.

[0018] The front desk clerk scenario includes (1) a scene in which a customer arrives in the lobby and checks in, and (2) a scene in which a customer checks out.

[0019] The bellboy scenario includes: (1) a scene in which the bellboy transports a customer's car to the parking lot; (2) a scene in which the bellboy transports a customer's luggage to the front desk; and (3) a scene in which the bellboy transports a customer's luggage to the guest room. The housekeeper scenario includes (1) a scene in which the guest rooms are cleaned after check-out and (2) a scene in which the beds are made in the guest rooms.

[0020] The driver's scenarios include: (1) a scene in which a customer is picked up from the station to the hotel, (2) a scene in which a customer is taken from the hotel to the station, (3) a scene in which sheets and towels (hereafter referred to as linen) are transported to the laundry, and (4) a scene in which linen is transported from the laundry to the hotel.

[0021] The restaurant scenario included (1) a scene of cooking, (2) a scene of preparing a table, (3) a scene of serving food to customers, and (4) a scene of clearing the table.

[0022] A scenario is set for each role, but a total scenario (hereinafter, sometimes referred to as the total scenario) is also set by setting multiple users as one team and assigning them to one team. In the above example, the total scenario is composed of the front clerk, bellboy, housekeeper, driver, and restaurant. Other examples of total scenarios include a pizza shop (scenario: telephone reception, dough craftsman, making, delivery, etc.), a hot spring (scenario: receptionist, hall staff, kitchen chef, etc.), an expedition team's life on a deserted island (scenario: navigator, laundry, props, fishing, cook, hunter, etc.), agriculture (scenario: plowing, sowing, watering, maintenance, fertilizer, harvesting, shipping, etc.), and a restaurant (scenario: receptionist, hall staff, kitchen chef, etc.). In the following, a hotel's operations will be explained as an example of a total scenario.

[0023] In the following embodiment, a task management device 100 in which most of the functions of a task management system are integrated in one housing will be described. However, it is not essential for a task management system to have multiple functions integrated in one housing, and for example, the components of the task management system may be distributed across multiple housings. In addition, some of the functions of the task management system may be realized by the cloud (cloud computing) or the like.

[0024] 1, the entire system including the task management device 100 includes a data input unit 3, the task management device 100, and a display device 4. The data input unit 3, the task management device 100, and the display device 4 are connected to each other so as to be able to communicate with each other via wire or wirelessly.

[0025] An example of a task performed by a user is a process in a product production line. In a production line, multiple users (workers) each perform different tasks. In addition, multiple users belonging to one production line can form one team.

[0026] One operation includes multiple tasks. For example, if one user is a worker who assembles one part, that is, if the worker assembles one part and places it on a conveyer to send it to the next user, one task is completed when the part is assembled and then placed on the conveyer.

[0027] As another example, when a user is a worker who cuts vegetables such as cabbage, that is, when the user is performing the task of cutting one vegetable, one task is completed when the user finishes cutting one vegetable.

[0028] The plurality of tasks may be one task that is repeatedly performed, or different tasks that are performed sequentially. When one task is completed, the data is input into task management device 100 by data input unit 3. (Data Entry Section 3)

[0029] The data input unit 3 inputs information that a task has been completed by the user to the task management device 100 for each task. For example, the data input unit 3 detects a deliverable generated by completing one task, and inputs the completion number "1" to the task management device 100. In this case, the data input unit 3 may be a sensor attached to a conveyor that moves the deliverables. Examples of the sensor include a non-contact sensor such as a photoelectric sensor that is installed so as to intersect with the conveyor's transport direction, a contact sensor such as a pressure sensor, a camera, an infrared sensor, etc.

[0030] The data input unit 3 is not limited to inputting the completion number "1" when one product is detected by the sensor. For example, when multiple products are produced in one task, the completion number "1" may be inputted when all of the multiple products are detected. Also, for example, in the case of a task of "cutting vegetables," the cut vegetables are the product, and the completion number "1" may be inputted when the cut vegetables exceed a predetermined weight.

[0031] The data input unit 3 may also determine the degree of completion of the work product, and input a completion number of "1" when it is determined that the product is complete. This makes it possible to avoid inputting defective products as the completion number. The degree of completion may be determined automatically by the system's functions, or by the worker of the next process on the production line.

[0032] The data input unit 3 does not have to automatically detect the completion of a task using a sensor. The data input unit 3 may be, for example, an input device that inputs that a task has been completed by a worker or a manager. Examples of the input device include a mouse, a keyboard, a microphone, and a touch panel. In the case of a task that does not generate a deliverable, an input device is preferably used as the data input unit 3. The data input by the data input unit 3 indicating that the task has been completed is transmitted from the data input unit 3 to the task management device 100. (Task management device 100)

[0033] The task management device 100 can execute processing such as graphics based on information transmitted from the data input unit 3 and display the processing on the display device 4. The task management device 100 includes, for example, a personal computer or a server computer. That is, the task management device 100 includes a computer system having one or more processors and a memory. At least some of the functions of the task management device 100 are realized by the processor of the computer system executing a program recorded in the memory of the computer system. The program may be recorded in the memory, or may be provided via a telecommunication line such as the Internet, or may be recorded and provided on a non-transitory recording medium such as a memory card.

[0034] 1, the task management device 100 includes a processing unit 1 that executes the processing of the task management device 100, and a storage unit 2. The processing unit 1 is realized by a processor that executes various processes according to programs stored in a storage. Examples of the processor include a CPU (Central Processing Unit), an MPU (Micro Processing Unit), a GPU (Graphics Processing Unit), and a microprocessor.

[0035] The storage unit 2 stores information handled by the task management device 100. The storage unit 2 is realized by, for example, a Read Only Memory (ROM), a Random Access Memory (RAM), an Electrically Erasable Programmable Read Only Memory (EEPROM), or the like. (Processing section 1)

[0036] The processing unit 1 includes a reception unit 11, a scenario progression unit 12, an event generation unit 13, a calculation unit 14, a title determination unit 15, and a display unit 16. The reception unit 11, the scenario progression unit 12, the event generation unit 13, the calculation unit 14, the title determination unit 15, and the display unit 16 merely indicate functions realized by the task management device 100, and do not necessarily indicate actual configurations. (Reception Section 11)

[0037] The reception unit 11 receives information that one task has been completed, which is sent from the data input unit 3. When the reception unit 11 receives information that one task has been completed from the data input unit 3, the reception unit 11 associates a user name with the information that one task has been completed and outputs the information to the scenario progression unit 12. This makes it possible to distinguish which user has completed the input information on task completion. The information received by the reception unit 11 is output to the scenario progression unit 12. (Scenario Progression Part 12)

[0038] The scenario progression unit 12 causes the avatars of multiple users to progress scene by scene according to the scenario assigned to each avatar. When information that one task has been completed is input from the reception unit 11, a command is output to the display unit 16 to display the corresponding avatar moving according to one scene.

[0039] After progressing the first scene, the scenario progression unit 12 stores this, and when information is input that the next task has been completed, the scenario progression unit 12 progresses the second scene. In this manner, the scenario progression unit 12 progresses multiple scenes in order. Furthermore, when the scenario progression unit 12 has finished progressing the final scene out of multiple scenes in a scenario assigned to the user's avatar, the scenario progression unit 12 progresses the first scene in the scenario if information is input that the next task has been completed.

[0040] The scenarios assigned to the avatars are stored in advance in the storage unit 2. The assignment of the avatars to the scenarios is preferably performed, for example, by initial setting. As described above, the scenarios include different numbers of scenes depending on the scenario, so it is preferable that the scenarios are assigned according to the user's work, the user's skill, etc. This makes it possible to adjust the difficulty of completing the scenarios for each user. (Event Generation Part 13)

[0041] The event generating unit 13 generates a specific event randomly or when a predetermined condition is satisfied. The event generated by the event generating unit 13 may be executed by interrupting a scene being executed by the scenario progression unit 12, or may be executed after the scene. In other words, the event generating unit 13 can execute a specific performance regardless of the scene executed by the scenario progression unit 12. As shown in FIG. 2A, the event generating unit 13 according to this embodiment includes a point-adding scene generating unit 131 and a point-deducting scene generating unit 132.

[0042] The point-adding scene generating unit 131 generates a scene (point-adding scene) in which a customer gives a point-adding evaluation to an avatar during the progress of a scenario. Examples of scenes generated by the point-adding scene generating unit 131 include a scene in which a customer gives a tip, a scene in which the owner gives a bonus, and the like. The point-adding scene generating unit 131 may also generate a scene that displays points or plus points regardless of the content of the scenario. Hereinafter, point-adding evaluations such as chips, points, and the like are collectively referred to as "point-adding points."

[0043] The points to be added may be changed randomly for each occurrence, may be a fixed number, or may be linked to the number of defective products in the deliverables (for example, the points to be added may be increased if there are few defective products). There are no particular limitations on the conditions for the occurrence of a point-adding scene, but for example, the event may be generated when the time required for one task is shorter than a fixed time, the event may be generated when there are few defective products in the deliverables, the event may be generated at a specific rate (for example, once every five tasks are completed), or the event may be generated randomly. When a scene generated by the score-increasing scene generating unit 131 is generated, it is preferable for the corresponding user to add a score to the evaluation points described below.

[0044] When a problem has occurred in a completed task, the deduction scene generating unit 132 generates a scene (deduction scene) that will result in a deduction evaluation in the scenario. For example, in the case of a front desk clerk, the scene may include a scene in which a room is double-booked, a scene in which a customer is furious, etc. For a bellboy, the scene may include a scene in which a package is delivered to the wrong place, and a scene in which a complaint is made to the general manager about the bellboy. For housekeeping, the scene may include a scene in which a large amount of garbage is left in a room, and a scene in which a customer posts on SNS that insects have appeared in the room. For a driver, the scene may include a scene in which a traffic violation or an accident occurs, and a scene in which a fine is paid. For a restaurant, the scene may include a scene in which a dish is dropped and broken, a scene in which a fire breaks, etc. The deduction scene generating unit 132 may generate a scene that displays deductions or minus points regardless of the contents of the scenario. In the following, deduction evaluations such as trouble, deductions, and minus points are collectively referred to as "deduction points".

[0045] The "fault" here means, for example, a fault in which a deliverable resulting from the completion of a task by a user does not meet a certain level of quality, or a fault in which an error occurs later due to insufficient execution of a task, etc. Information on the occurrence of a fault may be input to the reception unit 11 from the data input unit 3 by the user, or may be input to the reception unit 11 by a line manager. When a scene caused by the point-deducting scene generating unit 132 occurs, it is preferable for the relevant user to add a point-deducting evaluation to the evaluation score described below. (Computation unit 14)

[0046] The calculation unit 14 calculates the evaluation points of each user and team. As shown in Fig. 2A, the calculation unit 14 includes a user evaluation point calculation unit 141 that calculates the evaluation point of each user, and a team evaluation point calculation unit 142 that calculates the evaluation point of the team.

[0047] The user evaluation point calculation unit 141 calculates the user's evaluation point by tallying up the number of completed tasks by each user. The user evaluation point calculation unit 141 can also calculate the number of times a scenario assigned to each user's avatar has been accomplished from the number of completed tasks. It is preferable that the user evaluation point calculation unit 141 also adds the number of added points generated by the added point scene generation unit 131. On the other hand, as described above, when a scene is generated by the demerit scene generation unit 132, it is preferable to deduct demerit points from the evaluation point. In this way, it is possible to obtain an evaluation point for each user.

[0048] The team evaluation point calculation unit 142 can calculate the team evaluation points based on the evaluation points of the users belonging to the team. It is preferable that the team evaluation point calculation unit 142 calculates the evaluation points based on the number of times all scenarios are achieved and the number of times each user achieves a scenario.

[0049] The number of times all scenarios have been completed is the number of times all scenarios have been completed. When all scenarios are completed, it is assumed that a reward will be received from one customer, so the number of times all scenarios have been completed can be evaluated as the hotel's reward. When each of the front desk clerk, bellboy, housekeeping, driver, and restaurant has completed one scenario, all scenarios are completed once. In other words, the number of times all scenarios have been completed is the same as the number of times the fewest scenarios have been completed among all users belonging to one team. Since it is expected that the evaluation of each role will lead to an evaluation of the team, it is preferable that the number of times each user completes a scenario is also added to the team evaluation points. (Title Judgment Department 15)

[0050] The title determination unit 15 determines a title based on the team evaluation points and assigns the title to the team. The memory unit 2 stores a determination table used when determining a title. The determination table associates required points, which are the threshold value of the team evaluation points, with titles. The title determination unit 15 refers to the determination table and determines a title based on the team evaluation points. Examples of titles include "first-class hotel," "second-class hotel," and "third-class hotel," but these are merely examples and are not particularly limited.

[0051] The display unit 16 obtains graphics of each avatar progressing through a scene in accordance with instructions from the scenario progression unit 12, and displays these on the display device 4. The display unit 16 also obtains graphics in accordance with instructions from the calculation unit 14, the event generation unit 13, and the title determination unit 15, and displays these on the display device 4. It is preferable that the graphics are stored in the storage unit 2 in advance.

[0052] An avatar is set for each user. Examples of avatars include characters resembling people, animals, and workers, plants, machines, and imaginary characters (e.g., dragons, unicorns, etc.). The avatar displayed by the display unit 16 may be an avatar desired by the user, or all users may have the same character.

[0053] It is preferable that the display unit 16 displays the progress of the scenario by the avatar in real time while the user is performing a task. In this case, when information for one task is input, the avatar progresses through one scene, but if the avatar moves too fast, it will stop moving until the signal for the next task is input. To prevent this, it is preferable to set the avatar to move slowly. It is preferable that the avatar's movement can be adjusted appropriately.

[0054] It is preferable that the display unit 16 displays the user's evaluation and team's evaluation obtained by the calculation unit 14, and the title determined by the title determination unit 15 at the end of a day's work.

[0055] It is also preferable that the display unit 16 displays the number of times a scenario has been completed without displaying the number of times a task has been completed. This makes it difficult for the user to compare the actual number of tasks completed with other users, since the user does not know the number of scenes included in the scenario. (Display device 4)

[0056] The display screen of the display device 4 is controlled by the display unit 16 of the task management device 100. The display screen of the display device 4 is displayed based on information output from the display unit 16. The display device 4 may be a large display installed in a place where a plurality of workers can always see it, or a small display installed at each worker's work place. Furthermore, a terminal owned by each worker may be used as the display device 4. Examples of the display device 4 include a monitor, a display, a touch display, a projector, a smartphone, a tablet terminal, a notebook PC, VR goggles, and a head-mounted display. (flowchart) Next, an example of the operation of the task management device 100 according to this embodiment will be described with reference to a flowchart.

[0057] As shown in FIG. 3, the task management method using the task management device 100 sequentially executes reception steps (ST1, 2), scenario progression steps (ST3, 4), and evaluation steps (ST5 to ST9).

[0058] In the receiving step, it is received that one task has been completed by the user after the start of production (ST1, 2). When the user completes one task, information on the completion of one task is input from the data input unit 3 to the receiving unit 11.

[0059] Next, a scenario progression step is executed. In the scenario progression step, based on the information of one task completion, the user's avatar progresses one scene (ST3). At this time, as shown in FIG. 4, when the information of one task completion is input to the reception unit 11, the scenario progression unit 12 judges whether all scenes included in one scenario have progressed (ST31), and if not all scenes have been completed, progresses the scene next to the previously completed scene (ST32). If all scenes have been completed, progress is made from the first scene of the scenario (ST33). Thereafter, as shown in FIG. 3, it is checked whether the user's work is continuing (ST4), and if the work is continuing, step 2 is executed again.

[0060] On the other hand, when the work is completed, an evaluation step is executed. In the evaluation step, the number of tasks completed by each user is tallied, and the number of times each user has completed a scenario is tallied (ST5). Next, the number of times all scenarios have been completed is calculated from the number of times each user in the team has completed a scenario (ST6).

[0061] Also, positive evaluation points are added to each user from the points generated by the point-adding scene generating unit 131, and negative evaluation points are added from the points deducted from the point-deducting scene generating unit 132. Then, a team evaluation point (total evaluation point) is calculated for the team (ST7, 8). After that, a title is determined based on the team evaluation point and displayed on the display device 4 (ST9). <Modification>

[0062] The above embodiment is merely one of various embodiments of the present invention. The embodiment can be modified in various ways depending on the design, etc., as long as the object of the present invention can be achieved. Modifications of the embodiment are listed below. The modifications described below can be applied in appropriate combination.

[0063] In the above embodiment, one scene has been described as, for example, "a scene of welcoming guests from the station to the hotel", but one scene may also be a scene of moving 100 m from the station to the hotel. The scene may progress by moving 100 m each time one task is completed, and the character may arrive at the hotel from the station upon completion of multiple tasks. In other words, "a scene of welcoming guests from the station to the hotel" may be one scenario, and the scenes of moving 100 m from the station to the hotel may be multiple scenes. In this way, it is easy to set the number of scenes included in one scenario.

[0064] Multiple teams may be registered and compete with each other based on team evaluation points. Match results may be displayed using team evaluation points and the evaluation points of each user. This is expected to increase the unity of users in each team.

[0065] The data input unit 3 may evaluate the performance of the deliverable, obtain an evaluation score from the performance, and output data related to the evaluation score to the reception unit 11. When the evaluation score is equal to or greater than a reference score (e.g., 80 points), the data input unit 3 may receive a task completion signal, and when the evaluation score is less than the reference score, the data input unit 3 may not receive the task completion signal. When the evaluation score is 100 points, the data input unit 3 may output a signal to the event generation unit 13, and the score-adding scene generation unit 131 may display a score-adding scene. The data input unit 3 may be a device with a camera, or a system having a camera and a control device. The device with a camera includes a controller. The control unit included in the controller or the control device performs image processing on image data of the deliverable captured by the camera to evaluate the performance. The evaluation of the performance may be performed by AI or image analysis software. The evaluation of the performance may also be performed by an operator other than the user.

[0066] In the above embodiment, when the last scene in one scenario is finished, the first scene in the same scenario is displayed, but for example, when the last scene in one scenario is finished, the first scene of another scenario may be displayed. Also, one scenario may be composed of a number of scenes that cannot possibly be completed in one day's work.

[0067] The task management system according to the above embodiment is used for work on a production line as work performed by a user, but the work is not limited to production lines and can also be applied to training, rehabilitation, and the like. Examples of training work include muscle training for athletes and muscle and environmental training for astronauts. Examples of rehabilitation work include training in basic movement movements and training for functional recovery. In other words, "work" in this specification includes training and training.

[0068] In the above embodiment, the number of times all scenarios have been completed is the number of times the scenarios of the users belonging to the team have been completed the least, but all scenarios may be triggered by the completion of one scene by one user to progress a scene by a second user. For example, the scene of the front desk clerk checking in may not progress until the scene of the driver welcoming the guest from the station to the hotel is completed.

[0069] In the above embodiment, the task management device 100 includes, for example, a personal computer or a server computer, and the task management device 100 includes a computer system having one or more processors and memories, but it may also be, for example, a smartphone, a mobile phone, a tablet terminal, a game device, etc. <Summary>

[0070] As described above, the task management system according to the first embodiment includes a reception unit 11 that receives the completion of one of multiple tasks included in one work performed by each user, and a scenario progression unit 12 that causes avatars of multiple users to progress according to a scenario assigned to each avatar. Each time a task is completed, the scenario progression unit 12 causes each avatar to progress in sequence through multiple scenes included in one scenario. The number of scenes included in one scenario is set to a different number depending on the user.

[0071] According to this embodiment, by completing one task, the user can progress through the scenario by the avatar scene by scene, and thus not only can the motivation for completing the task be increased, but also, since the number of scenes included in one scenario is set to be different for each user, the degree of difficulty of the task can be reflected in the number of scenes, and the difficulty of completing the scenario can be set. As a result, even a user who only performs work such as repeating simple tasks can be motivated and improve their concentration on the work, and the user can increase the speed of their work, which is expected to improve their productivity. The task management system according to the second aspect is the same as the first aspect, and further includes a calculation unit 14 that tallies the number of completed tasks for each user. According to this embodiment, each user and the system administrator can grasp the number of completed tasks for each user.

[0072] In the task management system according to the third aspect, in the second aspect, the calculation unit 14 calculates the number of times the scenario has been achieved according to the number of completed tasks that has been collected. The task management system further includes a display unit 16 that causes the display device 4 to display the number of times the scenario has been achieved obtained by the calculation unit 14, without displaying the number of completed tasks. According to this embodiment, since the number of scenes included in the scenario is not known to the user, the actual number of completed tasks is difficult to compare with other users.

[0073] In the task management system according to the fourth aspect, in any one of the first to third aspects, the reception unit 11 is configured to be able to receive information that a problem has occurred in the completed task. The task management system further includes an event generation unit 13 that executes a specific performance regardless of the ongoing scene when the reception unit 11 receives information that a problem has occurred. According to this aspect, the occurrence of problems in the task management system can be suppressed.

[0074] In the task management system according to a fifth aspect, in any one of the first to fourth aspects, the receiving unit 11 is configured to be able to receive information that a problem has occurred in the completed task. When the receiving unit 11 receives information that a problem has occurred, the task management system adds a minus rating to the user's rating. According to this aspect, the occurrence of problems in the task management system can be suppressed.

[0075] In the task management system according to the sixth aspect, in any one of the first to fifth aspects, a team is made up of a plurality of users. The calculation unit 14 calculates the number of times a scenario is accomplished for each user according to the number of tasks completed that have been tallied. In the team, the number of times a scenario has been accomplished for a user who has accomplished the scenario the fewest times is regarded as the total number of times scenarios have been accomplished, which is the number of times the entire scenario has been accomplished. The task management system further includes a display unit 16 that displays an evaluation of the team based on the number of times all scenarios have been accomplished.

[0076] According to this embodiment, each team can compete for the highest rating, which is expected to improve the sense of unity among users included in the team and to increase the motivation of each user.

[0077] A task management method according to a seventh aspect includes a receiving step of receiving that one of a plurality of tasks included in one work performed by each user has been completed, and a scenario progression step of making avatars of the plurality of users progress according to a scenario assigned to each avatar. The scenario progression step is for making each avatar progress in sequence through a plurality of scenes included in one scenario each time a task is completed. The number of scenes included in one scenario is set to a different number depending on the user.

[0078] According to this aspect, even a user who only performs work such as repeating simple tasks can be motivated and improve his or her concentration on the work, and the user can increase the speed of their work, which is expected to improve productivity. A program according to an eighth aspect is a program for causing at least one processor to execute each step of the task management method according to the seventh aspect. According to this aspect, the above task management method can be realized by executing the program. [Explanation of symbols]

[0079] 100 Task management device (task management system) 1 Processing section 11 Reception 12 Scenario Progression Section 13 Event Generation Section 131 Addition scene generation section 132 Point deduction scene occurrence part 14 Arithmetic section 141 User evaluation point calculation unit 142 Team Evaluation Points Calculation Section 15 Title Judgment Department 16 Display 2 Storage section 3 Data Entry Section 4 Display device

Claims

1. a reception unit that receives information that one of a plurality of tasks included in one work performed by each user has been completed; a scenario progression unit that causes avatars of a plurality of users to progress according to a scenario assigned to each of the avatars; Equipped with the scenario progression unit causes each avatar to progress through a plurality of scenes included in one scenario in sequence each time one task is completed; The number of scenes included in one scenario is set to a different number depending on the user. Task management system.

2. A calculation unit that counts the number of completed tasks of each user is further provided. The task management system according to claim 1 .

3. The calculation unit calculates the number of times the scenario is achieved according to the number of completed tasks that have been collected, a display unit that displays, on a display device, a number of times the scenario obtained by the calculation unit has been achieved, without displaying a number of times the task has been completed; The task management system according to claim 2 .

4. The reception unit is configured to be able to receive information that a problem has occurred in the completed task, and an event generating unit that, when the receiving unit receives information that a malfunction has occurred, executes a specific performance regardless of the scene currently in progress. The task management system according to any one of claims 1 to 3.

5. The reception unit is configured to be able to receive information that a problem has occurred in the completed task, When the reception unit receives information that a malfunction has occurred, a minus rating is added to the user's rating. The task management system according to any one of claims 1 to 3.

6. Multiple users form a team, The calculation unit calculates, for each user, a number of times a scenario is achieved in accordance with the number of completed tasks that have been collected; The number of times that the scenario has been accomplished by the user in the team who has accomplished the scenario the fewest times is set as the total number of times that the scenario has been accomplished, which is the number of times that all scenarios have been accomplished; A display unit that displays an evaluation of the team based on the number of times all scenarios are completed, The task management system according to claim 2 .

7. A receiving step of receiving information that one of a plurality of tasks included in one work performed by each user has been completed; a scenario progression step of progressing avatars of a plurality of users according to a scenario assigned to each of the avatars; Equipped with the scenario progression step progresses each avatar through a plurality of scenes included in one scenario in sequence each time one task is completed; The number of scenes included in one scenario is set to a different number depending on the user. How to manage tasks.

8. A program for causing at least one processor to execute each step of the task management method according to claim 7.

Images