KR20220156362A - Kanban-based work processing device and work processing method - Google Patents

Abstract

According to embodiments, a Kanban-based work processing device includes: a Kanban board handling part that creates a new Kanban board; a Kanban card handling part that embeds a Kanban card for a created task project into the Kanban board; a work container handling part that embodies per-user-defined-work-type containers which associate the Kanban card with the task project; and a work handling part that performs user-defined work-based work communication between participants through a user-defined work container, which is one among the per-user-defined-work-type containers. The work efficiency can be improved.

Description

Kanban-based work processing device and work processing method {KANBAN-BASED WORK PROCESSING DEVICE AND WORK PROCESSING METHOD}

The present invention relates to work processing and management technology, and more particularly, to a technology for effectively supporting work performance by providing communication means between work participants, such as a work chat room for a kanban board or a kanban card in a kanban board.

In general, an Internet messenger corresponds to an application that transmits messages including text or graphics between users, and may be implemented as a chat room participated by a plurality of users. In one embodiment, the Internet messenger may include a mobile messenger executed in a mobile environment (eg, a mobile phone), and may include, for example, KakaoTalk, Line, WeChat, Facebook messenger, and the like. In addition, it is a trend that such an Internet messenger is gradually being used in various ways in the management and progress of business.

A Kanban board is one of the tools that can be used to implement kanban for managing tasks on an individual or organizational level. In addition, the kanban board is a board in which work steps and sub-tasks for each work step are listed and visualized on a flat surface. The kanban board lists each step of the entire process of a higher task in one direction and uses cards to represent work items. A card used in the kanban board may be referred to as a kanban card. For example, as the kanban card is moved from left to right for each task step, the progress of the task may be indicated.

Here, Kanban is one of the software development processes, and is a concept derived from a development method that allows developers to release products in a timely manner without excessive load.

Korean Patent Publication No. 10-2017-0040928 (2017.04.14)

According to an embodiment of the present invention, the user can grasp the progress of the ongoing project at a glance through the kanban board, and effectively provide feedback and supplement for each task through a unique chat room related to the kanban card and individual chat rooms related to work notes. It is intended to provide a kanban-based business processing device and method that can increase work efficiency by easily grasping the work flow through work messages shared in time series, and a recording medium for storing them.

Among the embodiments, a kanban-based business processing apparatus includes a kanban board processing unit that newly creates a kanban board; a kanban card processor for inserting a kanban card according to the creation of a business project into the kanban board; a work container processing unit that embodies per-user-defined-work-type containers associated with the work project on the Kanban card; and a task processing unit that performs task communication based on a user-defined task with task participants through a user-defined task container among the containers for each user-defined task type.

The Kanban card processing unit may insert a new Kanban card into the Kanban board whenever creation of the work project is detected.

The task container processing unit may implement the user-defined task container to exclusively process a corresponding user-defined task type through the user-defined task container.

The task container processing unit may assign a unique identity link to the user-defined task container and support direct movement between the containers for each user-defined task type through the user-defined task.

The task container processing unit may implement one of the containers for each user-defined task type as a dedicated container for the task chat room.

The business processing unit may materialize a business chat room associated with the business project in a dedicated container for the business chat room.

The task processing unit may materialize a user-defined task chat room associated with the user-defined task in a dedicated container for the task chat room.

The task processing unit may implement the user-defined task as a text or binary file-based task message and provide the task message to the task chat room.

When an event occurs in another user-defined task, the task processing unit implements the user-defined task as a system message and provides the task message to the task chat room.

The task processing unit may register a reminder event by tracking a conversation progress state of the task message.

The task container processing unit may implement one of the containers for each user-defined task type as a dedicated container for task notes.

The task processing unit may implement the user-defined task as a text or binary file-based task note and curate the task note in a container dedicated to the task note according to a user setting.

The work processing unit may generate a work note event according to the generation of the work note.

The work container processing unit may implement one of the containers for each user-defined work type as a container dedicated to a work object.

The business processing unit may implement the user-defined business as a business object and implement the business object in a container dedicated to the business object.

The business processing unit may generate a business object event when a business object is provided to an arbitrary chat room in a container dedicated to the business chat room.

The task processing unit may register a reminder event by tracking the task flow-based task progress status of the task object.

The task processing unit may detect registration of a reminder event generated in the user-defined task.

The task processing unit may generate a reminder condition of the reminder event and provide a reminder message according to the reminder condition to the work chat room.

The task processing unit may generate the reminder message by setting a task progress state of a user-defined task assigned to at least some of the task participants of the task project as the reminder condition.

The task processing unit may update the reminder message based on the number of times the same reminder message proceeds.

When the plurality of tasks are sequentially connected according to the task sequence, the task processing unit may integrally generate a reminder message reflecting the corresponding task sequence and share the task through the task chat room.

When an external user without access authority is invited to the business chat room, the business processing unit may limit the access authority to the external user to access only the business chat room.

Among the embodiments, a task processing method performed in a kanban-based task processing device includes the steps of newly creating a kanban board; inserting a kanban card according to the creation of a business project into the kanban board; embodying per-user-defined-work-type containers associated with the work project in the Kanban card; and performing task communication based on a user-defined task with task participants through a user-defined task container among the containers for each user-defined task type.

The disclosed technology may have the following effects. However, it does not mean that a specific embodiment must include all of the following effects or only the following effects, so it should not be understood that the scope of rights of the disclosed technology is limited thereby.

According to one embodiment of the present invention, the user can grasp the progress of the ongoing project at a glance through the kanban board, and provide feedback and supplementation for each task through a unique chat room related to the kanban card and individual chat rooms related to work notes. It can be performed effectively, and work efficiency can be increased by easily understanding the work flow through work messages shared in chronological order.

In particular, through this process, business messages shared in chat rooms related to Kanban cards facilitate communication between business participants by storing and managing records of the overall business in one place, and providing links for easy access. User convenience can be improved.

1 is a diagram illustrating a business processing system according to the present invention.
FIG. 2 is a diagram for explaining the system configuration of the business processing device of FIG. 1 .
FIG. 3 is a diagram illustrating a functional configuration of the business processing device of FIG. 1 .
4 is a flowchart illustrating a Kanban-based business processing method according to the present invention.
5 is a view for explaining an embodiment of a Kanban board according to the present invention.
6 is a diagram for explaining an embodiment of a Kanban card according to the present invention.
7 is a diagram illustrating a process of sharing a work chat room and a work message according to the present invention.
8 and 9 are flowcharts illustrating various embodiments of sharing work messages in a Kanban-based work process according to the present invention.
10 is a diagram for explaining an embodiment of a reminder sharing process according to the present invention.

Since the description of the present invention is only an embodiment for structural or functional description, the scope of the present invention should not be construed as being limited by the embodiments described in the text. That is, since the embodiment can be changed in various ways and can have various forms, it should be understood that the scope of the present invention includes equivalents capable of realizing the technical idea. In addition, since the object or effect presented in the present invention does not mean that a specific embodiment should include all of them or only such effects, the scope of the present invention should not be construed as being limited thereto.

Meanwhile, the meaning of terms described in this application should be understood as follows.

Terms such as "first" and "second" are used to distinguish one component from another, and the scope of rights should not be limited by these terms. For example, a first element may be termed a second element, and similarly, a second element may be termed a first element.

It should be understood that when an element is referred to as being “connected” to another element, it may be directly connected to the other element, but other elements may exist in the middle. On the other hand, when an element is referred to as being "directly connected" to another element, it should be understood that no intervening elements exist. Meanwhile, other expressions describing the relationship between components, such as “between” and “immediately between” or “adjacent to” and “directly adjacent to” should be interpreted similarly.

Expressions in the singular number should be understood to include plural expressions unless the context clearly dictates otherwise, and terms such as “comprise” or “having” refer to an embodied feature, number, step, operation, component, part, or these. It should be understood that it is intended to indicate that a combination exists, and does not preclude the possibility of the presence or addition of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.

In each step, the identification code (eg, a, b, c, etc.) is used for convenience of explanation, and the identification code does not describe the order of each step, and each step clearly follows a specific order in context. Unless otherwise specified, it may occur in a different order than specified. That is, each step may occur in the same order as specified, may be performed substantially simultaneously, or may be performed in the reverse order.

The present invention can be implemented as computer readable code on a computer readable recording medium, and the computer readable recording medium includes all types of recording devices storing data that can be read by a computer system. . Examples of computer-readable recording media include ROM, RAM, CD-ROM, magnetic tape, floppy disk, and optical data storage devices. In addition, the computer-readable recording medium may be distributed to computer systems connected through a network, so that computer-readable codes may be stored and executed in a distributed manner.

All terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the present invention belongs, unless defined otherwise. Terms defined in commonly used dictionaries should be interpreted as consistent with meanings in the context of the related art, and cannot be interpreted as having ideal or excessively formal meanings unless explicitly defined in the present application.

1 is a diagram illustrating a business processing system according to the present invention.

Referring to FIG. 1 , the business processing system 100 may include a plurality of user terminals 110 and a business processing device 130 .

In an embodiment of the present invention, a plurality of users may be included in one or more user groups. One or more user groups may be referred to as a first user group, a second user group, and the like. One user may be included in one or more user groups.

The first user terminal 110a is a terminal of the first user. The second user terminal 110b may correspond to the terminal of the second user, the third user terminal 110c may correspond to the terminal of the third user, and the fourth user terminal 110d may correspond to the terminal of the fourth user.

Here, the first to fourth users may jointly participate in one or more Kanban boards as business participants. With respect to a task progressed through one Kanban board, one or more users among the first to fourth users may be a task instructor, and one or more other users may be a task manager. Business participants excluding business directors and business managers may be classified as business related persons.

There is a joint overall project in which the first to fourth users participate, and the entire project can be progressed step by step through a Kanban board. In addition, there may be a plurality of business projects included in or subordinate to the entire project. In addition, there may be one or more sub-tasks included in or subordinate to each business project, and as these sub-tasks, large and small tasks generated in the process of promoting the corresponding business project are business objects (or tasks) in the embodiment of the present invention. can be referred to as

These business objects can be uploaded to Kanban Card and managed. That is, one work project can be progressed step by step through the Kanban card, and individual work objects subordinate to the corresponding work project can be performed and managed through work notes uploaded to the Kanban card. And, here, the progress or status of the work project is classified in stages, which may be referred to as a work progress stage.

The work progress stage may be divided into, for example, in progress, under confirmation, under supplementation, and complete supplementation according to the PDCA cycle. The PDCA cycle is known as a systematic and efficient work management technique to improve work performance and performance. P means plan establishment, that is, setting the goal of the project (or task) and establishing specific strategies and action plans for its realization. And D means task performance (do), that is, actual processing of tasks according to regulations, guidelines, standards, etc. for the matters for which plans have been established. And C is the stage of checking, after confirming the work performance result of D, analyzing and evaluating it to check whether it is different from the initially set goal, and finding areas to be improved or corrected. And A stands for act. Execute necessary items for improvement and supplementation, such as modifying the results of existing work performance or reprocessing work contents by reflecting the problems and improvements identified in the previous step C. It is a step to

That is, when the task instructions are uploaded to the Kanban card by the task instructor (Plan, P), the task progress step of the corresponding Kanban card becomes 'in progress'. In addition, if the business operator processes the business in accordance with the business instruction and uploads the business process as a result (Do, D), the business progress stage of the corresponding Kanban card becomes 'confirming'. At this time, the task-related contents input by the task instructor or the task manager may be recorded as a task note and uploaded to the Kanban card, and the card status of each Kanban card may be changed. In addition, work-related contents subordinate to work notes can be created as work objects, that is, tasks, and managed in association with work notes, and updating of work objects can lead to updates of work notes and kanban cards, respectively.

In addition, for the Kanban card 'under review', the task instructor can check the task processing details (Check, C) and terminate the task. In this case, the business progress stage of the corresponding Kanban card may be 'end'. On the other hand, after the task instructor checks the task processing details, it may request task supplementation for the task processing details. In this way, when a task supplementation request or task supplementation instruction is uploaded to the Kanban card by the task instructor, the task progress stage of the corresponding Kanban card becomes 'in process of supplementation', and the card status of the corresponding Kanban card may also be changed.

When the business handler complements the business process contents corresponding to the contents of the business supplement instruction (Act, A), and the business supplement contents are uploaded to the Kanban card by the business handler, or the uploaded business supplement contents are sent by the business director If confirmed, the task progress stage of the corresponding Kanban card may be set to 'supplementation complete'. In addition, each kanban card may be classified according to the stage of work and arranged in the kanban board.

The business processing device 130 corresponds to a computing device that can be connected to at least one user terminal 110 through a network. In one embodiment, the business processing device 130 may manage one or more user groups in which other users associated with one user are included as members, that is, business participants.

In one embodiment, the business processing device 130 may be connected to the user terminal 110 through a shared folder agent installed in the user terminal 110 . Here, the shared folder agent corresponds to an agent program that is software that, when installed in the user terminal 110, allows the user terminal 110 and the business processing device 130 to interact with each other under the approval of the user terminal 110.

A folder or file to be shared may be located in a shared folder provided by the business processing device 130, but is not limited thereto. A folder or file to be shared may be located in a shared folder provided by the business processing device 130 or a personal folder of a file sharer.

The user terminal 110 corresponds to a computing device that can be connected to the business processing device 130 through a network, and may be, for example, a terminal implemented as a desktop, laptop, tablet PC, or smart phone.

In one embodiment, at least one of the user terminals 110 may be a mobile terminal, and may be connected to the business processing device 130 through cellular communication or Wi-Fi communication. In another embodiment, at least one of the user terminals 110 may be a desktop and may be connected to the business processing device 130 through the Internet.

FIG. 2 is a diagram for explaining the system configuration of the business processing device of FIG. 1 .

Referring to FIG. 2 , the business processing device 130 may include a processor 210 , a memory 230 , a user input/output unit 250 and a network input/output unit 270 .

The processor 210 may execute a business schedule display procedure according to an embodiment of the present invention, manage the memory 230 read or written in this process, and volatile memory and non-volatile memory 230 in the memory 230. Synchronization time between memories can be scheduled.

The processor 210 can control the overall operation of the business processing device 130, and is electrically connected to the memory 230, the user input/output unit 250, and the network input/output unit 270 to control data flow between them. can The processor 210 may be implemented as a central processing unit (CPU) of the business processing device 130 . More detailed operation of the processor 210 will be described in detail with reference to FIG. 3 hereinafter.

The memory 230 may include a secondary storage device implemented as a non-volatile memory such as a solid state disk (SSD) or a hard disk drive (HDD) and used to store all data necessary for the business processing device 130, It may include a main memory implemented as a volatile memory such as RAM (Random Access Memory). As such, the memory 230 may be implemented as volatile and non-volatile memory, and if implemented as a non-volatile memory, it may be implemented to be connected through a hyperlink.

The user input/output unit 250 includes an environment for receiving user input and an environment for outputting specific information to the user, and includes, for example, a mouse, trackball, touch pad, graphic tablet, scanner, touch screen, keyboard, or pointing It may include an input device including an adapter such as a device or connected thereto, and an output device including an adapter such as a monitor or a touch screen. In one embodiment, the user input/output unit 250 may correspond to a computing device connected through a remote connection, and in such a case, the business processing device 130 may serve as a server.

The network input/output unit 270 includes an environment for connecting to the user terminal 120 through a network, and may include, for example, an adapter for local area network (LAN) communication.

FIG. 3 is a diagram illustrating a functional configuration of the business processing device of FIG. 1 .

Referring to FIG. 3 , the processor 210 of the business processing device 130 includes a kanban board processing unit 310, a kanban card processing unit 330, a business container processing unit 350, a business processing unit 370, and a control unit 390. can include

However, the processor 210 according to an embodiment of the present invention does not have to include all of the above components at the same time, and some of the above components may be omitted according to each embodiment, and the processor 210 may include the above components. It may optionally include some or all of the constituent parts of.

The Kanban board processing unit 310 may newly create a user-based Kanban board. That is, the kanban board can be created in correspondence with the entire project, and various work projects generated according to the progress of the entire project can be classified and managed according to the work progress stage. At this time, each work project can be created corresponding to the Kanban card and inserted into the Kanban board.

In addition, the kanban board processing unit 310 is accessed by a user group including one or more users, and sends a user selection signal for the kanban board provided through the user terminal 110 or one or more kanban cards in the kanban board to the user terminal ( 110).

More specifically, the kanban board processing unit 310 receives user information about one or more users from the user terminal 110 through the user input/output unit 250, and stores, manages, and stores user information of users participating in the kanban board. can be updated The kanban board processing unit 310 uses user information collected for kanban board generation, and then performs various operations necessary for project management, such as processing kanban cards, creating work notes, creating work objects, creating work chat rooms, and generating reminder messages. steps can be provided.

