A product R & D method, device and electronic equipment based on lean kanban

Abstract

The present invention discloses a product R & D method, device and electronic device based on lean kanban. The method includes: generating a lean kanban in advance according to product data; obtaining product development requirements and associating the product development requirements with the lean kanban; splitting user stories according to the product development requirements in the lean kanban, splitting the user stories into subtasks, and assigning the split subtasks to corresponding processors; monitoring the processing process of the subtasks of the processors through the lean kanban, and when it is detected that the subtasks are processed and the product has no defects, initiating product launch to complete the product launch. The lean kanban of the embodiment of the present invention provides a visual process, visual work items, visual personnel division of labor, visual work item hierarchy, and visual work item association / dependency, supporting project managers to manage the development progress of the team, being able to control the development quality, and forming a feedback loop.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and particularly to a product R & D method, device and electronic device based on a lean kanban. Background Art

[0002] Lean Production (LP for short) is the laudatory name given by experts of the International Motor Vehicle Program (IMVP) at the Massachusetts Institute of Technology in the United States to the Just In Time (JIT) production method of Toyota in Japan. The lean production method takes the automotive industry, which pioneered the mass production method and the JIT lean production method, as an example, and is summarized theoretically.

[0003] At present, most company project teams use physical kanbans to manage project progress. Different project teams have different kanban design methods. The common point is that each card on the kanban represents a task, and task allocation and transfer are carried out during regular meetings facing the physical kanban. Usually, a new card is written when there is a new task, and then it is moved in the swim lane of the task life cycle and removed from the kanban after completion. Physical kanbans pose great challenges to task archiving and traceability. A small number of companies use electronic kanbans, mostly pre-set conventional kanbans, which can only view the flow of tasks and do not have the function to adapt to all project teams. Since physical kanbans are not electronicized, they do not support task archiving and querying.

[0004] Existing agile kanbans do not support the lean R & D mode of tasks and cannot configure the kanban according to the R & D management of different project teams.

[0005] Therefore, the existing technology still needs to be improved and developed. Summary of the Invention

[0006] In view of the deficiencies of the above-mentioned existing technology, the purpose of the present invention is to provide a product R & D method, device and electronic device based on a lean kanban, aiming to solve the technical problem that existing agile kanbans do not support the lean R & D mode of tasks and cannot configure the kanban according to the R & D management of different project teams.

[0007] The technical solution of the present invention is as follows:

[0008] A product R & D method based on a lean kanban, the method comprising:

[0009] Generating a lean kanban in advance according to product data;

[0010] Obtaining product development requirements and associating the product development requirements with the lean kanban;

[0011] Split user stories according to product development requirements in the Lean Kanban, break them down into subtasks according to the user stories, and assign the split subtasks to the corresponding handlers;

[0012] Monitor the subtask processing process of the handler through the Lean Kanban. When it is detected that the subtask is completed and the product is defect-free, initiate the product launch and complete the product launch.

[0013] Further, the generation of the Lean Kanban based on product data in advance includes:

[0014] Obtain product line data in advance and configure status columns according to the product line data;

[0015] Configure swimlanes according to the product type;

[0016] Assemble the status columns and swimlanes into a Lean Kanban template;

[0017] Obtain the personnel of the execution team for the Lean Kanban, write the execution team personnel into the Lean Kanban template, and generate the Lean Kanban.

[0018] Further preferably, the monitoring of the subtask processing process of the handler through the Lean Kanban includes:

[0019] After monitoring through the Lean Kanban that the subtask of the handler is completed, copy the code of the subtask and submit the code through git.

[0020] Further preferably, after monitoring through the Lean Kanban that the subtask of the handler is completed, copying the code of the subtask and submitting the code through git, it further includes:

[0021] After detecting that all subtasks of the user story are completed, initiate a joint debugging requirement, and control the user story to perform automated testing according to the joint debugging requirement.

[0022] Preferably, after detecting that all subtasks of the user story are completed, initiating a joint debugging requirement, and controlling the user story to perform automated testing according to the joint debugging requirement, it includes:

[0023] Obtain the automated test result. If there are defects in the automated test result, generate a defective user story.

