Demand-oriented agile product research and development process management method and system

Abstract

The invention discloses a demand-oriented agile product research and development process management method and system. The system comprises a research and development demand management module, a to-be-released version management module and a released version management module. Wherein the research and development demand management module is used for allowing a user to track and manage product demands in research and development in real time, displaying product data through a tree structure, and positioning products and demands; meanwhile, related operation options are also provided for management and adjustment; the to-be-released version management module is used for storing a to-be-released product version, and the product version is associated with a plurality of completed demands; and the released version management module is used for filing and managing released product versions. According to the method, high matching of research and development contents and market demands can be ensured, problems can be found and solved in time, the risk of version delay is reduced, the research and development process is simplified, various repeated work caused by overall planning and demand change is removed, and the communication cost is reduced.

Description

Technical Field

[0001] The present invention relates to the field of management systems, and in particular to a demand-oriented agile product development process management method and system. Background Art

[0002] In the current software development environment, rapid iteration and high-quality delivery of products have become the core of corporate competition. The traditional waterfall development model can no longer meet the market's demand for rapid response to changes. The agile development model has gradually become the mainstream with its short-cycle iteration, high collaboration and flexible adjustment. In the traditional agile product development process management, the version is usually planned first, and then the requirements are split based on the content in the version, and then development, testing and release are carried out based on the requirements. However, this method often has problems such as the mismatch between version planning and actual requirements, and frequent changes in requirements leading to version delays.

[0003] The existing R&D management process usually plans the version first, then splits the requirements based on the version content, and then conducts R&D, testing, and release in sequence. However, this method has the following problems:

[0004] 1. Demand and R&D are out of sync:

[0005] In the traditional way, version planning is often based on preliminary forecasts, while actual requirements may change during the development process, resulting in a mismatch between the development content and market demand. This disconnect may lead to a waste of resources because the developed features may not be what the market really needs.

[0006] 2. Inflexible response to demand changes:

[0007] In an agile environment, requirements change frequently and are difficult to predict. In traditional methods, R&D teams need to spend a lot of time and energy to adjust R&D plans and task allocations to adapt to changes in requirements. This inflexibility may cause delays in R&D progress and even affect the final quality of the product.

[0008] 3. The R&D process is cumbersome and inefficient:

[0009] In traditional methods, the R&D process usually includes multiple links such as version planning, demand splitting, R&D, testing, and release. There may be overlaps or conflicts between each link, and when the demand changes, it may be necessary to re-plan, split, and develop processes. This cumbersome process may increase communication costs and inefficient team collaboration;

[0010] In order to solve the above problems, a demand-oriented agile product development process management method and system is proposed. Summary of the invention

[0011] The technical problem to be solved by the present invention is: how to solve the problems of disconnection between demand and R&D, inflexible response to demand changes, and inflexible response to demand changes, and provide a demand-oriented agile product R&D process management method and system.

[0012] The present invention solves the above technical problems through the following technical solutions, which include:

[0013] The R&D demand management module, the pending version management module and the released version management module;

[0014] Among them, the R&D demand management module is used to allow users to track and manage product requirements under development in real time, display product data through a tree structure, and locate products and requirements;

[0015] At the same time, relevant operation options are also provided for management and adjustment.

[0016] To-be-released version management module: used to store product versions to be released, which are associated with multiple completed requirements.

[0017] Released version management module: used to archive and manage released product versions.

[0018] Furthermore, the to-be-released version management module is further used to view specific information of the to-be-released version, including product name, current stage, version number and associated requirements;

[0019] At the same time, the version management module to be released provides deletion, iteration plan management, test submission and version release functions.

[0020] Furthermore, the released version management module is also used to view all released version information of the product, and is also used to cancel release, version plan and test status.

[0021] A demand-oriented agile product development process management method, the method comprising the following steps:

[0022] Step 1: Enter R&D requirements in R&D demand management;

[0023] Step 2: Adjust the requirements in R&D according to the actual situation;

[0024] Step 3: Continue to track the development of demand, maintain the development demand, and return to step 2 to rewrite and adjust the demand when there is a change in demand during the tracking process;

[0025] Step 4: Integrate and submit multiple R&D requirements, generate iterative version information, and push the iterative version information to the version management to be released for version advancement;

[0026] Step 5: Maintain the product development version information in the version management to be released, adjust the iteration version, R&D person in charge, start time, end time, iteration goal, related requirements, related design review meeting, iteration archive information, etc.

[0027] Step 6: Develop and execute a plan for the development version;

[0028] Step 7: Push the R&D version to the testing team for testing to ensure that the product meets quality requirements;

