Demand closed-loop long-chain management system and method

Abstract

The invention discloses a demand closed-loop long-chain management system and method, and relates to the technical field of development demand management, and the implementation process comprises the steps: obtaining and classifying demand information; determining whether to accept the demand according to the demand information, and if yes, assigning a demand principal; a demand manager sets time nodes for demands and specifies demand analysts; the demand analyst splits the original demand into sub-demands; a research and development manager splits a development task according to the sub-requirements, and research and development personnel construct corresponding iteration according to the development task; a tester issues an iteration version and generates a test task; the research and development manager creates a release process of a formal version after the test task is completed, and the project manager initiates a version online process application after the release process passes auditing; and performing statistics on the execution progress of the original demand through a report, and displaying the execution condition of each link. According to the invention, online management and tracking of the demand can be realized, and the demand completion efficiency is accelerated.

Description

Technical Field

[0001] The present invention relates to the technical field of development demand management, and in particular to a demand closed-loop long-chain management system and method. Background Art

[0002] Excel demand management tool is the most familiar and simplest management tool. Excel is suitable for maintenance by a single or a small team. It is easy and quick to use, and can be classified, sorted, and tracked. It can also perform simple quantity statistics and visualization. When the amount of demand data is extremely large, it does not support collaborative processing by multiple people, and Excel data is prone to human confusion or loss.

[0003] Worktitle is a project management system with a very high domestic market share. Although it is not a dedicated demand management system, it has a unique management method in demand management. It has a demand pool, collects requirements widely from members across departments, customizes process configurations, adapts to complex process situations, and configurable demand priorities to provide scheduling that changes with the situation. However, it lacks risk or problem traceability. Summary of the invention

[0004] In view of the needs and deficiencies of current technological development, the present invention provides a demand closed-loop long chain management system and method.

[0005] In the first aspect, the present invention provides a demand closed-loop long chain management system, and the technical solution adopted to solve the above technical problems is as follows:

[0006] A demand closed-loop long chain management system, comprising:

[0007] The demand collection module provides a user-friendly interface for project managers to input customer information and demand information, and is also used to preliminarily classify the submitted demand information according to preset rules;

[0008] The demand acceptance module provides a friendly operation interface for product managers to decide whether to accept the demand based on the demand information and designate a person in charge of the demand when accepting the demand;

[0009] The demand scheduling module provides a friendly operation interface for the demand manager to set the start and end time of demand analysis, demand development, demand testing and demand release according to the demand information, and designate demand analysts;

[0010] The requirements analysis module provides a user-friendly interface for requirements analysts to split the original requirements into sub-requirements that can be identified by R&D personnel;

[0011] The demand development module provides a friendly operation interface for R&D managers to separate development tasks according to sub-demands and assign R&D personnel. It also allows R&D personnel to build corresponding iterations.

[0012] The requirement testing module provides a user-friendly interface for testers to release iterative versions after a development cycle is completed. It also automatically generates and distributes test tasks covering all requirement points through versions. It also allows testers to associate test cases with specific sub-requirements and develop detailed test plans.

[0013] The version release module provides a friendly operation interface for R&D managers to create a formal version release process after the test task is completed and submit it to the reviewer. If the review is passed, the release process is completed and archived. If the review is not passed, the version is returned to the R&D manager.

[0014] The version launch module provides a friendly operation interface for project managers to initiate version launch process applications;

[0015] The report display module provides a friendly display interface for statistics on the overall progress of original requirements, sub-requirements and development tasks through reports, and displays the acceptance rate, analysis rate, R&D rate, testing rate, version release rate and version launch status for project managers, product managers, demand managers, demand analysts, R&D managers, R&D personnel and testers to view.

[0016] Optionally, the demand information entered by the project manager through the operation interface provided by the demand collection module includes demand description, demand source, demand proposer, demand urgency, attachments, and expected release time and online time of the demand;

[0017] The product manager views the demand information through the operation interface provided by the demand acceptance module, and judges the rationality of the demand based on the demand description, expected release time and online time of the demand. a) If the demand is reasonable, the product manager accepts the demand and designates a person in charge to handle it later; b) If the demand is unreasonable, the product manager rejects the demand and gives the reason for rejection based on the demand description, expected release time and online time of the demand, and sends it to the project manager via email or SMS.

