TWI732380B - Agile project management method and server - Google Patents

Abstract

The invention provides an agile project management method and a server. The method includes: obtaining a project management milestone; determining whether the task stories belonging to the project management milestone have been completed; in response to determining that the task stories of the project management milestone have been completed, obtaining a specific code node of each task story from each project commit tree; establishing a code artifact corresponding to the project management milestone based on the specific code node of each task story on each project commit tree.

Description

Agile project management method and server

The present invention relates to a project management method and server, and particularly relates to an agile project management method and server.

Driven by the DevOps culture and the upsurge of microservice program architecture, cross-departmental collaboration is more closely integrated than ever before, and related version control systems and code reviews also play an important role in improving software quality. However, under the architecture of microservices, there may be dependencies among various services. Therefore, regardless of whether Git Flow, GitHub Flow or Gitlab Flow is used, its project milestone (Milestone) has a certain degree to the project owner (Project Owner) the complexity.

In the past, in order to improve the quality of research and development, R&D personnel would be more cautious in executing the code that was delivered and merged. The principle followed Git Flow or GitHub Flow, which used branch lines to cut different story tasks to ensure that the code was independent of each other in different story tasks. It can be independently verified to ensure the quality of the final delivery, so the combined process is usually in the later stages of development. However, if the merged process involves a wide range of services, or there are inter-service interfaces, it may increase the time for quality convergence and even lead to delayed product delivery.

In addition, for some small teams or teams that use pair programming, there is actually no need to deal with the problem of later code conflicts, but because of the submission principles and interdependence issues, they will also face the challenges of the merge process in the later stages of development. .

Therefore, in the early stages of development, early recognition of the interdependence of related interfaces, completion of code merge (Code Merge) and early confirmation of conflicts (especially under the microservice architecture) will ensure the interconnection of each other's services and help The overall project management efficiency.

In view of this, the present invention provides an agile project management method and server, which can be used to solve the above technical problems.

The present invention provides an agile project management method suitable for an agile project management server, including: obtaining a project management milestone, wherein the project management milestone includes multiple story tasks, and each story task has a story task code and includes distributed At least one project submission tree has multiple code nodes. Each code node of each story task is assigned a submission serial number and corresponding story task code when it is submitted to a code repository; the aforementioned items are judged to belong to the project management milestone Whether all the task stories have been completed; the aforementioned task stories that reflect the project management milestones have been completed. Obtain each story task individually from at least one project submission tree. A specific code node on each project submission tree, including each story task The specific code node in each project submission tree has a latest submission sequence number belonging to the story task in at least one project submission tree to which it belongs; the specific code node corresponding to the project is created based on each story task in each project submission tree A code artifact that manages milestones.

The invention provides an agile project management server, which includes a version control management component and a submission management record engine. The version control management component is configured to: obtain a project management milestone, where the project management milestone includes multiple story tasks, each story task has a story task code and includes multiple code nodes distributed on at least one project submission tree, each Each code node of the story task is assigned a submission sequence number and a corresponding story task code when it is submitted to a code repository; it is determined whether the aforementioned task stories belonging to the project management milestones have been completed. The submission management record engine is configured to: the aforementioned task stories reflecting the project management milestones determined by the version control management component have been completed, and each story task is individually obtained from at least one project submission tree for a specific code node on each project submission tree , The specific code node of each story task in each project submission tree has a latest submission sequence number belonging to the story task in at least one project submission tree to which it belongs; based on the specific code of each story task in each project submission tree The node creates a code artifact corresponding to the project management milestone.

In order to make the above-mentioned features and advantages of the present invention more comprehensible, the following specific embodiments are described in detail in conjunction with the accompanying drawings.

In summary, the present invention provides a mechanism for implementing intelligent version control (version control for short) under a microservice architecture, which can be used to enable developers to resolve code conflicts early. When there are dependencies between services, the present invention can intelligently select appropriate submission results for packaging, and automatically align the progress of each microservice project from the perspective of overall service project management, regardless of whether there is a dependency, and solve the code earlier Conflict, to ensure compliance with demand specifications and rapid convergence of product quality. This will be further explained below.

Please refer to FIG. 1, which is a schematic diagram of an agile project management server according to an embodiment of the present invention. In this embodiment, the agile project management server 100 can provide overall service project management under agile software and microservice architecture, assist project managers to automatically align the progress of each microservice project, and allow developers to resolve code conflicts early .