[0029] Step 8: Continuously monitor the development progress, adjust the version plan completion status according to the actual situation of the monitoring development progress, and maintain the version development progress;

[0030] Step 9: During the development version advancement process, repeat steps 5, 6, 7, and 8 until the development version is completed. After confirming that the version meets the release adjustment, the version is released and pushed to the released version management;

[0031] Step 10, check the status of the R&D version in the released version management, and confirm whether to archive the version based on the status of the R&D version. If there is a problem, cancel the release and return to the pending version management to perform steps 5 to 9. If no adjustment is required, the version can be archived and the R&D process management is completed.

[0032] Furthermore, the content of the R&D requirements entered in step 1 includes the requirement name, description, product, module, requirement label, requirement type, requirement value, impact analysis, degree of realization, workload, planned completion time, requirement source, provider and requirement category.

[0033] Furthermore, the content of maintaining the R&D requirements in step 3 includes: start time, design completion time, coding completion time, planned completion time, R&D personnel, workload estimate, overall progress and confirmation information.

[0034] Furthermore, the iteration version information includes the iteration version, the R&D person in charge, the actual start time, the end time and the iteration target.

[0035] Furthermore, the content of the plan for formulating and executing the R&D version includes the person in charge of each plan, workload, start time, end time and completion progress;

[0036] The R&D version status in the released version management includes the overall plan and testing status of the version.

[0037] Compared with the prior art, the present invention has the following advantages: the demand-oriented agile product development process management method and system, the demand-oriented development process, starts from the entry of demand, runs through the entire development process, and finally releases the product. This process ensures that the development content is highly matched with market demand.

[0038] Agile R&D management allows for flexible adjustment, tracking and change of requirements. This management approach enables the R&D team to respond quickly to market changes and ensure product competitiveness.

[0039] The integration of R&D demand management, pending version management, and released version management forms a complete R&D process management system. The system can achieve comprehensive monitoring and management of R&D activities, ensure the transparency and efficiency of the R&D process, and make the system more worthy of promotion and use. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] Figure 1 It is the overall flow chart of the present invention. DETAILED DESCRIPTION

[0041] The following is a detailed description of an embodiment of the present invention. This embodiment is implemented on the premise of the technical solution of the present invention, and a detailed implementation method and a specific operation process are given, but the protection scope of the present invention is not limited to the following embodiment.

[0042] like Figure 1 As shown, this embodiment provides a technical solution: a demand-oriented agile product development process management system, including:

[0043] The R&D demand management module, the pending version management module and the released version management module;

[0044] R&D demand management module: allows users to track and manage product demand in real time, and displays product data in a tree structure, so that users can quickly locate specific products and demands. At the same time, the system also provides operation buttons such as add, select, track, delete and submit, so that users can flexibly manage and adjust demand;

[0045] R&D Demand Management Module: allows users to track and manage product requirements in real time, and displays product data in a tree structure, allowing users to quickly locate specific products and requirements. At the same time, the system also provides operation buttons such as add, select, track, delete, and submit, allowing users to flexibly manage and adjust requirements.

[0046] Released version management module: The system archives and manages the released product versions. Users can view all the released version information of the product in this module. At the same time, the system also provides operation buttons such as cancel release, version plan and test status, which facilitates users to manage and maintain the released versions.

[0047] The steps for R&D process management using the above system are as follows:

[0048] Step 1: Enter R&D requirements in the R&D requirements management, including the requirement name, description, product, module, requirement tag, requirement type, requirement value, impact analysis, implementation degree, workload, planned completion time, requirement source, provider, requirement category and other information;

[0049] Step 2: Adjust the requirements in R&D according to the actual situation;

[0050] Step 3: Keep tracking the development of demand, maintain the start time of development, design completion time, coding completion time, planned completion time, development personnel, workload estimate, overall progress and confirmation information. If there is a change in demand during the tracking process, return to step 2 to rewrite and adjust the demand;

[0051] Step 4: Integrate and submit multiple R&D completed requirements (with an overall progress of 100% and confirmed as yes), generate iteration version information, including iteration version, R&D person in charge, actual start time, end time, iteration target and other information, and push the iteration version information to the version management to be released for version advancement;

[0052] Step 5: Maintain the product development version information in the version management to be released, adjust the iteration version, R&D person in charge, start time, end time, iteration goal, related requirements, related design review meeting, iteration archive information, etc.

[0053] Step 6: Develop and execute the R&D version plan, including the person in charge of each plan, workload, start time, end time, completion progress, etc.

[0054] Step 7: Push the R&D version to the testing team for testing to ensure that the product meets quality requirements;

[0055] Step 8: Continuously monitor the development progress, adjust the version plan completion status according to the actual situation, and maintain the version development progress;