[0024] Further, after monitoring the subtask processing process of the handler through the Lean Kanban, detecting that the subtask is completed and the product is defect-free, initiating the product launch and completing the product launch, it further includes:

[0025] When detecting the flow chart output instruction of the Lean Kanban, output the cumulative flow chart of the Lean Kanban including the average delivery cycle and the number of work in progress.

[0026] Further, when monitoring the sub-task processing process of the handler through the lean kanban and detecting that the sub-task is completed and the product is defect-free, the product is launched. After the product is launched, it further includes:

[0027] When detecting the data export instruction of the lean kanban, the kanban information and the personnel workload analysis data are exported in the form of a table.

[0028] Another embodiment of the present invention provides a product R & D device based on a lean kanban, including:

[0029] A lean kanban generation module for generating a lean kanban in advance according to product data;

[0030] A requirement association module for obtaining product development requirements and associating the product development requirements with the lean kanban;

[0031] A task splitting module for splitting user stories according to product development requirements in the lean kanban, splitting the user stories into sub-tasks, and assigning the split sub-tasks to the corresponding handlers;

[0032] A product process monitoring module for monitoring the sub-task processing process of the handler through the lean kanban. When detecting that the sub-task is completed and the product is defect-free, the product is launched and the product launch is completed.

[0033] Another embodiment of the present invention provides an electronic device, which is characterized by including a processor and a memory;

[0034] The memory is used for storing operation instructions;

[0035] The processor is used for executing the product R & D method based on the lean kanban described in any one of the above by calling the operation instructions.

[0036] Another embodiment of the present invention further provides a non-volatile computer-readable storage medium. The non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, it implements the product R & D method based on the lean kanban described in any one of the above.

[0037] Beneficial effects: The lean kanban of the embodiment of the present invention provides a visual process, visual work items, visual personnel division of labor, visual work item hierarchy, and visual work item association / dependency, supporting project managers to manage the development progress of the team, being able to control the development quality, and forming a feedback closed loop. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] The present invention will be further described below in conjunction with the drawings and embodiments. In the drawings:

[0039] Figure 1Flow chart of a preferred embodiment of a product R & D method based on lean kanban according to the present invention;

[0040] Figure 2 Schematic structural diagram of a preferred embodiment of a product R & D device based on lean kanban according to the present invention;

[0041] Figure 3 Schematic structural diagram of a preferred embodiment of an electronic device according to the present invention. Detailed implementation manners

[0042] To make the objectives, technical solutions and effects of the present invention clearer and more definite, the present invention will be further described in detail below. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention. The embodiments of the present invention will be introduced below with reference to the accompanying drawings.

[0043] An embodiment of the present invention provides a product R & D method based on lean kanban. Please refer to Figure 1 , Figure 1 which is a flow chart of a preferred embodiment of a product R & D method based on lean kanban according to the present invention. As Figure 1 shown, it includes the steps:

[0044] Step S100, generating a lean kanban in advance according to product data;

[0045] Step S200, obtaining product development requirements and associating the product development requirements with the lean kanban;

[0046] Step S300, splitting user stories according to product development requirements in the lean kanban, splitting the user stories into subtasks, and assigning the split subtasks to corresponding processors;

[0047] Step S400, monitoring the subtask processing process of the processor through the lean kanban. When it is detected that the subtask processing is completed and the product has no defects, initiate product launch to complete product launch.

[0048] Specifically in implementation, the embodiment of the present invention proposes a method for R & D management with visual processes, visual work items, visual personnel division of labor, visual work item levels, and visual work item associations / dependencies, and proposes a controllable and transferable technical solution in combination with devops-related tools.

[0049] The main users of using lean kanban for R & D management are developers, product owners, and lean coaches. Different design styles of lean kanban do not affect the system usage. A lean coach is a processor familiar with the product process and the use of the kanban, and the lean coach may be the product owner.

[0050] The lean coach or product owner associates the system tasks in requirements management with the kanban. When the feature requirements appear in the requirements pool in the lean kanban or internal requirements are created from the kanban, the internal requirements appear in the ready column.