As shown in FIG. 1, the agile project management server 100 may include a user interface 101, a project management component 102, a version control management component 103 and a submission record management engine 104. The user interface 101 can be used to provide a graphical interface and an application programming interface (API) to system users. The project management component 102 can be used to perform project task creation management, user story definition, story task planning, project management milestone management, and submission serial numbers (Commit ID) of code nodes related to each story task. The version control management component 103 can be used to manage the source code and review the collaboratively developed code to ensure that the quality of the project source code meets the specifications.

In the embodiment of the present invention, the version control management component 103 is, for example, a Gitlab component based on Git, but it may not be limited thereto. In other embodiments, the version control management component 103 can also be implemented as other distributed version control components.

In the embodiment of the present invention, after the developer completes the required code development, the code can be submitted (commit) to the code repository in the form of a code node. In one embodiment, the code repository may include project commit trees corresponding to different projects (for example, microservice projects), and each project submission tree may include one corresponding to one or more story tasks. Or multiple code nodes.

In one embodiment, before the developer merges the code and submits the code to the code repository, the changed part of the code needs to be resolved. When Git cannot determine the changed part, it means that a code conflict occurs, and the developer needs to resolve the conflict. If the code conflict occurs closer to the later stage of development, the complexity of the related resolution is higher. Therefore, the present invention can assist the early resolution of code conflicts through the submission record management engine 104 of the proposed agile project management server 100, and the relevant details will be detailed later.

In one embodiment, in order to provide the relevant intelligent management capabilities of the agile project management server 100, the researcher needs to implement the method of associating the code to the agile project management server 100 as shown in FIG. 2.

Roughly speaking, the method in FIG. 2 is related to the project management component 102 and the version control management component 103 in the agile project management server 100, and the individual related steps are shown in dashed lines in FIG. 2, but the present invention is possible The embodiment is not limited to this.

First, in step S210, the researcher can select the story task assigned by the project manager in the project management component 102, and start to implement the code related to the story task in step S220. In the embodiment of the present invention, each story task may be assigned a corresponding story task code.

After completing the code development of the story task, developers can try to submit their research and development results to the code repository. At this time, the R&D personnel can first perform step S230 to perform code review through the version control management component 103. For example, the R&D team can use paired programming to ensure that the code meets the task of the story and the required quality. After that, the developer can perform step S240 to merge the changed code. If a code conflict occurs at this time (step S250), the developer must first eliminate various code conflicts in step S260. After completing the merging of the code, the developer can submit the code to the code repository. In this process, code reviewers and developers do not need to consider the progress of other dependent projects. Submitting the record management engine 104 can automatically align the progress of each microservice project in the subsequent stages, thus speeding up the code review process and Resolve code conflicts early.

When the developer submits the code developed for a certain story task as a code node to the corresponding project submission tree, the code node needs to be bound to the story task code to which it belongs (step S270). After that, the version control management component 103 can generate a corresponding submission sequence number for the code node (step S280) and record it through the project management component 102, and then associate the submission sequence number with the story task code (step S290). In this way, each project submission tree can include code nodes belonging to the same or different story tasks, and each code node will be bound to the story task code to which it belongs, and can be assigned a unique submission sequence number. However, the present invention It is not limited to this.

After that, when the project manager and version control personnel prepare to finalize the version, the agile project management server 100 of the present invention can execute the proposed agile project management method to achieve the purpose of smart version control, which is described in detail as follows.

Please refer to FIG. 3, which is an agile project management method according to an embodiment of the present invention, which can be executed by the agile project management server 100 of FIG. 1. The following is a description of each step of FIG. 3 with the content of FIG. 1. detail.

First, in step S310, the version control management component 103 can obtain project management milestones. In one embodiment, the project management milestone is, for example, the project management milestone selected by the project manager and/or the version controller from the user interface 101 to be finalized, and it may include multiple story tasks. As mentioned in the previous embodiment, each story task may have a story task code, and may include multiple code nodes distributed on one or more project submission trees (which respectively correspond to one project). In addition, when each code node of each story task is submitted to the code repository by the developer, the version control management component 103 can assign a submission sequence number to each code node and bind the story task code to which it belongs.

After that, in step S320, the version control management component 103 can determine whether all the task stories belonging to the above project management milestones have been completed. In one embodiment, step S320 can be understood as determining whether the developer has submitted the code that needs to be developed for each task story to the project submission tree of the code repository, but the present invention is not limited to this.