[0018] Optionally, through the operation interface provided by the demand development module, the R&D manager first prioritizes the sub-demands split by the demand analyst, then splits out at least one development task according to the sub-demands and their priorities, sets the start and end time of the development task according to the start and end time of the demand development, and then assigns the development task to a specific R&D personnel;

[0019] R&D personnel complete assigned tasks by, on the one hand, setting a batch of sub-requirements and decomposed tasks through the requirements development module to build an iteration, with one iteration serving as a development cycle; on the other hand, managing the code and documents generated during the development process through the requirements development module to facilitate subsequent testing and maintenance.

[0020] Optionally, after the project manager initiates the version launch process application through the version launch module, he / she designates version deployment personnel and integration test verification personnel to implement the final version launch through the demonstration and launch stages in the process. During the demonstration stage, the project manager and the customer will align requirements again to avoid secondary rework after the version is launched.

[0021] Optionally, the demand manager can track the overall progress of the original demand through the display interface provided by the report display module, so as to adjust the schedule in time to cope with possible changes;

[0022] The R&D manager tracks the progress of sub-demands and development tasks through the display interface provided by the report display module to ensure that the requirements are developed as planned.

[0023] In the second aspect, the present invention provides a demand closed-loop long chain management method, and the technical solution adopted to solve the above technical problems is as follows:

[0024] A demand closed-loop long chain management method is based on the demand closed-loop long chain management system of the first aspect, and its management process includes the following steps:

[0025] S1. The project manager enters customer information and demand information through the operation interface provided by the demand collection module and submits it. During the submission process, the demand collection module preliminarily classifies the demand information according to preset rules;

[0026] S2. The product manager checks the demand information through the operation interface provided by the demand acceptance module, decides whether to accept the demand, and designates a person in charge of the demand when deciding to accept the demand;

[0027] S3. The demand manager can view demand information through the operation interface provided by the demand scheduling module, set the start and end time of demand analysis, the start and end time of demand development, the start and end time of demand testing, and the release time of demand, and designate demand analysts;

[0028] S4. The demand analyst checks the demand information through the operation interface provided by the demand analysis module and splits the original demand into sub-requirements that can be identified by R&D personnel;

[0029] S5. The R&D manager uses the operation interface provided by the demand development module to view sub-requirements, separate sub-requirements into development tasks, and assign specific R&D personnel. The R&D personnel build corresponding iterations through the demand development module.

[0030] S6. After a development cycle is completed, the tester releases the iterative version through the operation interface provided by the requirement testing module. The interface automatically generates and distributes test tasks covering all requirement points according to the released version. The tester associates the test cases with specific sub-requirements through the operation interface provided by the requirement testing module and formulates a detailed test plan.

[0031] S7. After the test task is completed, the R&D manager creates the release process of the official version through the operation interface provided by the version release module and submits it to the reviewer. If the reviewer passes the review, the release process is completed and archived. If the reviewer fails the review, the version is returned to the R&D manager.

[0032] S8. The project manager initiates the version launch process application through the operation interface provided by the version launch module;

[0033] S9. Based on the display interface provided by the report display module, the report statistics the overall progress of the original demand, the progress of sub-demands and the progress of development tasks, and displays the acceptance rate, analysis rate, R&D rate, testing rate, version release rate and version online status for project managers, product managers, demand managers, demand analysts, R&D managers, R&D personnel and testers to view.

[0034] Optionally, step S1 is executed, and the demand information entered by the project manager includes the demand description, demand source, demand proposer, demand urgency, attachments, and expected release time and online time of the demand.

[0035] Execute step S2, the product manager views the demand information through the operation interface provided by the demand acceptance module, and judges the rationality of the demand based on the demand description, expected release time and online time of the demand. a) If the demand is reasonable, accept the demand and designate a person in charge of the demand for subsequent processing; b) If the demand is unreasonable, make a decision to reject the demand. At the same time, give the reason for rejection based on the demand description, expected release time and online time of the demand, and send it to the project manager via email or SMS.