[0051] The lean coach or product owner splits the requirements into user stories and assigns responsible persons, where the relationship between requirements and user stories is one-to-many.

[0052] The person in charge of the user story splits sub-tasks and assigns responsible persons, and the tasks flow in the work column. The relationship between the user story and the tasks is one-to-many.

[0053] The present invention can support the combination of lean thinking and software R & D management, and the lean kanban is linked with devops tools at the same time. The task card is linked with the GIT code submission push action, and the task is associated with the code submission. The requirement card is linked with the pipeline, and when the requirement task is completed, it triggers the build + deployment pipeline to build the code and deploy it to the test environment. The defect card is linked with the automated testing tool, and a defect card is automatically generated on the kanban. After the card is dragged to the completed column, a completion message is sent to the automated testing tool.

[0054] Based on the lean kanban in the present invention, first, it provides a visual process, visual work items, visual personnel division of labor, visual work item hierarchy, visual work item association / dependency, and has explicit drag-and-drop rules, supporting project managers to manage the team development progress, control the development quality, and form a feedback loop. Developers can actively drag cards to achieve the forward flow of work items.

[0055] Furthermore, the lean kanban is generated in advance according to product data, including:

[0056] Obtain the product line data in advance and configure the status columns according to the product line data;

[0057] Configure the swimlanes according to the product type;

[0058] Assemble the status columns and the swimlanes into a lean kanban template;

[0059] Obtain the personnel of the execution team of the lean kanban and write the execution team personnel into the lean kanban template to generate the lean kanban.

[0060] In specific implementation, the lean coach configures the status columns in the system according to the product line, where the status columns include work columns and attention columns. The lean coach configures the swimlanes in the system according to the product category. The lean coach assembles the configured status columns and the swimlanes into a lean kanban template. The lean coach selects team members and the lean kanban template to form a lean kanban, which is only visible to team members.

[0061] Furthermore, monitor the subtask processing process of the processor through the Lean Kanban, including:

[0062] After monitoring through the Lean Kanban that the subtask of the processor is completed, copy the encoding of the subtask and submit the code through git.

[0063] In specific implementation, the developer drags the subtask for which they are responsible. After completion, copy the commit number of the task and submit the code through git.

[0064] Furthermore, after monitoring through the Lean Kanban that the subtask of the processor is completed, copying the encoding of the subtask and submitting the code through git, it also includes:

[0065] After detecting that all subtasks of the user story are completed, initiate the joint debugging requirement, and control the user story to perform automated testing according to the joint debugging requirement.

[0066] In specific implementation, after all tasks under the user story are completed, the Lean coach drags the user story to the completed column, and the tasks are automatically archived. The Lean coach can drag the requirement card to the subsequent status column to trigger the pipeline to execute build + deployment for automated testing.

[0067] Furthermore, after detecting that all subtasks of the user story are completed, initiating the joint debugging requirement, and controlling the user story to perform automated testing according to the joint debugging requirement, it includes:

[0068] Obtain the automated test results. If there are defects in the automated test results, generate a defective user story.

[0069] In specific implementation, the defects of the automated test tool are automatically associated with the Kanban to form a defective user story. The developer then conducts corresponding subtask development based on the defective story until the product has no defects.

[0070] Furthermore, when monitoring the subtask processing process of the processor through the Lean Kanban and detecting that the subtask processing is completed and the product has no defects, initiate the product go - live. After completing the product go - live, it also includes:

[0071] Detect the flow chart output instruction of the Lean Kanban, and output the cumulative flow chart of the Lean Kanban containing the average lead time and the number of work - in - process items.

[0072] In specific implementation, the cumulative flow diagram shows the change in the number of work-in-progress items in the most recent two weeks, and the lean coach can identify bottlenecks through the cumulative flow diagram. The embodiments of the present invention also provide a cumulative flow diagram of the lean kanban. The horizontal distance between the two lines represents the Lead time (the average time from Analysis to Done, the average delivery cycle), and the vertical distance represents the WIP (the number of work-in-progress items, the number of cards between all Analysis and Done). It can identify processes, identify work-in-progress items, identify bottlenecks, view the production process from the perspective of the entire life cycle of the product, and use the cumulative flow diagram to more quickly and accurately locate the links where problems may occur, and can also better anticipate subsequent project risks.