If the task stories belonging to the above project management milestones have not been completed, it means that the project management milestones may not be suitable for finalization because the required functions have not yet been developed. In this case, the version control management component 103 can adjust or abandon the project milestone according to the selection of the project manager and/or the version control personnel (step S350). For example, if the project manager chooses to temporarily exclude unfinished story tasks, the version control management component 103 may continue to perform subsequent operations based on the completed story tasks. For another example, if the project manager thinks that all story tasks need to be completed before finalizing the version, he can choose to temporarily abandon the project milestone on the user interface 101 (for example, postpone the schedule of finalization). In this case, the version control management component 103 can accordingly abandon the project milestone to interrupt the relevant version setting operation, but the present invention is not limited to this.

On the other hand, if the version control management component 103 determines that all the task stories of the above project management milestones have been completed, it means that the above project management milestones are suitable to be used to finalize the version. In this case, the submission record management engine 104 may perform step S330 to individually obtain the specific code node of each story task in each project submission tree from the aforementioned project submission tree, where each story task is specific to each project submission tree. The code node has the latest submission sequence number belonging to the story task in the project submission tree to which it belongs.

In order to facilitate the understanding of the above concepts, an example is supplemented below for description. In one embodiment, it is assumed that the story task of the project management milestone includes a first story task, and it includes a plurality of first code nodes distributed on one or more of the project submission tree. According to the teaching of the previous embodiment, each first code node is assigned the story task code of the first story task and a different submission sequence number through the version control management component 103 when it is submitted.

Assuming that the above project submission tree includes a first project submission tree corresponding to a first (microservice) project, the submission record management engine 104 can find the specific code node corresponding to the first story task in the first project submission tree . Specifically, the submission record management engine 104 can find the first code node belonging to the first story task and its individual submission sequence number on the first project submission tree. After that, the submission record management engine 104 can find the one with the latest submission sequence number among the first code nodes belonging to the first story task on the first project submission tree as the first story task on the first project submission tree The specific code node.

In addition, assuming that the above-mentioned project submission tree further includes a second project submission tree corresponding to a second (microservice) project, the submission record management engine 104 can find the task corresponding to the first story task in the second project submission tree. Specific code node. Specifically, the submission record management engine 104 can find the first code node belonging to the first story task and its individual submission sequence number in the second project submission tree. After that, the submission record management engine 104 can find the first code node belonging to the first story task in the second project submission tree and find the one with the latest submission sequence number as the first story task on the second project submission tree The specific code node.

In short, for any project submission tree that has a code node belonging to a certain story task, the submission record management engine 104 can find the specific code node corresponding to the aforementioned story task in the project submission tree.

It can be seen from the above that for each story task, the submission record management engine 104 can find a specific code node corresponding to each story task in each project submission tree.

After that, in step S340, the submission record management engine 104 may create a code artifact corresponding to the project management milestone based on the specific code node of each story task in each project submission tree. In one embodiment, the submission record management engine 104 can obtain the code corresponding to the specific code node of each story task, and compile it into a code artifact corresponding to the aforementioned project management milestone. For the details of this step, please refer to technical documents related to compilation in the prior art, and will not be repeated here.

It can be seen from the above that through the submission record management engine 104, developers can directly merge and submit the code when completing the code development of the story task, without having to consider the progress of the overall project. If code conflicts occur, they can be resolved early in the early stages of development. Under the structure of microservices, a single service may be developed by only a few people (or even a team that performs pairing programming), so the code review may have already been completed.

With the method proposed by the present invention, developers can submit code immediately without worrying about the overall project progress and its dependencies. In this way, the present invention can automatically align the progress of each microservice project, thereby helping to speed up the code review process of developers and resolve code conflicts early. Moreover, under the microservice architecture, the present invention can reduce the complexity of integrating various projects by project managers and developers, thereby ensuring compliance with demand specifications and rapid convergence of product quality.

In summary, the present invention provides an agile project management method and server, which help developers to resolve code conflicts early. Moreover, when there are dependencies between services, the present invention can intelligently select appropriate delivery results (that is, specific code nodes of each task story in each project submission tree) and package them. From the perspective of overall service project management, the present invention can automatically align the progress of each microservice project, perform subsequent integration tests and verifications, and ensure compliance with demand specifications and rapid convergence of product quality.