[0036] Optionally, in step S5, the R&D manager first prioritizes the sub-demands split by the demand analyst through the operation interface provided by the demand development module, and then splits at least one development task according to the sub-demands and their priorities, sets the start and end time of the development task according to the start and end time of the demand development, and then assigns the development task to a specific R&D personnel;

[0037] R&D personnel complete assigned tasks by, on the one hand, setting a batch of sub-requirements and decomposed tasks through the requirements development module to build an iteration, with one iteration serving as a development cycle; on the other hand, managing the code and documents generated during the development process through the requirements development module to facilitate subsequent testing and maintenance.

[0038] Optionally, execute step S8. After the project manager initiates the version launch process application through the version launch module, he / she designates version deployment personnel and integration test verification personnel to finally launch the version through the demonstration and launch links in the process. During the demonstration link, the project manager and the customer align the requirements again to avoid secondary rework after the version is launched.

[0039] Optionally, when executing step S9, the demand manager tracks the overall progress of the original demand through the display interface provided by the report display module, so as to adjust the schedule in time to cope with possible changes, and the R&D manager tracks the progress of sub-demands and development tasks through the display interface provided by the report display module, so as to ensure that the demand is developed as planned.

[0040] Compared with the prior art, the demand closed-loop long chain management system and method of the present invention has the following beneficial effects:

[0041] The present invention coordinates project managers, product managers, demand managers, demand analysts, R&D managers, and testers online through the processes of collecting demand, accepting demand, scheduling demand, analyzing demand, developing demand, testing demand, releasing versions, and launching versions. The division of labor is clear and personnel are quickly coordinated to efficiently complete demand delivery. The dynamic information of demand is displayed visually through reporting tools, so that the overall progress can be tracked and responsibility can be traced, ultimately forming a closed-loop operation to solve the problem of online demand management. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Attached Figure 1 is a module connection block diagram of the first embodiment of the present invention;

[0043] Attached Figure 2 It is a method flow chart of embodiment 2 of the present invention. DETAILED DESCRIPTION

[0044] In order to make the technical solution, the technical problem solved and the technical effect of the present invention more clearly understood, the technical solution of the present invention is clearly and completely described below in conjunction with specific embodiments.

[0045] Embodiment 1:

[0046] Combined with Figure 1 , this embodiment proposes a demand closed-loop long chain management system, which includes:

[0047] The demand collection module provides a user-friendly interface for project managers to input customer information and demand information, including demand description, demand source, demand proposer, demand urgency, attachments, and expected release and launch time of the demand. It is also used to preliminarily classify the submitted demand information according to preset rules.

[0048] The demand acceptance module provides a friendly operation interface for product managers to view demand information and make reasonable judgments on demand based on demand description, expected release time and online time. a) If the demand is reasonable, the demand will be accepted and a person in charge will be designated to handle the subsequent process. b) If the demand is unreasonable, the decision to reject the demand will be made. At the same time, the reason for rejection will be given based on the demand description, expected release time and online time, and sent to the project manager via email or SMS.

[0049] The demand scheduling module provides a friendly operation interface for the demand manager to set the start and end time of demand analysis, demand development, demand testing and demand release according to the demand information, and designate demand analysts;

[0050] The requirements analysis module provides a user-friendly interface for requirements analysts to split the original requirements into sub-requirements that can be identified by R&D personnel;

[0051] The demand development module provides a friendly operation interface to facilitate R&D managers to prioritize the sub-requirements split by demand analysts, split at least one development task according to the sub-requirements and their priorities, set the start and end time of the development task according to the start and end time of the demand development, and assign the development task to specific R&D personnel; it also allows R&D personnel to set a batch of sub-requirements and decomposed tasks to build an iteration. An iteration is a development cycle, which allows R&D personnel to manage the code and documents generated during the development process, facilitating subsequent testing and maintenance;

[0052] The requirement testing module provides a user-friendly interface for testers to release iterative versions after a development cycle is completed, and automatically generates and distributes test tasks covering all requirement points through versions. It also allows testers to associate test cases with specific sub-requirements and develop detailed test plans to track version quality through bugs and handle version issues in a closed loop, thereby ensuring software quality and stability.

[0053] The version release module provides a friendly operation interface for R&D managers to create a formal version release process after the test task is completed and submit it to the reviewer. If the review is passed, the release process is completed and archived. If the review is not passed, the version is returned to the R&D manager.