[0073] Further, by monitoring the subtask processing process of the processor through the lean kanban, when it is detected that the subtask is processed and the product is defect-free, the product is launched. After the product is launched, it further includes:

[0074] When a data export instruction of the lean kanban is detected, the kanban information and the personnel workload analysis data are exported in the form of a table.

[0075] In specific implementation, the exported kanban data includes kanban information such as task processing duration, defect processing duration, and obstacle processing duration, and personnel workload analysis: personnel working hours and user story situations.

[0076] Further, the lean kanban of the present invention is linked to the requirements analysis level, which is an integral part of the end-to-end delivery of requirements. It can be used with an additional electronic screen during regular meetings to manage the development progress of the team and can control the development quality. The electronic lean kanban and the physical kanban can be converted. The user stories and tasks on the excel can be imported into the kanban, and at the same time, all the cards on the kanban can be exported, printed, and pasted onto the physical kanban.

[0077] The present invention also provides a specific embodiment of a product R & D method based on the lean kanban, as follows:

[0078] The system task responsible person receives a requirement and manages the process of the requirement from analysis, development, testing to launch.

[0079] The system task responsible person associates the requirement with the lean kanban in use

[0080] The product responsible person or the system task responsible person splits the requirement into different user stories

[0081] The lean coach splits the user story into multiple different types of tasks, such as analysis, detailed design, and development

[0082] The developer receives the task, and after completion, drags the task to the completed sub-column and submits the code through the responsible commit code

[0083] After all the tasks under the user story are completed, the lean coach drags the user story to the completed column, and the tasks are automatically archived.

[0084] The lean coach can drag the requirement card to the subsequent system test column, trigger the pipeline to execute build + deployment, and the defects of the automated test tool are automatically associated with the kanban to form defect user stories.

[0085] The lean coach drags the requirement to the completed column, and the system task is automatically completed.

[0086] As can be seen from the above method embodiments, the embodiments of the present invention provide a product R & D method based on lean kanban. By combining lean thinking with software R & D management, it solves the problem that the current agile kanban is not suitable for the lean R & D mode. At the same time, the current kanban cannot view the production process of the product throughout the life cycle. And it can realize the configurable function of the kanban, configure different columns and swimlanes, cooperate with project teams with different R & D requirements for R & D management, can realize the archiving and query of task cards, manage the development progress of the team at any time, view the periodic progress, and can identify risks, export kanban data for analysis. And it can link the card with the devops pipeline. While dragging the card, it realizes the association of code and tasks, version building, version deployment, initiating testing, and defect association, so as to achieve the purpose of liberating developers.

[0087] It should be noted that there is not necessarily a certain sequence among the above steps. Those of ordinary skill in the art can understand according to the description of the embodiments of the present invention that in different embodiments, the above steps can have different execution sequences, that is, they can be executed in parallel, or can be exchanged, etc.

[0088] Another embodiment of the present invention provides a product R & D device based on lean kanban, as Figure 2 shown, the device 1 includes:

[0089] A lean kanban generation module 11, configured to generate a lean kanban in advance according to product data;

[0090] A requirement association module 12, configured to obtain product development requirements and associate the product development requirements with the lean kanban;

[0091] A task splitting module 13, configured to split user stories according to product development requirements in the lean kanban, split the user stories into subtasks, and assign the split subtasks to corresponding processors;

[0092] A product process monitoring module 14, configured to monitor the processing process of the subtasks of the processor through the lean kanban. When it is detected that the subtasks are processed and the product has no defects, initiate product go-live and complete product go-live.

[0093] For the specific implementation manners, refer to the method embodiments described above, which will not be elaborated herein.

[0094] Optionally, the lean kanban generation module 11 is further configured to pre-obtain product line data and configure status columns according to the product line data;

[0095] Configure swimlanes according to product types;

[0096] Assemble the status columns and swimlanes into a lean kanban template;

[0097] Obtain the personnel of the execution team for the lean kanban, write the personnel of the execution team into the lean kanban template, and generate a lean kanban.