In addition, the kanban board processing unit 310 may manage a schedule for task processing or task supplementation for set task instructions and supplementary instructions input from the user terminal 110 . For example, when the task instructions uploaded by the task director include information on the deadline for task processing, or when the task supplementary instruction includes information on the deadline for task supplementation, or on a kanban board or kanban card When a work schedule is set, information related to the schedule or due date may be collected and managed.

In addition, the kanban board processing unit 310 may provide user information collected for generating kanban boards when necessary in the process of managing schedules for tasks related to kanban boards or kanban cards. The kanban board processing unit 310 may provide necessary user information even when creating or driving a business chat room.

In addition, the kanban board processing unit 310 may create a user group when it is necessary to create a user group for a work chat room, and the name of each user group, classification criteria of the user group, information on members, etc., matching for each user group It is possible to store and manage information about identification information of a chat room, classification or membership of each user group, and authority management of each user or each user group.

That is, when the user group of the corresponding user differs depending on the user's affiliation or position, the kanban board processing unit 310 sets the identification information of the matching user group according to the affiliation, department or position, or identifies the user group for each individual user. If specified, information about the specified user group can be stored.

In addition, the kanban board processing unit 310 may also set or store the contents of the authority to access, open, or edit a chat room, file, kanban card, or kanban board for each user. Here, the kanban board may be implemented so that only users belonging to a certain user group can access it. In this case, only users who have access to the corresponding kanban board can be designated as participants in the work chat room related to the kanban board, kanban cards, and work notes.

If an external user who does not have access to the kanban board is invited as a participant in the work chat room, the external user may acquire access to the kanban board, kanban card, or work note. In this case, access rights to the kanban board, kanban card, or work notes may be limited. For example, access is possible only through a work chat room, and access to other Kanban cards within the same Kanban board may be restricted with access rights acquired through a work chat room related to a specific Kanban card. Similarly, access to other work notes within the same Kanban card may be restricted with access rights obtained through the work chat room related to the work note.

In one embodiment, the kanban board processing unit 310 may store and manage various documents, data, materials (hereinafter referred to as work data), etc. that each user uploads to the kanban board in relation to instructions or processing of work. The kanban board processing unit 310 may provide the user terminal 110 with work data into which chat room information is inserted when a work chat room is created in relation to the uploaded work data.

In one embodiment, the Kanban board processing unit 310 may provide the user terminal 110 with a user interface for receiving user signals related to business data or the Kanban board. The kanban board processing unit 310 may receive a user signal including at least one of an entire project creation request signal and a deadline setting signal input from the user terminal 110 through the user interface.

If there is one or more work chat rooms created in relation to the Kanban board, the Kanban board processing unit 310 may display a list (or list) of related work chat rooms together with the corresponding Kanban board. Also, when the kanban board processing unit 310 provides a list of work chat rooms for the kanban board, it may also provide an access path to the corresponding work chat room as hyperlink information.

In addition, the kanban board may include first to third integration containers that integrate and manage work notes, work chat rooms, and work objects created in association with a plurality of kanban cards. That is, work notes created in association with each kanban card can be integrated and managed by being inserted into the first integrated container, and work chat rooms and business objects are also inserted into the second and third integrated containers and managed in an integrated manner. can As a result, the first integration container may correspond to the work note integration container, the second integration container to the work chat room integration container, and the third integration container to the work object integration container. In one embodiment, the first to third integration containers may respectively correspond to DO, CHECK, and ACT tabs for management according to work progress stages.

In one embodiment, the Kanban board processing unit 310 may independently set a curation method for each of the first to third integrated containers according to a user's preference. Here, the curation method may correspond to a method of providing corresponding information when a user searches for work notes, work chat rooms, or work objects related to the Kanban board.

In one embodiment, when external sharing is set for work notes, work chat rooms, and work objects, the Kanban board processing unit 310 creates and inserts permanent links that are uniquely accessible, and inserts each of the first to third integrated containers. can be shared through Here, the permanent link may correspond to a link directly accessible to work notes, work chat rooms, and work objects without indirect access through a Kanban card from the outside. In other words, basically, the Kanban card can be set to allow access only to business participants who carry out the business project, and accordingly, if an outsider who does not carry out a business project does not have access to the Kanban card, the business note In addition, individual access to business chat rooms and business objects may also be restricted.

However, external sharing can be individually set for work notes, work chat rooms, and work objects, and when external sharing is set, permanent links for external sharing can be created and linked to the work notes, work chat rooms, and work objects, respectively.

For example, work notes can be shared through the DO tab (or first integrated container) of the kanban board, and work participants can directly access them when selecting the corresponding work note from the DO tab. The work chat room can be shared through the CHECK tab (or the second integrated container) of the Kanban board, and the work participant can directly access the work chat room when selecting the corresponding work chat room from the CHECK tab. The work object can be shared through the ACT tab (or third integrated container) of the Kanban board, and the work participant can directly access it when selecting the corresponding work object in the ACT tab.

In addition, the above description of the operation of the kanban board processing unit 310 can be equally applied to other components, that is, the kanban card processing unit 330, the business container processing unit 350, and the business processing unit 370. explanation is omitted.

The Kanban card processing unit 330 may insert a Kanban card according to the creation of a work project into the Kanban board. The Kanban card processing unit 330 may detect creation of a work project on the Kanban board and automatically generate a Kanban card for management of the work project. That is, Kanban cards can be generated for each individual work project that is generated according to the progress of the entire project, and the card status of the Kanban card can be synchronized with the progress stage of the corresponding work project and updated. The Kanban card processing unit 330 may receive user information collected for generating the Kanban board from the Kanban board processing unit 310 .

The Kanban card processing unit 330 may insert a Kanban card into the Kanban board for management of a specific work project. That is, the Kanban card processing unit 330 may control and process operations related to the Kanban card along with basic management functions such as creation, modification, and deletion of the Kanban card. The Kanban card generated by the Kanban card processing unit 330 can be inserted into the Kanban board and used to manage work projects and records.

Meanwhile, the Kanban card may be implemented by including at least one dedicated container that exclusively manages work notes, work chat rooms, and work objects, respectively. Here, the task note, task chat room, and task object may correspond to user-defined tasks, and the Kanban card may be implemented by selectively including containers for each user-defined task type.

In addition, the Kanban card processing unit 330, when the task instructions or task supplement instructions are uploaded to the Kanban card, converts the Kanban card on which the task instructions or task supplement instructions are uploaded to the Kanban card before the task instructions or task supplement instructions are uploaded. can be differentiated. In this case, the user can intuitively know whether new work instructions or work supplementary instructions have been uploaded only by the display state of the Kanban card.

In one embodiment, the Kanban card may be implemented by including, as a reminder condition, periodic generation of work notes or a work deadline based on a work flow. The kanban card may be defined including preset business conditions according to the type of business project. That is, the reminder condition may correspond to a condition for starting an operation of generating a reminder message provided through the work chat room according to the work progress situation, and predetermined actions to be performed by the work participant may be set as the reminder condition. For example, the kanban card may include a task condition for periodically generating task notes according to task progress or a task condition to be performed within a deadline set according to a task flow.

In addition, the kanban card is a task note for sharing basic tasks between task participants, a task object for sharing instructional tasks between task participants, and a plurality of task chat rooms related to the corresponding kanban card or task note as user-defined tasks. can be implemented including

In this case, the Kanban card can manage a plurality of work notes, work chat rooms, and work objects in a list form, and can be implemented by including a dedicated container for this (ie, a container for each user-defined work type).

Basically, business chat rooms associated with Kanban cards may allow limited access to business participants participating in the business project. That is, the kanban card can be used as a means to record and manage the overall progress of each business project, and can be used as a means to manage the work of the entire project within the kanban board.

In one embodiment, the Kanban card processing unit 330 may independently set a curation method for each of the first to third dedicated containers according to a user's preference. Here, the curation method may correspond to a method of providing corresponding information when a work note, work chat room, or work object associated with a Kanban card is inquired by a user.

For example, the kanban card processing unit 330 may sort and provide work notes according to time series or importance. In addition, the Kanban card processing unit 330 may sort and provide one-to-one work conversations with a specific person in the work chat room. In addition, the kanban card processing unit 330 may sort and provide business objects according to business instructors or business processors. Meanwhile, the Kanban card processing unit 330 may directly receive user settings to determine a curation method for each of the dedicated containers.