[0056] Step 9: During the development version advancement process, you can repeat steps 5, 6, 7, and 8 until the development version is completed. After confirming that the version meets the release adjustment requirements, you can release the version and push the development version to the released version management.

[0057] Step 10, check the status of the R&D version in the released version management, including the overall plan, test status and other information of the version, and confirm whether to archive the version based on the actual situation. If there is a problem, cancel the release and return to the pending version management to perform steps 5 to 9. If no adjustment is required, archive the version and the R&D process management is completed.

[0058] The present invention adopts a demand-oriented R&D process. After the demand is entered, it immediately enters the R&D stage and makes flexible adjustments as the R&D progresses, ensuring that the demand is closely linked to the R&D activities. Agile R&D management is adopted. During the R&D process, operations such as demand adjustment and tracking can be quickly implemented, and changes in demand can be flexibly responded to. By integrating demand management, management of versions to be released, and management of released versions during R&D, R&D process management can be flexibly and quickly implemented, making the entire R&D process more transparent and team collaboration more efficient.

[0059] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In the description of the present invention, the meaning of "plurality" is at least two, such as two, three, etc., unless otherwise clearly and specifically defined.

[0060] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.

[0061] Although the embodiments of the present invention have been shown and described above, it is to be understood that the above embodiments are exemplary and are not to be construed as limitations of the present invention. A person skilled in the art may change, modify, replace and vary the above embodiments within the scope of the present invention.

Claims

1. A demand-oriented agile product development process management system, characterized in that: include: The R&D demand management module, the pending version management module and the released version management module; Among them, the R&D demand management module is used to allow users to track and manage product requirements under development in real time, display product data through a tree structure, and locate products and requirements; At the same time, relevant operation options are also provided for management and adjustment; To-be-released version management module: used to store product versions to be released, which are associated with multiple completed requirements; Released version management module: used to archive and manage released product versions.

2. The demand-oriented agile product development process management system according to claim 1, characterized in that: The to-be-released version management module is also used to view the specific information of the to-be-released version, including the product name, current stage, version number and associated requirements; At the same time, the version management module to be released provides deletion, iteration plan management, test submission and version release functions.

3. The demand-oriented agile product development process management system according to claim 1, characterized in that: The released version management module is also used to view all released version information of the product, and is also used to cancel release, version plan and test status.

4. A demand-oriented agile product development process management method, the method is based on the management system according to any one of claims 1 to 3, characterized in that: The method comprises the following steps: Step 1: Enter R&D requirements in R&D demand management; Step 2: Adjust the requirements in R&D according to the actual situation; Step 3: Continue to track the development of demand, maintain the development demand, and return to step 2 to rewrite and adjust the demand when there is a change in demand during the tracking process; Step 4: Integrate and submit multiple R&D requirements, generate iterative version information, and push the iterative version information to the version management to be released for version advancement; Step 5: Maintain the product development version information in the version management to be released, and adjust the iteration version, development manager, start time, end time, iteration goal, related requirements, related design review meeting, and iteration archive information; Step 6: Develop and execute a plan for the development version; Step 7: Push the R&D version to the testing team for testing to ensure that the product meets quality requirements; Step 8: Continuously monitor the development progress, adjust the version plan completion status according to the actual situation of the development progress, and maintain the version development progress; Step 9: During the development version advancement process, repeat steps 5, 6, 7, and 8 until the development version is completed. After confirming that the version meets the release adjustment, the version is released and pushed to the released version management; Step 10, check the status of the R&D version in the released version management, and confirm whether to archive the version based on the status of the R&D version. If there is a problem, cancel the release and return to the pending version management to perform steps 5 to 9. If no adjustment is required, the version can be archived and the R&D process management is completed.

5. The demand-oriented agile product development process management method according to claim 4, characterized in that: The content of the R&D requirements entered in step 1 includes the requirement name, description, product, module, requirement label, requirement type, requirement value, impact analysis, degree of realization, workload, planned completion time, requirement source, provider and requirement category.

6. The demand-oriented agile product development process management method according to claim 4, characterized in that: The contents of maintaining R&D requirements in step 3 include: start time, design completion time, coding completion time, planned completion time, R&D personnel, workload estimate, overall progress and confirmation information.

7. The demand-oriented agile product development process management method according to claim 4, characterized in that: The iteration version information includes the iteration version, R&D person in charge, actual start time, end time and iteration target.

8. The demand-oriented agile product development process management method system according to claim 4, characterized in that: The content of the plan for formulating and executing the R&D version includes the person in charge of each plan, workload, start time, end time and completion progress; The R&D version status in the released version management includes the overall plan and testing status of the version.

Images