[0098] Optionally, after the product process monitoring module 14 monitors that the subtask of the processor is completed through the lean kanban, it copies the code of the subtask and submits the code through git.

[0099] Optionally, after the product process monitoring module 14 detects that all subtasks of the user story are completed, it initiates a joint debugging requirement and controls the user story to perform automated testing according to the joint debugging requirement.

[0100] Optionally, the product process monitoring module 14 is further configured to obtain the automated test results. If there are defects in the automated test results, it generates a defective user story.

[0101] Optionally, after the product process monitoring module 14 detects the flow chart output instruction of the lean kanban, it outputs a lean kanban cumulative flow chart including the average delivery cycle and the number of work in progress.

[0102] Optionally, after the product process monitoring module 14 detects the data export instruction of the lean kanban, it exports the kanban information and the personnel workload analysis data in tabular form.

[0103] Another embodiment of the present invention provides an electronic device 10, as Figure 3 shown, including a processor 110 and a memory 120;

[0104] The memory 120 is used to store operation instructions;

[0105] The processor 110 is configured to execute the product R & D method based on the lean kanban described in any one of the above by calling the operation instructions.

[0106] The processor 110 is used to complete various control logics of the electronic device 10, and it can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a single-chip microcomputer, an ARM (Acorn RISCMachine), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination of these components. Moreover, the processor 110 can also be any conventional processor, microprocessor, or state machine. The processor 110 can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration.

[0107] The memory 120, as a non-volatile computer-readable storage medium, can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules, such as the program instructions corresponding to the lean kanban-based product R & D method in the embodiments of the present invention. The processor 110 executes various functional applications and data processing of the electronic device 10 by running the non-volatile software programs, instructions, and units stored in the memory 120, that is, implements the lean kanban-based product R & D method in the above method embodiments.

[0108] The memory 120 can include a program storage area and a data storage area. Among them, the program storage area can store an operating device and application programs required for at least one function; the data storage area can store data created according to the use of the electronic device 10, etc. In addition, the memory 120 can include a high-speed random access memory, and can also include non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices. In some embodiments, the memory 120 optionally includes a memory remotely set relative to the processor 110, and these remote memories can be connected to the electronic device 10 through a network. Examples of the above networks include, but are not limited to, the Internet, an enterprise intranet, a local area network, a mobile communication network, and combinations thereof.

[0109] One or more units are stored in the memory 120, and when executed by the processor 110, they execute the lean kanban-based product R & D method in any of the above method embodiments. For example, they execute the Figure 1 method steps S100 to step S400 described above.

[0110] The embodiments of the present invention provide a non-volatile computer-readable storage medium. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, it implements the lean kanban-based product R & D method described in any one of the above, for example, executes the Figure 1 method steps S100 to step S400 described above.

[0111] By way of example, non-volatile storage media can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) as external cache memory. By way of illustration and not limitation, RAM can be in many forms such as synchronous RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM (DRRAM). The disclosed memory components or memories of the operating environments described herein are intended to include one or more of these and / or any other suitable type of memory.

[0112] The embodiments described above are merely illustrative, where the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, i.e., they may be located in one place or distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0113] Through the description of the above embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus a general hardware platform, and of course, it can also be implemented by hardware. Based on such an understanding, the essence of the above technical solution, or the part that contributes to the related technology, can be embodied in the form of a software product. This computer software product can exist in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods of each embodiment or some parts of the embodiments.

[0114] Among other things, conditional language such as "can", "be able to", "may", or "could", unless specifically stated otherwise or otherwise understood within the context in which it is used, generally is intended to convey that a particular embodiment can include (while other embodiments do not include) a particular feature, element, and / or operation. Thus, such conditional language generally is also intended to imply that the feature, element, and / or operation is in some way required for one or more embodiments or that one or more embodiments must include logic for determining whether such feature, element, and / or operation is included or will be performed in any particular embodiment, with or without input or prompting.