The work container processing unit 350 may embody per-user-defined-work-type containers associated with the work project on the Kanban card. Here, the user-defined tasks may include task notes, task chat rooms, task objects, etc., and the containers for each user-defined task type include a task note-only container (or a first dedicated container), a work chat room-only container (or a second dedicated container), and the like. ) and business object-only containers (or third-only containers).

That is, the work container processing unit 350 may embody a dedicated container (second dedicated container) for a work chat room related to a work project in response to the creation of a Kanban card by default. At this time, the materialization operation may correspond to a series of specific processes of creating a container dedicated to the work chat room and connecting it to the Kanban card. That is, the work container processing unit 350 may implement one of the containers for each user-defined task type as a container dedicated to the work chat room, and accordingly, a unique work chat room may be connected to the kanban card. Through this, various messages can be shared among various business participants participating in the corresponding business project.

In addition, the work container processing unit 350 may selectively materialize not only a container dedicated to work chat rooms, but also a container dedicated to work notes or a container dedicated to work objects as one of user-defined containers for each task type. That is, the task container processing unit 350 may implement one of the containers for each user-defined task type as a container dedicated to work notes (or a first dedicated container), and use one of the containers for each user-defined task type as a container dedicated to work objects (or a container dedicated to work objects). 3 dedicated containers).

In one embodiment, the task container processing unit 350 may implement a user-defined task container to exclusively process a corresponding user-defined task type through the user-defined task container. For example, if the user-defined task is a task note, the user-defined task container may correspond to a container dedicated to the task note. In addition, when the user-defined task is a task chat room, the user-defined task container may correspond to a container dedicated to the task chat room, and when the user-defined task is a task object, the user-defined task container may correspond to a container dedicated to the task object. That is, the work container processing unit 350 can implement the user-defined work container as a result of materializing the user-defined work container, and the user-defined work container can be inserted into the Kanban card and managed.

In one embodiment, the task container processing unit 350 may assign a unique identity link to the user-defined task container and support direct movement between containers for each user-defined task type through the user-defined task. For example, first to third links may be assigned as unique identification links to containers dedicated to work notes, containers dedicated to work chat rooms, and containers dedicated to work objects. At this time, if the work note n1 including the first link is shared through work chat room C2, the user can search for and select the work note n1 in the work chat room dedicated container, and the work note n1 shared in the work chat room C2 Through the first link, it is possible to directly move to a container dedicated to the work note associated with the corresponding work note n1. That is, the user can effectively move between containers for each user-defined task type by using the user-defined task and a unique identification link.

The task processing unit 370 may perform user-defined task-based task communication with task participants through a user-defined task container among containers for each user-defined task type. In the course of a work project, various types of user-defined tasks can be created and used among task participants, and user-defined tasks can be shared among task participants through each user-defined task container. In other words, business participants can share various messages through the business chat room in the course of a business project, and create business notes and business objects to manage and share business progress, thereby performing custom business-based business communication. have.

In one embodiment, the work processing unit 370 may materialize a work chat room (ie, a first work chat room) associated with a work project in a container dedicated to the work chat room. In one embodiment, the task processing unit 370 may materialize a user-defined task chat room (ie, a second task chat room) associated with a user-defined task in a container dedicated to the task chat room. In this case, when the user-defined task is a task note, the user-defined task chat room may correspond to a task note-based task chat room.

In one embodiment, the task processing unit 370 may implement a user-defined task as a text or binary file-based task message and provide the task message to the task chat room. For example, when a task note or task object is created as a user-defined task based on a text input by a task participant or a binary file uploaded by the task participant, a task message associated with the creation may be provided in the task chat room.

In one embodiment, the task processing unit 370 may provide a task message to the task chat room by implementing the user-defined task as a system message when an event occurs in another user-defined task. For example, when an event related to creation of a work note or work object occurs through another work chat room, a work message related to the creation may be provided to the work chat room.

In one embodiment, the task processing unit 370 may register a reminder event by tracking the conversation progress of the task message. For example, work messages shared through work chat rooms may include an explicit designation message for designating a specific user and an indirect designation message for indirectly designating a specific user but not explicitly designating a specific user. The task processing unit 370 may analyze the task message to create a reminder condition and create and register a reminder event related thereto.

In one embodiment, the task processing unit 370 may implement a user-defined task with a text or binary file-based task note and curate the task note in a container dedicated to the task note according to user settings. Work notes inserted into the container dedicated to work notes may be arranged in a predetermined priority according to user settings, and displayed according to the corresponding priority in response to a user's inquiry request.

In one embodiment, the work processing unit 370 may generate a work note event according to the creation of the work note. In one embodiment, the business processing unit 370 may implement a business object in a business object-only container by implementing a user-defined business as a business object. In one embodiment, the business processing unit 370 may generate a business object event when a business object is provided to an arbitrary chat room in a container dedicated to the business chat room.

In one embodiment, the task processing unit 370 may register a reminder event by tracking the task flow-based task progress status of the task object. In one embodiment, the task processing unit 370 may detect registration of a reminder event generated in a user-defined task. In one embodiment, the task processing unit 370 may create a reminder condition for a reminder event and provide a reminder message according to the reminder condition to the work chat room.

More specifically, the task processing unit 370 may detect registration of a reminder event when a predetermined reminder event is generated and registered from a user-defined task. When the registration of the reminder event is detected, the task processing unit 370 may create a reminder condition, and may generate a reminder message according to the reminder condition and share it with task participants through a task chat room.

In one embodiment, the task processing unit 370 may generate a reminder message by setting a task progress status of a user-defined task assigned to at least some of the task participants of the task project as a reminder condition. The task progress status of a user-defined task can be defined as planned, in progress, past, and confirmed, and a task deadline can be set according to each task progress status. The task processing unit 370 may generate and provide a reminder message to task participants associated with a corresponding user-defined task according to a task deadline associated with each task progress state.

In one embodiment, the task processing unit 370 may update the reminder message based on the number of times the same reminder message proceeds. That is, the task processing unit 370 may generate and provide a reminder message according to the reminder condition, and when the same reminder message is repeatedly generated, it may accumulate and count the number of progresses of the reminder message, and according to the counting number, the reminder message Messages can be updated.

In one embodiment, when a plurality of tasks are sequentially connected according to the task order, the task processing unit 370 integrally creates a reminder message reflecting the task order and shares it through a task chat room (eg, the first task chat room). can do. For example, when to-dos associated with a Kanban card are defined as a plurality of tasks and are sequentially connected to each other, the task processing unit 370 may generate and share a reminder message according to the order of connection. If the preceding task is completed, the task processing unit 370 may generate and share a reminder message for the next subsequent task.

In one embodiment, when an external user without access authority is invited to the work chat room, the work processing unit 370 may limit the access authority to the external user to access only the work chat room.

In one embodiment, the task processing unit 370 may be implemented by including a plurality of subcomponents that independently perform operations related to work notes, work chat rooms, and work objects as user-defined tasks. For example, the work processing unit 370 may be implemented by including a work note processing unit 371, a work chat room processing unit 373, and a work object processing unit 375. The business processing unit 370 may be implemented in various combinations of the business note processing unit 371, the business chat room processing unit 373, and the business object processing unit 375, and may be implemented as an independent component as needed. to be. Hereinafter, detailed operations of each component will be described.

The work note processing unit 371 creates a work note in the first dedicated container to share basic tasks among task participants participating in a specific work project. Task participants can create task notes through a dedicated interface provided in the task chat room associated with the Kanban card or the first dedicated container (or the DO tab of the Kanban card). The generated task note may be stored in association with the corresponding kanban card, added to the first integrated container of the kanban board, and shared as basic task content among task participants of the entire project. The work note may include basic work contents related to the progress of the work project, and may contain simple memos for information delivery purposes.

In addition, the work note may be created in the form of a file, and the file itself created or uploaded by the work participant may be defined as an independent work note and added to the Kanban card. For example, the first dedicated container may provide an interface for creating a work note, and when a file itself is uploaded by a work participant, the file may be converted into a work note and shared with other work participants.

In one embodiment, the work note processing unit 371 may create a work record written by a work participant and generated in the course of a work project as a work note, and insert the work note into the first dedicated container time-sequentially. The work notes may be stored in association with one or more kanban cards, and may be managed through the first integrated container of the kanban board according to the progress stage of the entire project. To this end, the work note processing unit 371 may insert the work notes into the first dedicated container in a chronological order based on the creation time of the work notes.