[0054] The version launch module provides a friendly operation interface for project managers to initiate version launch process applications, and then designate version deployment personnel and integration test verification personnel to achieve the final version launch through the demonstration and launch phases in the process. During the demonstration phase, the project manager and the customer will align requirements again to avoid secondary rework after the version is launched.

[0055] The report display module provides a friendly display interface for statistics on the overall progress of original requirements, sub-requirements and development tasks through reports, and displays the acceptance rate, analysis rate, R&D rate, testing rate, version release rate and version launch status for project managers, product managers, demand managers, demand analysts, R&D managers, R&D personnel and testers to view.

[0056] It should be added that: the demand manager tracks the overall progress of the original demand through the display interface provided by the report display module, so as to adjust the schedule in time to cope with possible changes; the R&D manager tracks the progress of sub-demands and development tasks through the display interface provided by the report display module, so as to ensure that the demand is developed as planned.

[0057] Embodiment 2:

[0058] Combined with Figure 2 This embodiment proposes a demand closed-loop long chain management method. Based on the demand closed-loop long chain management system described in Embodiment 1, the management process includes the following steps:

[0059] S1. The project manager enters and submits customer information and demand information through the operation interface provided by the demand collection module. The demand information includes demand description, demand source, demand proposer, demand urgency, attachments, and expected release time and online time of the demand. During the submission process, the demand collection module preliminarily classifies the demand information according to preset rules.

[0060] S2. The product manager checks the demand information through the operation interface provided by the demand acceptance module, and judges the rationality of the demand based on the demand description, expected release time and online time of the demand. a) If the demand is reasonable, the product manager accepts the demand and designates a person in charge to handle it later. b) If the demand is unreasonable, the product manager rejects the demand. At the same time, the product manager gives the reason for rejection based on the demand description, expected release time and online time of the demand, and sends it to the project manager via email or SMS.

[0061] S3. The demand manager can view demand information through the operation interface provided by the demand scheduling module, set the start and end time of demand analysis, the start and end time of demand development, the start and end time of demand testing, and the release time of demand, and designate demand analysts.

[0062] It should be added that the person in charge of demand tracks the overall progress of the original demand through the display interface provided by the report display module so as to adjust the schedule in time to cope with possible changes.

[0063] S4. The demand analyst checks the demand information through the operation interface provided by the demand analysis module and splits the original demand into sub-requirements that can be identified by R&D personnel;

[0064] S5. The R&D manager uses the operation interface provided by the demand development module to view the sub-requirements, prioritize the sub-requirements split by the demand analyst, split at least one development task based on the sub-requirements and their priorities, set the start and end time of the development task based on the start and end time of the demand development, and then assign the development task to a specific R&D personnel;

[0065] R&D personnel complete assigned tasks by, on the one hand, setting a batch of sub-requirements and decomposed tasks through the requirements development module to build an iteration, with one iteration serving as a development cycle; on the other hand, managing the code and documents generated during the development process through the requirements development module to facilitate subsequent testing and maintenance.

[0066] It should be added that the R&D manager tracks the progress of sub-demands and development tasks through the display interface provided by the report display module to ensure that the requirements are developed as planned.

[0067] S6. After a development cycle is completed, the tester releases the iterative version through the operation interface provided by the requirement testing module. The interface automatically generates and distributes test tasks covering all requirement points based on the released version; the tester associates the test cases with specific sub-requirements through the operation interface provided by the requirement testing module, and formulates a detailed test plan to track version quality through bugs and handle version issues in a closed loop, thereby ensuring software quality and stability.

[0068] S7. After the test task is completed, the R&D manager creates the release process of the official version through the operation interface provided by the version release module and submits it to the reviewer. If the reviewer passes the review, the release process is completed and archived. If the reviewer fails the review, the version is returned to the R&D manager.

[0069] S8. The project manager initiates the version launch process application through the operation interface provided by the version launch module, and then designates version deployment personnel and integration test verification personnel to achieve the final version launch through the demonstration and launch links in the process. During the demonstration link, the project manager and the customer will align the requirements again to avoid secondary rework after the version is launched.