[0115] What has been described herein in this specification and the drawings includes examples of a product development method and apparatus capable of providing a lean kanban-based approach. Of course, it is not possible to describe every conceivable combination of components and / or methods for the purpose of describing the various features of the present disclosure, but it will be recognized that many additional combinations and permutations of the disclosed features are possible. Thus, it is evident that various modifications can be made to the present disclosure without departing from the scope or spirit thereof. Additionally, or in the alternative, other embodiments of the present disclosure may be apparent from consideration of the specification and drawings and from practice of the present disclosure as presented herein. It is intended that the examples presented in this specification and the drawings be considered illustrative in all respects and not restrictive. Although specific terms are employed herein, they are used in a generic and descriptive sense and not for purposes of limitation.

Claims

1. A product R & D method based on lean kanban, characterized in that , including: Generating a lean kanban in advance according to product data; Obtaining product development requirements and associating the product development requirements with the lean kanban; In the lean kanban, splitting user stories according to product development requirements, splitting the user stories into subtasks, and assigning the split subtasks to the corresponding processors; Monitoring the processing process of the subtasks of the processors through the lean kanban. When it is detected that the subtasks of the processors are completed and the product is defect-free, initiating product launch and completing product launch; The generating a lean kanban in advance according to product data includes: Obtaining product line data in advance and configuring status columns according to the product line data; Configuring swimlanes according to product types; Assembling the status columns and the swimlanes into a lean kanban template; Obtaining the execution team members of the lean kanban and writing the execution team members into the lean kanban template to generate a lean kanban; The monitoring the processing process of the subtasks of the processors through the lean kanban includes: After monitoring that the subtasks of the processors are completed through the lean kanban, copying the codes of the subtasks and committing the codes through git; After monitoring that the subtasks of the processors are completed through the lean kanban, copying the codes of the subtasks and committing the codes through git, further including: When it is detected that all the subtasks of the user story are completed, initiating joint debugging requirements and controlling the user story to perform automated testing according to the joint debugging requirements.

2. The method according to claim 1, characterized in that after detecting that all the subtasks of the user story are completed, initiating joint debugging requirements and controlling the user story to perform automated testing, including: Obtaining the automated test results. If there are defects in the automated test results, generating defective user stories.

3. The method according to claim 2, characterized in that after monitoring the processing process of the subtasks of the processors through the lean kanban, detecting that the subtasks are completed and the product is defect-free, initiating product launch and completing product launch, further including: Detecting the flow chart output instruction of the lean kanban and outputting a lean kanban cumulative flow chart including the average delivery cycle and the number of work-in-process products.

4. The method according to claim 3, characterized in that after monitoring the processing process of the subtasks of the processors through the lean kanban, detecting that the subtasks are completed and the product is defect-free, initiating product launch and completing product launch, further including: Detecting the data export instruction of the lean kanban and exporting the kanban information and the personnel workload analysis data in tabular form.

5. A product R & D device based on lean kanban, characterized in that including: A lean kanban generation module for generating a lean kanban in advance according to product data, including: obtaining product line data in advance, configuring status columns according to the product line data; configuring swimlanes according to product types; assembling the status columns and the swimlanes into a lean kanban template; obtaining the execution team members of the lean kanban and writing the execution team members into the lean kanban template to generate a lean kanban; A requirement association module for obtaining product development requirements and associating the product development requirements with the lean kanban; The task splitting module is used to split user stories according to product development requirements in the lean kanban, split the user stories into subtasks, and assign the split subtasks to the corresponding handlers; The product process monitoring module is used to monitor the subtask processing process of the handler through the lean kanban. When it is detected that the subtask processing is completed and the product is defect-free, it initiates the product go-live and completes the product go-live; it is also used to copy the code of the subtask and submit the code through git after monitoring that the subtask of the handler is completed in the lean kanban, and when it is detected that all subtasks of the user story are completed, it initiates the joint debugging requirement and controls the user story to perform automated testing according to the joint debugging requirement.

6. An electronic device, Characterized in that, It includes a processor and a memory; The memory is used to store operation instructions; The processor is used to execute the method according to any one of claims 1-4 by calling the operation instructions.

7. A non-volatile computer-readable storage medium, Characterized in that, The non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, it implements the method according to any one of claims 1-4.

Images