In one embodiment, the work note processing unit 371 may provide a work message including a permanent link to the work note to the work chat room. Here, the work chat room may basically correspond to a work chat room shared through the second integrated container of the Kanban board. That is, the record on the work note can be shared as a work message through the work chat room that is uniquely connected to the Kanban card. If external sharing is set and a permanent link is inserted into the work note, the work message related to the work note can also be shared. A corresponding permanent link may be inserted. Since the work chat room in which the work message is shared is shared outside the Kanban card through the second integrated container, other people who do not participate in the work project can also access the work note through the permanent link of the work message.

The work chat room processing unit 373 creates a work chat room in which business participants performing work projects participate in the second dedicated container (or work chat room dedicated container), and generates work messages and messages according to the creation of chat messages, work notes, and work objects. Reminder messages can be shared in work chat rooms. In this case, the work chat room may include a first work chat room related to the Kanban card and a second work chat room related to the work note.

That is, when a work note is created, the work chat room processing unit 373 creates a second work chat room related to the work note in the second dedicated container to share conversations and work messages related to the work note among work participants. That is, the second work chat room may correspond to a work chat room uniquely connected to a specific work note. Therefore, the work chat room processing unit 373 can create a second work chat room and insert it into the second exclusive container whenever a new work note is created in one kanban card, and the work participants associated with the work note can create a second work chat room in the second dedicated container. You can participate in the work chat room and share conversations related to the work note.

Meanwhile, the second work chat room may share work messages as well as conversations related to work notes, and may provide a creation function related to work objects. That is, a work object (or task) created in association with the work note may be created through a dedicated interface provided in the second work chat room. Accordingly, records (including creation, modification, and deletion) of multiple work objects associated with one work note can be shared with other work participants through the second work chat room as work messages. In addition, the work message shared through the second work chat room may include a first reminder message related to the work object.

In addition, the work chat room processing unit 373 stores and manages access rights for each work chat room, participants in the conversation, and message threads transmitted through the work chat room, for example, conversation messages transmitted or shared through the work chat room, shared files or folders, etc. You can save business data or save access routes. That is, the work chat room processing unit 373 stores data related to each work chat room, and even if a conversation in a specific work chat room is temporarily or permanently terminated, data on the corresponding work chat room may be stored. Further, when the corresponding work chat room is resumed later, data related to the corresponding work chat room may be provided. In addition, the work chat room processing unit 373 may process and store the work chat room in the form of a file object when saving the work chat room.

In addition, the work chat room processing unit 373 sends among the chat messages or notification signals transmitted through the work chat room to each user, such as each work-related person participating in the work chat room, among the chat messages or notification signals that have not yet been read by each user. One or more numbers may be calculated for each user to provide the number of unread messages.

Here, if there is one or more work chat rooms created in relation to a specific kanban card or work note, the work chat room processing unit 373 may provide the number of unread messages for each work chat room together with a list of work chat rooms. The work chat room processing unit 373 may include and display the list of work chat rooms and the number of unread messages for each work chat room on the Kanban board.

In one embodiment, when a kanban card is created, the work chat room processing unit 373 creates a first work chat room associated with the corresponding kanban card in a second dedicated container, so that work participants talk about work projects and work messages about work notes. can share. That is, the first work chat room may correspond to a work chat room uniquely connected to a specific Kanban card. Therefore, the work chat room processing unit 373 can provide one first work chat room within one Kanban card, and business participants associated with the Kanban card participate in the first work chat room to discuss all activities of the corresponding work project. Information can be shared through work messages.

For example, the first work chat room may provide information on note records, conversation contents, task records, etc. related to the corresponding kanban card in the form of messages. Accordingly, task participants can check the records of all activities of the corresponding task project through task message inquiry, and can also check the message records sorted in chronological order or by task handler or task instructor. In addition, the work message shared through the first work chat room may include a second reminder message related to the work note.

In one embodiment, the work chat room processing unit 373 may create a work link directly accessible to a work object in the process of creating a work message and insert it into the work message. The work messages created in this way can be shared through the corresponding task chat room, and the task participants who participated in the task chat room can directly access the relevant task object through the task link included in the task message without resorting to a separate access action to view the related tasks. You can easily check the content.

On the other hand, even if it is possible to check a work message including a work link by participating in a work chat room, access through the work link may be blocked if there is no access right to the work object. For example, a task message including a task link can be shared with task participants related to the kanban card through the first task chat room, and in the case of task participants not related to the corresponding task object, access to the first task chat room and Separately, access to the corresponding business object can be blocked.

In one embodiment, the work chat room processing unit 373 may create a one-to-one work chat room in the second dedicated container when receiving a request for a one-to-one work chat with a specific business participant regarding a specific work object. The one-to-one business chat room inserted into the second exclusive container can be searched in list form in the CHECK tab of the Kanban card together with the first business chat room associated with the Kanban card and the second business chat room associated with the work note. The business chat room processing unit 373 can basically create a related business chat room whenever a kanban card or business note is newly created, and one-on-one business in which only limited business participants selectively participate according to the business participant's one-to-one business conversation request. You can create a chat room. In addition, the one-to-one business chat room may be added to the second integrated container of the Kanban board and managed separately from the second exclusive container of the Kanban card.

In one embodiment, the work chat room processing unit 373 inserts a work note or a work notification message including a direct link to a work object into the one-to-one work chat room so that it is always visible through the one-to-one work chat room. The one-to-one work chat room can be managed separately from the Kanban card, and in this case, it is possible to access the work note or work object of the Kanban card through a link. The work chat room processing unit 373 is a notice work message that is always displayed on the upper part of the chat window of the one-to-one work chat room, and may provide a means of access to the work node or work object by providing a link. The notification work message may be implemented to be generated in the form of a work message and always displayed in the work chat room. The notification work message may be displayed through the upper or lower part of the chat window in the work chat room, but is not necessarily limited thereto and may be displayed through a predetermined area defined in the work chat room.

In one embodiment, when a task participant shares a general message in the task chat room, the task chat room processing unit 373 may first query the task participant whether or not there is a corresponding task. The work chat room processing unit 373 may provide a work chat room as a dedicated space for work-related communication, and may perform an operation of determining whether a corresponding work participant is a person related to the work when a general message is shared. That is, the work chat room processing unit 373 may differentially display general messages in the work chat room according to whether work relevance exists.

In one embodiment, the task chat room processing unit 373 may convert the task message into a task message by displaying the task in a general message when a corresponding task exists. At this time, the corresponding task displayed in the general message may include object identification information for identifying a related task object. In another embodiment, the work chat room processing unit 373 may insert a link for a corresponding task into a corresponding task displayed in the converted task message. In this case, the inserted link may correspond to a work link or a permanent link.

In one embodiment, the business chat room processing unit 373 detects a business object related to the business participant when the business participant shares a conversation message through the first business chat room, displays the business object in the conversation message, and converts it into a business message. can do. More specifically, the first work chat room corresponds to a work chat room uniquely generated in the Kanban card, and unlike the second work chat room, access rights may be granted to all work participants participating in the corresponding work project. Accordingly, the conversation message shared in the first task chat room can be shared with other task participants regardless of whether the task object participates or not. However, it is necessary to additionally provide information on whether the conversation message was written by a business participant associated with a business object, if necessary. Accordingly, the business chat room processing unit 373 detects the business object associated with the business participant who created the conversation message, By displaying the corresponding work object in the chat message, an operation of automatically converting the work message to the work message can be performed.

In addition, the business chat room processing unit 373 displays each business object together in the conversation message when there are multiple business objects associated with the business participant who created the conversation message and converts them into one business message, or separates each business object in the conversation message. It can be displayed as and converted to each work message. In another embodiment, the business chat room processing unit 373 may display a business object in a conversation message and convert it into a business message, and the business object displayed in the conversation message may correspond to object identification information for identifying the business object.

In one embodiment, the work chat room processing unit 373 may insert a work link accessible to the work object in the process of converting the work message into a work message. Accordingly, the conversation message input through the first work chat room can be converted into a work message including a work link, and the work chat room processing unit 373 provides direct access to the corresponding work object according to the selection of other work participants. can do.

In one embodiment, when a file is uploaded through the work chat room, the work chat room processing unit 373 may process the file as a work note or work object under the control of a work participant. The work chat room processing unit 373 may provide an interface for file upload in the work chat room. Through this, the task participant can control the conversion of the file to a task note or task object along with file upload.