[0070] S9. Based on the display interface provided by the report display module, the report statistics the overall progress of the original demand, the progress of sub-demands and the progress of development tasks, and displays the acceptance rate, analysis rate, R&D rate, testing rate, version release rate and version online status for project managers, product managers, demand managers, demand analysts, R&D managers, R&D personnel and testers to view.

[0071] In summary, by adopting a demand closed-loop long-chain management system and method of the present invention, online management and tracking of demand can be achieved, thereby accelerating the efficiency of demand completion.

[0072] The above specific examples are used to explain the principles and implementation methods of the present invention in detail. These examples are only used to help understand the core technical content of the present invention. Based on the above specific embodiments of the present invention, any improvements and modifications made by technicians in this technical field without departing from the principles of the present invention should fall within the scope of patent protection of the present invention.

Claims

1. A demand closed-loop long chain management system, characterized in that: It includes: The demand collection module provides a user-friendly interface for project managers to input customer information and demand information, and is also used to preliminarily classify the submitted demand information according to preset rules; The demand acceptance module provides a friendly operation interface for product managers to decide whether to accept the demand based on the demand information and designate a person in charge of the demand when accepting the demand; The demand scheduling module provides a friendly operation interface for the demand manager to set the start and end time of demand analysis, demand development, demand testing and demand release according to the demand information, and designate demand analysts; The requirements analysis module provides a user-friendly interface for requirements analysts to split the original requirements into sub-requirements that can be identified by R&D personnel; The demand development module provides a friendly operation interface for R&D managers to separate development tasks according to sub-demands and assign R&D personnel. It also allows R&D personnel to build corresponding iterations. The requirement testing module provides a user-friendly interface for testers to release iterative versions after a development cycle is completed. It also automatically generates and distributes test tasks covering all requirement points through versions. It also allows testers to associate test cases with specific sub-requirements and develop detailed test plans. The version release module provides a friendly operation interface for R&D managers to create a formal version release process after the test task is completed and submit it to the reviewer. If the review is passed, the release process is completed and archived. If the review is not passed, the version is returned to the R&D manager. The version launch module provides a friendly operation interface for project managers to initiate version launch process applications; The report display module provides a friendly display interface for statistics on the overall progress of original requirements, sub-requirements and development tasks through reports, and displays the acceptance rate, analysis rate, R&D rate, testing rate, version release rate and version launch status for project managers, product managers, demand managers, demand analysts, R&D managers, R&D personnel and testers to view.

2. A demand closed-loop long chain management system according to claim 1, characterized in that: The demand information entered by the project manager through the operation interface provided by the demand collection module includes demand description, demand source, demand proposer, demand urgency, attachments, and expected release time and online time of the demand; The product manager views the demand information through the operation interface provided by the demand acceptance module, and judges the rationality of the demand based on the demand description, expected release time and online time of the demand. a) If the demand is reasonable, the product manager accepts the demand and designates a person in charge of the demand for subsequent processing; b) If the demand is unreasonable, the product manager decides to reject the demand. At the same time, the product manager gives the reason for rejection based on the demand description, expected release time and online time of the demand, and sends it to the project manager via email or SMS.

3. A demand closed-loop long chain management system according to claim 1, characterized in that: Through the operation interface provided by the demand development module, the R&D manager first prioritizes the sub-demands split by the demand analyst, then splits out at least one development task based on the sub-demand and its priority, sets the start and end time of the development task based on the start and end time of the demand development, and then assigns the development task to a specific R&D personnel; R&D personnel complete assigned tasks by, on the one hand, setting a batch of sub-requirements and decomposed tasks through the requirements development module to build an iteration, with one iteration serving as a development cycle; on the other hand, managing the code and documents generated during the development process through the requirements development module to facilitate subsequent testing and maintenance.

4. A demand closed-loop long chain management system according to claim 1, characterized in that: After the project manager initiates the version launch process application through the version launch module, he / she designates version deployment personnel and integration test verification personnel to finally launch the version through the demonstration and launch stages in the process. During the demonstration stage, the project manager and the customer will align requirements again to avoid secondary rework after the version is launched.