Although the present invention has been disclosed in the above embodiments, it is not intended to limit the present invention. Anyone with ordinary knowledge in the relevant technical field can make some changes and modifications without departing from the spirit and scope of the present invention. The protection scope of the present invention shall be subject to those defined by the attached patent application scope.

100: Agile project management server 101: User Interface 102: Project management component 103: Version control management components 104: Submit the record management engine S210~S290, S310~S350: steps

FIG. 1 is a schematic diagram of an agile project management server according to an embodiment of the present invention. FIG. 2 is a method for associating code to an agile project management server according to an embodiment of the present invention. Fig. 3 is an agile project management method according to an embodiment of the present invention.

S310~S350: Steps

Claims (8)

An agile project management method suitable for an agile project management server, including: obtaining a project management milestone, where the project management milestone includes multiple story tasks, and each story task has a story task code and includes multiple Multiple code nodes on a project submission tree, each code node of each story task is assigned a submission serial number and corresponding story task code when it is submitted to a code repository; it is judged to belong to the project management Whether the mission stories of the milestone are all completed; the mission stories that reflect the determination of the project management milestones are all completed, obtain a specific task of each story task in each project submission tree from the project submission tree individually Code node, where the specific code node of each story task in each project submission tree has a latest submission sequence number belonging to the story task in the project submission tree to which the story task belongs, and the story tasks include a first A story task, and the first story task includes a plurality of first code nodes distributed on the project submission trees, and each of the first code nodes is assigned the story task code of the first story task And different submission serial numbers, where the project submission trees include a first project submission tree, and from the project submission trees, the steps of each story task at the specific code node on each project submission tree are individually obtained Including: finding the first code nodes belonging to the first story task and their individual submission sequence numbers on the first project submission tree; among the first code nodes belonging to the first story task Find the right The specific code node corresponding to the first story task, where the specific code node corresponding to the first story task has the latest in the first project submission tree compared to the other first code nodes The submission sequence number of the; based on each story task, create a code artifact corresponding to the project management milestone in the specific code node on each project submission tree. For the method described in item 1 of the scope of patent application, each of the project submission trees corresponds to a microservice project. For example, the method described in item 1 of the scope of patent application, wherein the task stories reflecting the determination of the project management milestones are not completed, the method further includes: abandoning the project management milestones, or adjusting the project management milestones At least one of these story missions. For example, in the method described in item 1 of the scope of patent application, the step of creating the code artifact corresponding to the project management milestone on the specific code node on each project submission tree based on each of the story tasks includes: obtaining each The story task is a code corresponding to the specific code node on the project submission tree, and is compiled accordingly into the code manufacture corresponding to the project management milestone. An agile project management server, including: a version control management component, which is configured to: obtain a project management milestone, wherein the project management milestone includes a plurality of story tasks, each of the story tasks has a story task code and includes distribution Multiple code nodes on the tree for multiple project submissions, each code for each story task When a node is submitted to a code repository, it is assigned a submission sequence number and the corresponding story task code; it is determined whether the task stories belonging to the project management milestone are all completed; a submission management record engine is configured to : The task stories that reflect the project management milestones determined by the version control management component have been completed. Obtain the specific code nodes of each story task in each project submission tree from the project submission trees. The specific code node of each story task in each project submission tree has a latest submission sequence number belonging to the story task in the project submission tree to which it belongs, wherein the story tasks include a first story task, and The first story task includes a plurality of first code nodes distributed on the project submission trees, and each of the first code nodes is assigned the story task code of the first story task and a different submission Serial number, where the project submission trees include a first project submission tree, and the submission management record engine is configured to: find the first code nodes belonging to the first story task on the first project submission tree And its individual submission sequence number; find the specific code node corresponding to the first story task among the first code nodes belonging to the first story task, where the specific code node corresponding to the first story task The specific code node in the first project submission tree has the latest submission sequence number compared to the other first code nodes; based on the specific code in each project submission tree for each story task The node creates a code artifact corresponding to the project management milestone. For example, in the agile project management server described in item 5 of the scope of patent application, each project submission tree corresponds to a microservice project. For example, the agile project management server described in item 5 of the scope of patent application, in which all the task stories that reflect the determination of the project management milestone are not completed, the version control management component is further configured to: abandon the project management milestone, Or adjust at least one of the story tasks in the project management milestone. For example, the agile project management server described in item 5 of the scope of patent application, wherein the submission management record engine is configured to: obtain a code corresponding to the specific code node of each story task in each project submission tree , And compile it into the code artifact corresponding to the project management milestone.

Images