The task object processing unit 375 may create a task object including a task instructor, a task handler, and task details in a third dedicated container to share task instructions among task participants. In addition, the business object processing unit 375 may provide a function of creating a business object through the second business chat room. Accordingly, task participants can create task objects (or tasks) through the interface while participating in the second task chat room. The created task object may be stored in association with the corresponding task note and the corresponding kanban card, and may be added to the third integrated container of the kanban board and shared as indicative task content among task participants of the entire project.

On the other hand, the work object may include an execution instruction task in which the task director instructs the task handler to perform a new task in relation to the progress of the work project, and a supplementary instruction task in which the task supervisor confirms the task processing details and instructs additional supplementation.

In one embodiment, the work object processing unit 375 may create a work object based on a work flow between a work director and a work processor. In this case, the business object may further include a business deadline, and the business deadline may include a business start date and a business deadline. That is, a work object can be defined as various tasks necessary for the progress of a work project, and a task deadline (or task deadline) can be automatically set according to the precedence relationship with other tasks in the work flow based on the time of creation. have. In addition, the business object may include a business instructor instructing business processing and a business processor to process business performance, respectively.

In one embodiment, the work object processing unit 375 may manage the work flow-based work object as a work state. At this time, the business object may further include a business state. For example, a work object created in response to the progress of a work project may include any one of new, in progress, finished, and confirmed as a work status. As another example, the task status may be defined as in progress, confirmed, supplemented, and supplemented according to the task progress stage.

That is, the business object processing unit 375 may monitor the progress of the business object, update the business status of the business object according to the progress, and provide information on the progress of the business object. Business participants can check the list of business objects related to the corresponding business project through the 3rd exclusive container of the Kanban card, access each business object to check the individual business status, and through the 3rd integrated container of the Kanban board, You can check the status and status of business objects related to the project.

The control unit 390 controls the overall operation of the business processing device 130, and controls flow or data flow between the kanban board processing unit 310, the kanban card processing unit 330, the business container processing unit 350, and the business processing unit 370. can manage

4 is a flowchart illustrating a Kanban-based business processing method according to the present invention.

Referring to FIG. 4 , the business processing device 130 may generate a user-based Kanban board for managing the entire project through the Kanban board processing unit 310 (step S410). At this time, the kanban board may include first to third integration containers for integrating and managing work notes, work chat rooms, and work objects associated with each work project, and the first to third integration containers are DO, CHECK, respectively And it may correspond to the ACT tap.

Thereafter, the business processing device 130 may generate a business project in response to a user signal from the user terminal 110, and display a kanban card according to the generation of the corresponding business project on the kanban board through the kanban card processing unit 330. It can be created and inserted (step S430).

In addition, the business processing device 130 will embody per-user-defined-work-type containers associated with the business project on the Kanban card through the business container processing unit 350 It can (step S450). The task processing device 130 may perform user-defined task-based task communication with task participants through a user-defined task container among containers for each user-defined task type through the task processing unit 370 (step S470).

In addition, the business processing device 130 may create a reminder message according to the progress of a business project related to the Kanban card through the business processing unit 370 and share it through a business chat room. For example, the reminder message generated by the task processing unit 370 may be generated according to the creation cycle or task deadline for the task note of the Kanban card and provided to related task participants. That is, the task processing unit 370 may generate a reminder message by setting a periodic request for creation of a task note or a task deadline based on a task flow of a task object for at least some of the task participants as a reminder condition.

5 is a view for explaining an embodiment of a Kanban board according to the present invention.

Referring to FIG. 5 , the task processing device 130 may visualize and provide kanban cards 530 according to a task progress state 510 through a kanban board 500 . Here, the kanban cards 530 may be classified and arranged according to the work progress status 510, but are not necessarily limited thereto, and may be arranged according to various criteria such as a department in charge, a work orderer, a work manager, a work deadline, and a work flow. may be sorted accordingly.

According to an embodiment, task instructions may be uploaded to the Kanban card 530 'in progress', and task process details may be uploaded to the Kanban card 530 'in progress'. In addition, when a business manager or business director selects one of the Kanban cards 530, the business processing device 130 may provide a user interface for the corresponding Kanban card. In this case, the user interface may provide various functions related to the Kanban card 530 (eg, WRITE, UPLOAD, DELETE, and CREAT CHAT-ROOM).

For example, the user can access the detailed screen of the Kanban card 530 through this, and can also access work notes, work chat rooms, and work objects related to the work project. In addition, in the case of a task instructor, it is possible to input task supplementation instructions for task processing details through a task chat room associated with the Kanban card 530 . At this time, for more specific instructions, the work director may enter a task supplementation instruction through a work chat room associated with a specific work note. In this case, a new work object related to the work supplement instruction is created and uploaded to the corresponding Kanban card can In addition, the Kanban card 530 updated by the creation of a new work object may be differently displayed in thickness, brightness, color, etc. on the Kanban board 500 compared to other Kanban cards without a new issue.

Meanwhile, the Kanban board 500 may include various tabs in addition to the Kanban card area 520 where the Kanban cards 530 are displayed. For example, the Kanban board 500 may include D (DO), C (CHECK), and A (ACT) tabs, and each tab includes a list of business notes (or a list of files) belonging to the Kanban board 500, A business chat room list and a business object list (or task list) may be displayed.

Also, tabs D, C, and A of the Kanban board 500 may correspond to the first to third integration containers, respectively. That is, work notes that can be searched on the D tab can be inserted and managed in the first integrated container, work chat rooms that can be searched on the C tab can be inserted and managed in the second integrated container, and work objects that can be searched on the A tab can be managed. It can be inserted into and managed by a third integration container.

In addition, a link to a related Kanban card 530 may be included in each work note, work chat room, and work object (or task) on the list displayed in each tab. That is, the user can quickly access the corresponding Kanban card 530 just by selecting a specific object on the list. In addition, each of the work note, work chat room, and work object may include a permanent link for external sharing. In this case, the user may directly access the object by selecting it from the list.

6 is a diagram for explaining an embodiment of a Kanban card according to the present invention.

Referring to FIG. 6 , when a new work project is created on the kanban board, the work processing device 130 can create and insert a kanban card 530 for management of the work project. The generated kanban card 530 can be visualized and displayed on the kanban board, and a task participant can select a specific kanban card 530 and move to a detailed screen.

The detailed screen of the Kanban card 530 may include a plan area 600, a DO tab 610, a CHECK tab 620, and an ACT tab 630. In this case, the DO tab 610 may correspond to a first dedicated container, the CHECK tab 620 to a second dedicated container, and the ACT tab 630 to a third dedicated container. Here, in the plan area 600, a brief description of the corresponding Kanban card 530 may be displayed. For example, in the plan area 600 , information about the work contents of the kanban card 530 , work period, participants, kanban board, and the like may be displayed.

In addition, the Kanban card 530 may provide inquiry information in the form of a work note list 640 through each tab. For example, the DO tab 610 may provide a list of work notes. The work note list may correspond to a list of work notes registered in the course of a work project. The work note list may include information on files registered as work notes as well as work notes.

The CHECK tab 620 may provide a list of business chat rooms. The work chat room list may correspond to a list of work chat rooms created in the course of a work project. For example, the work chat room list may include a first work chat room uniquely related to the Kanban card 530, a second work chat room created for each work note, and a one-to-one work chat room created according to a one-to-one work chat request.

A work object list may be provided through the ACT tab 630 . The work object list may correspond to a list of work objects created in the course of a work project. In this case, the work object list may display the work objects by classifying them according to the work progress stage. For example, business objects may be classified and displayed as new (S1), busy (S2), done (S3), and confirmed (S4) on the business object list.

In addition, the business processing device 130 may provide a unique interface 650 through each tab of the Kanban card 530 . Each interface 650 may include commands for entities managed by a corresponding tab. For example, each interface 650 may include commands for object creation, modification, and deletion.

In addition, the operation performed through each tab can be shared through the work chat room as a work message (or system message). For example, when a work note is created in the DO tab, a work message (or system message) related to the work note creation may be created and shared through the first work chat room. When a work object is created in the ACT tab, a work message (or system message) related to the work object creation is created and can be shared through the first work chat room or the second work chat room.

7 is a diagram illustrating a process of sharing a work chat room and a reminder according to the present invention.

Referring to FIG. 7A , the business processing device 130 may create one business chat room (ie, a first business chat room) 710 basically corresponding to a specific Kanban card 530 . In the corresponding work chat room 710, various operations related to work processing, such as writing work notes, uploading files, inputting chat messages, and creating work objects (tasks), can be performed. To this end, independent interfaces 710 for various functions may be provided in the first work chat room 710 . Meanwhile, the second work chat room for work notes may also provide the same functions as the first work chat room 710 .