5. A demand closed-loop long chain management system according to claim 1, characterized in that: The demand manager can track the overall progress of the original demand through the display interface provided by the report display module, so as to adjust the schedule in time to cope with possible changes; The R&D manager tracks the progress of sub-demands and development tasks through the display interface provided by the report display module to ensure that the requirements are developed as planned.

6. A demand closed-loop long chain management method, characterized in that: Based on the demand closed-loop long chain management system as claimed in claim 1, the management process includes the following steps: S1. The project manager enters customer information and demand information through the operation interface provided by the demand collection module and submits it. During the submission process, the demand collection module preliminarily classifies the demand information according to preset rules; S2. The product manager checks the demand information through the operation interface provided by the demand acceptance module, decides whether to accept the demand, and designates a person in charge of the demand when deciding to accept the demand; S3. The demand manager can view demand information through the operation interface provided by the demand scheduling module, set the start and end time of demand analysis, the start and end time of demand development, the start and end time of demand testing, and the release time of demand, and designate demand analysts; S4. The demand analyst checks the demand information through the operation interface provided by the demand analysis module and splits the original demand into sub-requirements that can be identified by R&D personnel; S5. The R&D manager uses the operation interface provided by the demand development module to view sub-requirements, separate sub-requirements into development tasks, and assign specific R&D personnel. The R&D personnel build corresponding iterations through the demand development module. S6. After a development cycle is completed, the tester releases the iterative version through the operation interface provided by the requirement testing module. The interface automatically generates and distributes test tasks covering all requirement points according to the released version. The tester associates the test cases with specific sub-requirements through the operation interface provided by the requirement testing module and formulates a detailed test plan. S7. After the test task is completed, the R&D manager creates the release process of the official version through the operation interface provided by the version release module and submits it to the reviewer. If the reviewer passes the review, the release process is completed and archived. If the reviewer fails the review, the version is returned to the R&D manager. S8. The project manager initiates the version launch process application through the operation interface provided by the version launch module; S9. Based on the display interface provided by the report display module, the report statistics the overall progress of the original demand, the progress of sub-demands and the progress of development tasks, and displays the acceptance rate, analysis rate, R&D rate, testing rate, version release rate and version online status for project managers, product managers, demand managers, demand analysts, R&D managers, R&D personnel and testers to view.

7. A demand closed-loop long chain management method according to claim 6, characterized in that: Execute step S1, the demand information entered by the project manager includes demand description, demand source, demand proposer, demand urgency, attachments, and expected release time and online time of the demand. Execute step S2, the product manager views the demand information through the operation interface provided by the demand acceptance module, and judges the rationality of the demand based on the demand description, the expected release time and the online time of the demand, a) accepts the demand when it is reasonable, and designates a person in charge of the demand for subsequent processing, b) makes a decision to reject the demand when it is unreasonable, and at the same time, gives the reason for rejection based on the demand description, the expected release time and the online time of the demand, and sends it to the project manager via email or SMS.

8. A demand closed-loop long chain management method according to claim 6, characterized in that: Execute step S5, through the operation interface provided by the demand development module, the R&D manager first prioritizes the sub-demands split by the demand analyst, then splits at least one development task according to the sub-demand and its priority, sets the start and end time of the development task according to the start and end time of the demand development, and then assigns the development task to a specific R&D personnel; R&D personnel complete assigned tasks by, on the one hand, setting a batch of sub-requirements and decomposed tasks through the requirements development module to build an iteration, with one iteration serving as a development cycle; on the other hand, managing the code and documents generated during the development process through the requirements development module to facilitate subsequent testing and maintenance.

9. A demand closed-loop long chain management method according to claim 6, characterized in that: Execute step S8. After the project manager initiates the version launch process application through the version launch module, he / she designates version deployment personnel and integration test verification personnel to implement the final version launch through the demonstration and launch stages in the process. During the demonstration stage, the project manager and the customer will align requirements again to avoid secondary rework after the version is launched.

10. A demand closed-loop long chain management method according to claim 6, characterized in that: When executing step S9, the demand manager tracks the overall progress of the original demand through the display interface provided by the report display module, so as to adjust the schedule in time to cope with possible changes. The R&D manager tracks the progress of sub-demands and development tasks through the display interface provided by the report display module, so as to ensure that the demand is developed as planned.

Images