As a result, the first work chat room 710 can provide all activities related to the kanban card 530 as work messages in the chat room in chronological order, through which the work participants can easily understand the work flow.

In FIG. 7A , the task supplementation instruction may be input through the first task chat room 710 . In addition, the work complement instructions input through the first business chat room 710 are automatically uploaded to the corresponding kanban card 530 in real time, so that the work progress through the first business chat room 710 and the corresponding first business chat room 710 It can be shared and synchronized with the related Kanban card 530 in real time.

Meanwhile, in FIG. 7A, a case in which a task supplementation instruction is input through the first work chat room 710 is exemplified, but in another embodiment, after work supplement instructions after the work supplement instruction are also input through the first work chat room 710, It can be uploaded to the Kanban card 530. In another embodiment, even for the Kanban card 530 that is in progress or being checked, after work instructions or business process details are entered through the first business chat room 710, they can be uploaded to the related Kanban card 530. have.

After all task supplementary instructions and task supplementary details are entered through the first task chat room 710, when the task handler confirms or approves the task supplementary content, the same content is reflected on the corresponding Kanban card 530, and the corresponding Kanban card 530 may move to a supplementary completion step. Meanwhile, the above contents applied to the first work chat room 710 may equally be applied to the second work chat room related to work notes.

Referring to FIG. 7B , the business processing device 130 may provide one first business chat room 710 for each kanban card and one second business chat room 750 for each business note. That is, the work chat room 711 may be created in connection with a kanban card or work note, and respective work participants may perform various work communications related to the work through the work chat room 711 . For example, when a work note or a work object (or task) is created, work messages 730 and 740 associated with the corresponding operation may be created and displayed through the work chat room 711 .

In this case, the creation of work notes can be performed in the first work chat room 710, and the creation of work objects can be performed in the first and second work chat rooms 710 and 750. Also, it may be done within the DO tab or ACT tab of the Kanban card. In any case, work messages 730 and 740 related to related operations may be displayed through the work chat room 711 . Therefore, the task participants can check the flow of the task in chronological order by checking the task message in the task chat room 711 .

Referring to FIG. 7C , the task processing device 130 may share a task message related to a task object through the second task chat room 750 . In addition, the work message shared through the second work chat room 750 may be automatically uploaded to the corresponding Kanban card 530 in real time. In addition, work notes can be managed in the form of a list through the DO tab of the Kanban card 530, and a second work chat room 750 can be created and managed for each work note 640. That is, as a result of uniquely connecting the second work chat room 750 for each work note 640, a record of the corresponding work note 640 can be created as a work message and shared with work participants through the second work chat room 750. have.

Referring to FIG. 7D , the business processing device 130 may basically provide one first business chat room 710 for each kanban card 530, and one second business chat room 750 for each business note 640. ) can be provided. Accordingly, when a plurality of work notes 640 are created, a plurality of second work chat rooms 750 may be created. Business participants can perform various business communications related to the corresponding business project and the corresponding business note 640 through the first business chat room 710 and the second business chat room 750 .

For example, when a work object (or task) is created, a work message 740 associated with the corresponding operation may be generated and displayed through the second work chat room 750, and when a work note 640 is created, the corresponding task message 740 is generated. A work message 730 associated with the operation may be generated and displayed through the first work chat room 710 . At this time, the created work note 640 and work object can be inserted into and managed in the first and third dedicated containers of the Kanban card 530, respectively, and can be inquired from the DO tab and the ACT tab, respectively.

Meanwhile, the task note 640 or the task object may be created in the first task chat room 710 or the second task chat room 750, or in the DO tab or the ACT tab of the Kanban card 530. have. In any case, work messages 730 and 740 related to related operations may be displayed through the corresponding work chat room. Therefore, the task participants can check the work project or the flow of each task in chronological order by checking the work messages in the work chat room 711 .

8 and 9 are flowcharts illustrating various embodiments of sharing work messages in a Kanban-based work process according to the present invention.

Referring to FIG. 8 , the task processing device 130 may create a Kanban board related to the entire project. The task processing device 130 may receive a user signal requesting generation of a Kanban board from the user terminal 110 in the previous step.

In addition, the kanban board may include a user interface (UI) for performing various functions. The user interface is a UI to support collaboration through a kanban board or kanban card, and the UI includes creation of work chat rooms, designation of chat room participants, simple sharing of kanban boards, input of work data related to kanban boards, inquiry of work chat rooms or reading of data. and instructions for receiving a user signal such as data attachment.

The work director terminal 110a may create a work project. The task indicator terminal 110a may provide an interface provided by the task processing device 130, and the task processing device 130 may generate a kanban card and insert it into the kanban board when a task project is generated. Thereafter, the business processing device 130 may create a business chat room corresponding to the Kanban card. That is, a work chat room can be created for each Kanban card to manage work records related to a work project related to the Kanban card.

Meanwhile, the creation time of the work chat room may be the time when the Kanban card is created, but is not necessarily limited thereto, and the work processing device 130 receives a separate request from the user terminal 110 even when the Kanban card is created. It is also possible to wait for the creation of the business chat room until there is a signal. Therefore, prior to the creation of the work chat room, work instructions or work processing may have already been uploaded to the kanban board or kanban card.

After the business chat room is created, business participants such as the business director terminal 110a and the business manager terminal 110b may participate in the business chat room. Thereafter, the task instructing terminal 110a may input the content of the task instruction through the task chat room. The work instruction input through the work chat room may be displayed in the form of a work message. The task processing device 130 may create a task object according to the task instructions input by the task director terminal 110a, and the task object may be uploaded to and registered in the Kanban card.

At this time, the creation of the business object may be performed on the Kanban card instead of the business chat room, and in this case, a business message related to the creation of the business object may be generated. The work message may be displayed through the work chat room and shared with other work participants (S810).

When the task instructions are uploaded to the Kanban card, the task processing device 130 may transmit the task instructions to the task handler terminal 110b. The business processor may process the business according to the business instructions received from the business director through the business processing device 130 and input the business processing details into the business processing device 130 . The business processing contents input by the business processor terminal 110b may be input through the business chat room and uploaded to the Kanban card by the business processing device 130 .

For example, when a business manager transmits a file object corresponding to business processing details through a business chat room, the business processing device 130 may upload the file object to a Kanban card associated with the business chat room.

At this time, the input of the work processing details may be performed on the Kanban card instead of the work chat room, and in this case, a task message regarding the input of the work processing details may be generated. The work message may be displayed through the work chat room and shared with other work participants (S830).

Thereafter, the task instructor may check the task processing contents uploaded by the task processor and input a task supplementation request for a part requiring supplementation. The task complementation request may be entered through the task chat room. When the task director inputs a task supplementation request, the task processing device 130 may upload the task supplementation request to the Kanban card and provide the task supplementation request to the task handler terminal 110b.

In addition, if a deadline is set for the task supplementation request, that is, if information on the task supplementation deadline is included in the task supplementation request, the task processing device 130 may generate a task supplementation reminder message. That is, the task processing device 130 may generate a task supplement reminder message and provide it to the task handler terminal 110b through the task chat room when the task supplement deadline is imminent.

Upon receiving the task supplementation request and the task supplementation reminder message through the task handler terminal 110b, the task handler may correct, edit, change, or rewrite the task instructions according to the task supplementation request and input the task supplementation details. The business supplementary information may be directly entered into the Kanban card or may be entered through a business chat room. When the task processing device 130 receives task supplementary information from the task processor terminal 110b, it can upload the entered task supplementary information to the corresponding Kanban card.

Referring to FIG. 9 , the business processing device 130 may create a Kanban board, and the business director terminal 110a may create a business project. When a business project is created, the business processing device 130 may create a kanban card and insert it into the kanban board.

Thereafter, the business processing device 130 may create a first business chat room corresponding to the Kanban card. The first work chat room may be created and managed independently of the second work chat room corresponding to the work note. That is, the first work chat room may be uniquely created for each Kanban card and manage work records of work projects related to the Kanban card.

After the first task chat room is created, task participants such as the task director terminal 110a, the task manager device 1 110b, and the task handler device 2 110c may participate in the first task chat room. Thereafter, the task directing terminal 110a may input task instruction content through the first task chat room. The work processing device 130 may generate a work note by receiving the input of the work instruction as a request signal for generating a work note. When the work note is generated, the work processing device 130 may share the work message 1 related thereto through the first work chat room (S910).

In addition, the work processing device 130 may create a second work chat room associated with the work note according to the creation of the work note. In the second work chat room, only business participants related to the corresponding work note may participate. In FIG. 9 , business participants of the business director terminal 110a and the business manager terminal 2 110c may participate in the second business chat room, and the business participants of the business manager terminal 1 110b may be restricted from participating in the chat room.

The task instruction input by the task director may be delivered to the task participant of the task handler terminal 2 110C through the second task chat room, and the task participant may request creation of a task object to perform the task. The business processing device 130 may create a business object in response to receiving the request, and the business object may be uploaded and registered to the Kanban card. At this time, task message 2 according to the creation of the task object is generated and displayed through the second task chat room, so that it can be shared with other task participants (S930).

In addition, according to the progress of the task thereafter, the task processing content can be input through the task handler terminal 2 (110c) and reflected in the task object, and a task message is generated accordingly to communicate with other task participants through the second task chat room. can be shared with

On the other hand, if the work performance deadline is set in the work instructions, that is, in the state where the work performance deadline related to the work note is set, the work note is not updated (for example, work note record) despite the passage of the deadline The processing device 130 may generate a task performance reminder message. In this case, the work note may include information about the deadline for performing the task, and the deadline for performing the task for each work note may be managed through a kanban card (plan). As a result, the task processing device 130 may generate a task performance reminder message when the task performance deadline is imminent or has elapsed, and share it as a task message through the first task chat room or the second task chat room, Through this, it is possible to effectively inform the work participants of the urgency of the work process related to the work note.

10 is a diagram for explaining an embodiment of a reminder sharing process according to the present invention.

Referring to FIG. 10 , the business processing device 130 may create a Kanban board for managing the entire project. A kanban card for managing a work project may be created and inserted into the kanban board, and a first work chat room uniquely related to the kanban card may be created according to the generation of the kanban card. At this time, the created first work chat room may be inserted into and managed in the second integrated container of the Kanban board.

Depending on the creation of the Kanban card, the work of the related work project can be started, and a predetermined work deadline can be set for each Kanban card, work note, and work object.

When the business deadline is imminent (eg, 3 days before the business deadline) (S1010), the business processing device 130 may generate and provide a related reminder message. For example, the business processing device 130 may detect whether the business deadline is related to the Kanban card (step S1020), and if it is related to the Kanban card, a first reminder message is created and shared through the first business chat room. It can be done (S1030). If the work deadline is related to the work note, a second reminder message may be created and shared through the second work chat room (S1040). On the other hand, if the task due date is related to the task note, a case where the task object included in the task note is imminent may be included.

For example, if a task performance deadline is set in the work instructions, that is, if the task performance deadline for periodic recording of work notes is set and there is no record of work notes despite the lapse of the deadline, the work processing device (130 ) may generate a reminder message (or first reminder message) related to task performance. At this time, the kanban card may include information about the deadline for performing duties.

As a result, the business processing device 130 may create a reminder message and share it through a business chat room when the deadline is imminent or exceeded in relation to the progress of the business, and through this, the business participants can be reminded of the urgency of the business process. can be communicated effectively.

Meanwhile, the task processing device 130 according to the present invention can provide an effective tool for project progress and management through a kanban board and a kanban card. In addition, the business processing device 130 may provide a kanban board and a dash board for each kanban card. More specifically, the dashboard of the Kanban board can provide statistical analysis of Kanban cards (PLAN), D (DO), C (CHECK), and A (ACT) belonging to the Kanban board, and the dash of the Kanban card Analysis information on the corresponding Kanban card (P) and statistical analysis on D, C, and A belonging to the corresponding Kanban card can be provided through the board.

Although the above has been described with reference to preferred embodiments of the present invention, those skilled in the art will variously modify and change the present invention within the scope not departing from the spirit and scope of the present invention described in the claims below. You will understand that it can be done.

100: business processing system
110: user terminal 130: business processing device
500: Kanban board 510: Work progress status
520: Kanban card area 530: Kanban card
600: plan area 610: DO tab
620: CHECK tab 630: ACT tab
640: list of work notes 650: interface
710: first business chat room 711: business chat room
720: interface 730, 740: business message
750: second business chat room

Claims (24)

a kanban board processing unit that newly creates a kanban board;
a kanban card processor for inserting a kanban card according to the creation of a business project into the kanban board;
a work container processing unit that embodies per-user-defined-work-type containers associated with the work project on the Kanban card; and
A Kanban-based business processing device including a business processing unit that performs business communication based on a user-defined task with business participants through a user-defined task container among the containers for each user-defined task type.
The method of claim 1, wherein the Kanban card processing unit
A Kanban-based business processing device characterized in that a new Kanban card is inserted into the Kanban board whenever creation of the business project is detected.
The method of claim 1, wherein the business container processing unit
A Kanban-based business processing device characterized in that the user-defined task container is implemented to exclusively process a corresponding user-defined task type through the user-defined task container.
The method of claim 3, wherein the business container processing unit
A Kanban-based task processing device characterized in that a unique identity link is given to the user-defined task container and direct movement between containers for each user-defined task type is supported through the user-defined task.
The method of claim 1, wherein the business container processing unit
A Kanban-based business processing device characterized in that one of the containers for each user-defined business type is implemented as a container dedicated to the business chat room.
The method of claim 5, wherein the business processing unit
A Kanban-based business processing device characterized in that a business chat room associated with the business project is materialized in a dedicated container for the business chat room.
The method of claim 6, wherein the business processing unit
A kanban-based business processing device characterized in that a user-defined business chat room associated with the user-defined business is materialized in a dedicated container for the business chat room.
The method of claim 6, wherein the business processing unit
A Kanban-based business processing device characterized in that the user-defined business is implemented with a text or binary file-based business message and the business message is provided to the business chat room.
The method of claim 8, wherein the business processing unit
When an event occurs in another user-defined task, the user-defined task is implemented as a system message and the task message is provided to the task chat room.
The method of claim 8, wherein the business processing unit
A kanban-based business processing device characterized in that a reminder event is registered by tracking the conversation progress of the business message.
The method of claim 1, wherein the business container processing unit
A Kanban-based business processing device characterized in that one of the containers for each user-defined task type is implemented as a container dedicated to work notes.
The method of claim 11, wherein the business processing unit
A Kanban-based business processing device characterized in that the user-defined task is implemented as a text or binary file-based work note and the work note is curated in a container dedicated to the work note according to user settings.
The method of claim 12, wherein the business processing unit
A Kanban-based business processing device characterized in that a work note event is generated according to the generation of the work note.
The method of claim 1, wherein the business container processing unit
Kanban-based business processing apparatus characterized in that one of the containers for each user-defined business type is implemented as a container dedicated to business objects.
The method of claim 14, wherein the business processing unit
A Kanban-based non-processing device characterized in that the user-defined task is implemented as a task object and the task object is implemented in a container dedicated to the task object.
The method of claim 14, wherein the business processing unit
A Kanban-based business processing device characterized in that a business object event is generated when a business object is provided to an arbitrary chat room in a container dedicated to a business chat room.
The method of claim 15, wherein the business processing unit
Kanban-based business processing device, characterized in that for registering a reminder event by tracking the business flow-based business progress status of the business object.
The method of claim 1, wherein the business processing unit
A Kanban-based task processing device characterized in that for detecting registration of a reminder event generated in the user-defined task.
The method of claim 18, wherein the business processing unit
A kanban-based business processing device characterized in that for generating a reminder condition of the reminder event and providing a reminder message according to the reminder condition to the business chat room.
The method of claim 19, wherein the business processing unit
The kanban-based task processing device characterized by generating the reminder message by setting a task progress status of a user-defined task assigned to at least some of the task participants of the task project as the reminder condition.
The method of claim 20, wherein the business processing unit
A kanban-based business processing device characterized in that the reminder message is updated based on the number of times the same reminder message progresses.
The method of claim 21, wherein the business processing unit
When the plurality of tasks are sequentially connected according to the work order, a reminder message reflecting the work order is integrated and shared through the work chat room.
The method of claim 1, wherein the business processing unit
A kanban-based business processing device characterized in that, when an external user without access authority is invited to the business chat room, access authority is restricted so that the external user has access only to the business chat room.
Creating a new Kanban board;
inserting a kanban card according to the creation of a business project into the kanban board;
embodying per-user-defined-work-type containers associated with the work project in the Kanban card; and
A task processing method performed in a Kanban-based task processing device including; performing task communication based on a user-defined task with task participants through a user-defined task container among containers for each user-defined task type.

Images