Agile development management method and device, computer equipment and readable storage medium

Abstract

The invention discloses an agile development management method and device, computer equipment and a readable storage medium, and the method comprises the steps: firstly, automatically recognizing and storing a total demand file required by a user from a target IT management service system to a preset MySQL database through responding to a data docking instruction; furthermore, the method can respond to a user demand instruction, and performs processing in combination with the full demand file to obtain a processing result. And finally, judging whether the processing result is finished or not through data statistics and a visualization technology so as to obtain a monitoring result of agile development management. According to the method, automation, real-time performance and visualization of the agile development process are realized, and the development efficiency and the monitoring accuracy are remarkably improved.

Description

Technical Field

[0001] The present invention relates to the field of agile development, and in particular to an agile development management method, apparatus, computer equipment and readable storage medium. Background Art

[0002] In the current software development field, agile development methods have attracted widespread attention for their ability to quickly respond to changes and deliver efficiently. However, traditional agile development management methods often rely on manual tracking and manual data processing, which leads to problems such as information delays, inefficient processing, and inaccurate monitoring. Summary of the invention

[0003] The object of the present invention is to provide an agile development management method, apparatus, computer equipment and readable storage medium. An embodiment of the present invention provides an agile development management method, including:

[0004] In response to the data connection instruction, a full demand file of the user's demand is identified from the target IT management service system, and the full demand file is stored in a preset MySQL database;

[0005] In response to the user's demand instruction, processing is performed in combination with the full demand file to obtain a processing result;

[0006] Through data statistics and visualization, we try to determine whether the processing results are completed and obtain the agile development management monitoring results.

[0007] In a possible implementation, identifying a full demand file of user demand from the target IT management service system and storing the full demand file in a preset MySQL database includes:

[0008] Identify the requirement document type of the full requirement document of user requirements from the target IT management service system;

[0009] Parsing the full demand file into structured data according to the demand file type;

[0010] The parsed structured data is imported into the preset MySQL database, and the database records are automatically updated according to data changes.

[0011] In a possible implementation, the user demand instruction includes a priority sorting instruction, the full demand file includes development, review, and production node information of the demand, and the response to the user demand instruction is combined with the full demand file to perform processing to obtain a processing result, including:

[0012] In response to the priority sorting instruction, the target demand is prioritized to obtain the target priority of the target demand;

[0013] The development, review and production node information corresponding to the target demand are updated according to the target priority.

[0014] In a possible implementation, the user demand instruction includes a scheduling review instruction, the full demand file includes a review window, and the response to the user demand instruction is combined with the full demand file to perform processing to obtain a processing result, including:

[0015] In response to the scheduling review instruction, creating a target review window for the target requirement and setting a date and status of the target review window;

[0016] Associating the target requirement with the target review window, and adding the design document SVN path corresponding to the target requirement to the target review window;

[0017] The review result of the target requirement in the target review window is updated to the preset MySQL database.

[0018] In a possible implementation, the user demand instruction includes a production scheduling instruction, the full quantity demand file includes a production window, and the response to the user demand instruction and the full quantity demand file are processed to obtain a processing result, including:

[0019] In response to the production scheduling instruction, a target production window is created according to the business requirements included in the production scheduling instruction; the business requirements include front-end packages, back-end system packages, client packages, data scripts and ESB packages;

[0020] Add the target requirements that have passed the test to the target production window and set the production date;

[0021] The production result of the target demand in the target production window is updated to the preset MySQL database.

[0022] In a possible implementation, the trying to determine whether the processing result is completed through data statistics and visualization to obtain the agile development management monitoring result includes:

[0023] Attempt to obtain the processing progress of the processing results through data statistics and visualization;

[0024] Determine the processing efficiency according to the development requirements corresponding to the processing results;

[0025] It is determined whether the current progress is lagging behind according to the processing progress and the preset progress requirement, and in the case of lag, the progress is highlighted and displayed on the web page according to the severity level.

[0026] In a possible implementation, the method further includes:

[0027] In response to the new adding instruction, new management user or new development company information for the example system of the present invention is entered.

[0028] In a second aspect, an embodiment of the present invention provides an agile development management device, including:

[0029] The management module is used to respond to data docking instructions, identify the full requirement file of user needs from the target IT management service system, and store the full requirement file in a preset MySQL database; respond to user requirement instructions, process the full requirement file to obtain processing results; try to determine whether the processing results are completed through data statistics and visualization, and obtain agile development management monitoring results.

[0030] In a third aspect, an embodiment of the present invention provides a computer device, comprising a processor and a non-volatile memory storing computer instructions, wherein when the computer instructions are executed by the processor, the computer device executes the method described in at least one possible implementation of the first aspect.

[0031] In a fourth aspect, an embodiment of the present invention provides a readable storage medium, wherein the readable storage medium includes a computer program, and when the computer program is executed, the computer device where the readable storage medium is located is controlled to execute the method described in at least one possible implementation manner of the first aspect.

[0032] Compared with the prior art, the beneficial effects provided by the present invention include: using an agile development management method, device, computer equipment and readable storage medium disclosed in the present invention, including: first, by responding to data docking instructions, automatically identifying and storing the full demand file of user needs from the target IT management service system to a preset MySQL database. Furthermore, the method can respond to user demand instructions, combine the full demand file for processing, and obtain processing results. Finally, through data statistics and visualization technology, it is determined whether the processing result is completed, thereby obtaining the monitoring result of agile development management. The present invention realizes the automation, real-time and visualization of the agile development process, significantly improving development efficiency and monitoring accuracy. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings required for use in the embodiments are briefly introduced below. It should be understood that the following drawings only illustrate certain embodiments of the present invention and should not be regarded as limiting the scope. For those of ordinary skill in the art, other related drawings can also be obtained based on these drawings without creative work.

[0034] Figure 1 A schematic diagram of the steps of the agile development management method provided by an embodiment of the present invention;

[0035] Figure 2 A schematic block diagram of the structure of an agile development management device provided by an embodiment of the present invention;

[0036] Figure 3 A schematic block diagram of the structure of a computer device provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0037] In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Generally, the components of the embodiments of the present invention described and shown in the drawings here can be arranged and designed in various different configurations.

[0038] The specific implementation modes of the present invention are described in detail below in conjunction with the accompanying drawings.

[0039] In order to solve the technical problems in the aforementioned background technology, Figure 1 This is a flow chart of an agile development management method provided in an embodiment of the present disclosure. The agile development management method is introduced in detail below.

[0040] Step S201, in response to the data connection instruction, identifying a full demand file of the user's demand from the target IT management service system, and storing the full demand file in a preset MySQL database;

[0041] Step S202, responding to the user demand instruction, processing in combination with the full demand file to obtain a processing result;

[0042] Step S203, attempting to determine whether the processing result is completed through data statistics and visualization, and obtaining agile development management monitoring results.

[0043] In an embodiment of the present invention, exemplarily, the server receives a data docking instruction from the development team, which requires obtaining the demand files submitted by all current users from the company's IT service management system. The server communicates with the target IT management service system through a preset API interface, and successfully identifies and extracts the full demand files of all user requirements. It also supports users to manually download from the target IT management service system and upload to the server. These files contain various types of business requirements, such as functional enhancement, performance optimization, bug fixes, etc. The server then stores these full demand files in a preset MySQL database for subsequent processing and analysis.

[0044] The development team submitted a user requirement instruction through the server interface, requesting that all stored requirement files be prioritized and a preliminary development plan be generated. After receiving this instruction, the server began to process the full amount of requirement files, first analyzing the urgency and importance of each requirement, and then sorting these requirements according to the preset priority rules. After the sorting is completed, the server generates a preliminary development plan based on the available resources and time window of the development team, including information such as the allocation of requirements and the estimated completion time. This processing result is saved in the server's memory, ready for the next step of monitoring and visualization.

[0045] The agile development management platform on the server begins to perform data statistics and visualization tasks. It first collects key data from the processing results, such as the progress of each requirement, the workload of developers, and the estimated completion time. Then, this data is converted into charts and dashboards and presented to the development team through the web interface. The development team can use these visual views to monitor the progress of the requirements in real time and determine whether the processing results are as expected. If any problems or deviations are found, the team can adjust the plan in time to ensure the smooth progress of the agile development process. Finally, the server generates an agile development management monitoring result report for the team to further analyze and make decisions.

[0046] In the embodiment of the present invention, the aforementioned step S201 can be implemented through the following example execution.

[0047] Identify the requirement document type of the full requirement document of user requirements from the target IT management service system;

[0048] Parsing the full demand file into structured data according to the demand file type;

[0049] The parsed structured data is imported into the preset MySQL database, and the database records are automatically updated according to data changes.

[0050] In the embodiment of the present invention, the server obtains the full amount of demand files of user requirements stored in the target IT management service system directly (automatically) or indirectly (manually) from the system. These files are in Excel table format. The server accurately identifies the specific type of each demand file by file extension or content features for subsequent processing.

[0051] After identifying the required file type, the server uses a preset parser or parsing script to read the row and column data therein and convert it into a database table structure.

[0052] After parsing is complete, the server imports the structured data into the preset MySQL database. During the import process, the server will determine whether the data already exists based on the unique identifier of the data (such as the requirement number). If it does exist, the server will update the corresponding record in the database; if it does not exist, the server will add a new record. At the same time, the server will also set triggers or listeners to automatically update database records when the data changes, ensuring that the information in the database is synchronized with the information in the IT service management system.

[0053] Through the above steps, the server can effectively identify, parse and store the full requirement files of user needs from the target IT management service system, providing accurate data support for subsequent agile development management.

[0054] In an embodiment of the present invention, the user demand instruction includes a priority sorting instruction, and the full demand file includes development, review, and production node information of the demand. The aforementioned step S202 can be implemented through the following example execution.

[0055] In response to the priority sorting instruction, the target demand is prioritized to obtain the target priority of the target demand;

[0056] The development, review and production node information corresponding to the target demand are updated according to the target priority.

[0057] In an embodiment of the present invention, illustratively, the development team submits a prioritization instruction through the server interface, requesting that the currently stored full demand files be prioritized. After receiving this instruction, the server begins to process the full demand files. It first analyzes the importance and urgency of each requirement, which may involve multiple dimensions such as the business value, customer impact, and technical difficulty of the requirement. Then, the server prioritizes each requirement according to the preset priority rules. For example, the requirements are divided into three priorities: "high", "medium", and "low". After the processing is completed, the server obtains the target priority information for each target requirement.

[0058] After obtaining the target priority of the target requirement, the server begins to update the development, review, and production node information corresponding to each requirement based on this priority information. For requirements with a "high" priority, the server may advance their development nodes to ensure that these requirements can enter the development stage as soon as possible. At the same time, the server will also update the review and production nodes of these requirements to ensure that they can be given priority throughout the agile development process. For requirements with "medium" and "low" priorities, the server will make reasonable arrangements based on the resources and time windows of the development team. After the update is completed, the server generates a new development plan, including the development, review, and production node information of each requirement and the corresponding status (such as "to be developed", "under development", "to be reviewed", "put into production", etc.). This new development plan is saved in the server's memory and is ready to be presented to the development team through a visual interface.

[0059] In an embodiment of the present invention, the user demand instruction includes a scheduling review instruction, and the full demand file includes a review window. The aforementioned step S202 can be implemented through the following example execution.

[0060] In response to the scheduling review instruction, creating a target review window for the target requirement and setting a date and status of the target review window;

[0061] Associating the target requirement with the target review window, and adding the design document SVN path corresponding to the target requirement to the target review window;

[0062] The review result of the target requirement in the target review window is updated to the preset MySQL database.

[0063] In an embodiment of the present invention, the development team submits a review scheduling instruction through the server interface, requesting a review scheduling for currently stored specific requirements. After receiving this instruction, the server first identifies the target requirements that need to be reviewed, and then creates a review window for these target requirements. The server sets the date of the review window to three days later, that is, the development team hopes to conduct a review after these three days, and sets the status of the review window to "pending review".

[0064] After creating the review window, the server associates the target requirement with the review window to ensure that the requirements to be reviewed can be accurately identified during the review. At the same time, the server also extracts the design document SVN path corresponding to each target requirement from the full requirement file and adds these paths to the review window. In this way, reviewers can directly access the design document through the SVN path during the review, improving the review efficiency.

[0065] When the review window arrives, the development team conducts a review and submits the review results to the server. After receiving the review results, the server updates them to the preset MySQL database. The review results may include information such as the feasibility of the requirements, technical difficulty, and estimated development time. The server also updates the status of the target requirements based on the review results, for example, changing the status from "pending review" to "review passed" or "review failed". In this way, the development team and other relevant personnel can query the latest review results and requirement status through the database.

[0066] In an embodiment of the present invention, the user demand instruction includes a production scheduling instruction, and the full demand file includes a production window. The aforementioned step S202 can be implemented through the following example execution.

[0067] In response to the production scheduling instruction, a target production window is created according to the business requirements included in the production scheduling instruction; the business requirements include front-end packages, back-end system packages, client packages, data scripts and ESB packages;

[0068] Add the target requirements that have passed the test to the target production window and set the production date;

[0069] The production result of the target demand in the target production window is updated to the preset MySQL database.

[0070] In an embodiment of the present invention, the development team submits a production scheduling instruction through the server interface, requesting that the current requirements that have been tested be scheduled for production. After receiving this instruction, the server first parses out the business requirements contained in the instruction, which specifically include front-end packages, back-end system packages (such as order systems, payment systems, etc.), client packages, data scripts, and ESB (Enterprise Service Bus) packages. Based on these business requirements, the server creates a target production window, which will be used to manage the production process of these business requirements.

[0071] The server selects the target requirements that have passed the test from the full requirement file. These requirements have completed the development and review stages and have reached the production standards. The server adds these target requirements to the target production window created previously and sets a specific production date for each requirement. The setting of the production date takes into account factors such as the resource allocation of the development team, the priority of business requirements, and the market window.

[0072] When the launch date arrives, the development team performs the launch operation and submits the launch results to the server. After receiving the launch results, the server updates them to the preset MySQL database. The launch results may include the launch status of each requirement (such as "successful launch", "failed launch"), problem records during the launch, and system performance data after launch. By updating the database, the development team and other relevant personnel can query the latest launch results and demand status in real time to carry out subsequent development or operation and maintenance work.

[0073] In the embodiment of the present invention, the aforementioned step S203 can be implemented through the following example execution.

[0074] Obtaining the processing progress of the processing results through data statistics and visual views;

[0075] Determine the processing efficiency according to the development requirements corresponding to the processing results;

[0076] Whether the progress is behind schedule is determined based on the processing progress and the preset progress requirement, and in the case of a delay, the progress is highlighted and displayed on the web page according to the severity level.

[0077] In an embodiment of the present invention, exemplarily, the server periodically extracts processing result data from a preset MySQL database, which includes progress information of each link from demand identification, priority sorting, review scheduling, production scheduling to final production. The server uses this data to generate a visual progress chart, such as a Gantt chart or a burning chart, to intuitively display the processing progress of each demand. For example, in the Gantt chart, each demand corresponds to a bar, the length of the bar indicates the processing time, and the color indicates the processing status (such as green for in progress and red for lagging). The server analyzes the processing result data and calculates the processing efficiency of each development demand. The processing efficiency can be determined by comparing the actual processing time and the expected processing time. For example, if the expected development time of a demand is 10 days, and the actual development time is 8 days, then the processing efficiency of this demand is 80% (actual time / estimated time). The development team presets the progress requirements for each time node before the production of the demand. For example, if the production date is T, the demand process needs to be advanced to the "closing version confirmation" node on T-7, and the demand process needs to be advanced to the "business test" node on T-14. If a certain demand is less than 7 days away from the production date and the demand process node is in the "closing version confirmation", the demand has no lag. If a certain demand is less than 7 days away from the production date and the demand process node is in the "business test", the demand is delayed by level 1. If a certain demand is less than 7 days away from the production date and the demand process node is in the "functional test" (the node before the business test), the demand is delayed by level 2. By analogy, the level of lag is equal to the number of nodes where the demand process should be located and the node where the demand process is currently located. The server counts the lag of each demand and highlights the level on the web page. .

[0078] In the embodiments of the present invention, the following implementation modes are also provided.

[0079] In response to the new adding instruction, new management user or new development company information for the example system of the present invention is entered.

[0080] In the embodiment of the present invention, the server receives a new instruction, which requires that the information of a new management user or a new development company be entered into the example system of the present invention. The instruction may come from a system administrator or a user with corresponding authority.

[0081] The server first parses the new instruction to determine whether it needs to add management user information or development company information. Then, the server opens an entry interface and prompts you to enter the relevant user or company information.

[0082] For new management users, the server requires the user to enter basic information such as name, login name, password, email address, etc., and requires the user's role and permissions to be set in order to determine the user's operating scope and level in the system.

[0083] For a new development company, the server requires you to enter the company name and abbreviation.

[0084] After entering all the necessary information, the server verifies the information to ensure its accuracy and completeness. If the information is verified, the server saves the information of the new management user or new development company to the preset MySQL database and updates the relevant user or company list.

[0085] Finally, the server generates an operation log to record the execution and results of the new instruction for subsequent auditing and tracking. At the same time, the server also sends a notification to the user who submitted the new instruction, informing him that the new operation has been successfully completed.

[0086] In order to more clearly describe the solution provided by the embodiment of the present application, a more detailed implementation method is provided below.

[0087] The embodiment of the present invention adopts Vue+Springboot+MySQL+Redis, and the front-end and back-end are separated. The front-end page adopts Vue, which is mainly responsible for display and simple data processing and interface calling; the back-end service adopts Springboot, which is mainly used to process requests, logical calculations, database queries and other operations sent by the front-end; the database adopts MySQL, which is used to process system data, such as demand data, user data, etc.; the cache database adopts Redis, which is used to save user login session data.

[0088] The embodiment of the present invention introduces the following models, based on which database tables and business objects are established:

[0089] Demand model. It is the basic model of demand, which consists of demand number, demand title, demand category, proposer, proposer, status node and other elements.

[0090] Active requirement model. This is a model of the requirement development status. It consists of elements such as requirement number, developer, developer, and workload.

[0091] Requirements analysis and design review window model. It is a model for the requirements review meeting. It consists of elements such as window date, window status (open, sealed, closed), and review requirements list.

[0092] Production window model. It is a model for production planning. It consists of elements such as window date, window status (open, closed, or disabled), and production requirement list.

[0093] User model. It is the basic model of the user. It consists of user ID, user name, password, company, role and other elements.

[0094] Based on the above model, we designed the following database tables:

[0095] Demand summary table. Stores all demand data in the system.

[0096] Active requirement table. After a requirement is activated by a developer, the requirement number and the data filled in by the developer are stored in this table.

[0097] Requirements analysis and design review window table. Requirements management personnel create new review windows and store them in this table.

[0098] Requirements analysis and design review window and requirements association table. After the developer adds the review requirements to the window, the window ID and requirement number, as well as the SVN path of the requirements review document and other information are stored in this table. After the review meeting, the review results are also stored in this table.

[0099] Production window table. After medical staff create a new production window, it is stored in this table.

[0100] The production window and demand association table. After the business personnel add the demand to be put into production to the window, the window ID, demand number, packaging information and other information are stored in this table. After production, the production results are also stored in this table.

[0101] User table. Stores information such as user ID, user name, password, company ID, etc.

[0102] Role table. Stores role ID and role name.

[0103] Company table. Stores company ID, abbreviation, and full name.

[0104] User role association table. Stores user ID and role ID.

[0105] The system implemented in the embodiment of the present invention has the following functions:

[0106] Demand import and synchronization. The requirements in the IT service management system include the requirement number, requirement title, requirement description, proposer, current node, person to be processed and other elements. After all of them are exported to Excel, they are dragged into the system of the embodiment of the present invention. The system will automatically determine whether the operation on the requirement is to add or update. After the requirements are imported, the organization to which the proposer belongs is identified according to the matching rules, and the organization name attribute is added to the requirements. The flow of the demand process is still operated in the IT service management system. This function should be operated at least once every working day to ensure the timeliness of the data.

[0107] Priority sorting. Business personnel log in to the system and mark the priority of the requirements based on the customer (application organization), and the system will sort them according to the priority.

[0108] Full demand query. All users can use this function to query the full demand information of the system. They can filter and query based on fields such as demand number, demand title, application organization, process node, etc., and sort in ascending order according to priority.

[0109] Active (development-initiated) demand query. All users can use this function to query the demand information being developed in the system. In addition to basic demand information, it also displays data such as the developer (partner company), developer, and workload.

[0110] Start development. The development project manager clicks "Start new demand" and enters the demand number to be started (fuzzy query). After the system matches the corresponding demand, click "Start" to start development. At this time, the demand can be queried in the "Active demand query" menu.

[0111] Active requirement maintenance. The development project manager can click "Edit" after each active requirement and fill in the corresponding data according to the actual situation.

[0112] Requirements design review window maintenance and review requirements collection. Requirements management personnel regularly organize offline design review meetings, and requirements management personnel enter the review window into the "Requirements Analysis and Design Review Window Management". Developers add requirements and corresponding design document SVN paths to the appropriate review window based on the requirements design progress. Requirements management personnel export the requirements list for this review before the review.

[0113] Production window maintenance and production demand scheduling. Business personnel formulate production windows according to business needs and enter them into the "Production Window Management" page. Business personnel add the requirements that have passed the test to the production window. The system automatically calculates whether the current progress is delayed according to the specified time requirements.

[0114] Production packaging management. Developers fill in the production package information of the requirements they are responsible for developing based on the production requirements list in the production window, such as front-end packages, back-end system packages, client packages, data scripts, ESB packages, etc.

[0115] Demand dashboard. Based on the production window, the requirements in the current window are displayed according to node classification, such as "to be developed", "under development", "under testing", "to be put into production", and "completed". It also shows whether the progress of the current requirements has been delayed.

[0116] Data statistics. Project managers can use this function to view the demand quantity and workload summary data of each developer, and can summarize the data within the current range according to the selected time range.

[0117] User management. Administrators can add new users and developer companies. All users can change their passwords.

[0118] Please refer to Figure 2 , Figure 2 An agile development management device 110 provided in an embodiment of the present invention includes:

[0119] The management module is used to respond to data docking instructions, identify the full requirement file of user needs from the target IT management service system, and store the full requirement file in a preset MySQL database; respond to user requirement instructions, process the full requirement file to obtain processing results; try to determine whether the processing results are completed through data statistics and visualization, and obtain agile development management monitoring results.

[0120] It should be noted that the implementation principle of the aforementioned agile development management device 110 can refer to the implementation principle of the aforementioned agile development management method, and will not be repeated here. It should be understood that the division of the various modules of the above device is only a division of logical functions. In actual implementation, they can be fully or partially integrated into a physical entity, or physically separated. And these modules can all be implemented in the form of software calling through processing elements; they can also be all implemented in the form of hardware; some modules can also be implemented in the form of software calling through processing elements, and some modules can be implemented in the form of hardware. For example, the agile development management device 110 can be a separately established processing element, or it can be integrated in a chip of the above device. In addition, it can also be stored in the memory of the above device in the form of program code, and called and executed by a processing element of the above device. The function of the above agile development management device 110. The implementation of other modules is similar. In addition, these modules can be fully or partially integrated together, or they can be implemented independently. The processing element described here can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each of the above modules can be completed by an integrated logic circuit of hardware in the processor element or instructions in the form of software.

[0121] For example, the above modules may be one or more integrated circuits configured to implement the above methods, such as one or more application specific integrated circuits (ASIC), or one or more microprocessors (digital signal processors, DSP), or one or more field programmable gate arrays (FPGA), etc. For another example, when a module above is implemented in the form of a processing element scheduling program code, the processing element may be a general-purpose processor, such as a central processing unit (CPU) or other processor that can call program code. For another example, these modules may be integrated together and implemented in the form of a system-on-a-chip (SOC).

[0122] The embodiment of the present invention provides a computer device 100, which includes a processor and a non-volatile memory storing computer instructions. When the computer instructions are executed by the processor, the computer device 100 executes the aforementioned agile development management apparatus 110. Figure 3 As shown, Figure 3 The computer device 100 provided in the embodiment of the present invention is a structural block diagram. The computer device 100 includes an agile development management apparatus 110 , a memory 111 , a processor 112 and a communication unit 113 .

[0123] To achieve data transmission or interaction, the memory 111, the processor 112 and the communication unit 113 are electrically connected to each other directly or indirectly. For example, the electrical connection between these elements can be achieved through one or more communication buses or signal lines. The agile development management device 110 includes at least one software function module that can be stored in the memory 111 in the form of software or firmware or solidified in the operating system (OS) of the computer device 100. The processor 112 is used to execute the agile development management device 110 stored in the memory 111, such as the software function modules and computer programs included in the agile development management device 110.

[0124] An embodiment of the present invention provides a readable storage medium, which includes a computer program. When the computer program is running, the computer device where the readable storage medium is located is controlled to execute the aforementioned agile development management method.

[0125] For illustrative purposes, the foregoing description is made with reference to specific embodiments. However, the above illustrative discussion is not intended to be exhaustive or to limit the present disclosure to the precise form disclosed. Numerous modifications and variations are possible in accordance with the above teachings. These embodiments are selected and described in order to best illustrate the principles of the present disclosure and its practical application, so that those skilled in the art can best utilize the present disclosure and utilize various embodiments with different modifications to suit the intended specific application.

Claims

1. An agile development management method, characterized in that: include: In response to the data connection instruction, a full demand file of the user's demand is identified from the target IT management service system, and the full demand file is stored in a preset MySQL database; In response to the user's demand instruction, processing is performed in combination with the full demand file to obtain a processing result; Through data statistics and visualization, we try to determine whether the processing results are completed and obtain the agile development management monitoring results.

2. The method according to claim 1, characterized in that The step of identifying a full demand file of user demand from the target IT management service system and storing the full demand file in a preset MySQL database includes: Identify the requirement document type of the full requirement document of user requirements from the target IT management service system; Parsing the full demand file into structured data according to the demand file type; The parsed structured data is imported into the preset MySQL database, and the database records are automatically updated according to data changes.

3. The method according to claim 1, characterized in that The user demand instruction includes a priority sorting instruction, the full demand file includes development, review and production node information of the demand, and the response to the user demand instruction is combined with the full demand file to perform processing to obtain a processing result, including: In response to the priority sorting instruction, the target demand is prioritized to obtain the target priority of the target demand; The development, review and production node information corresponding to the target demand are updated according to the target priority.

4. The method according to claim 1, characterized in that: The user demand instruction includes a scheduling review instruction, the full demand file includes a review window, and the response to the user demand instruction is combined with the full demand file to perform processing to obtain a processing result, including: In response to the scheduling review instruction, creating a target review window for the target requirement and setting a date and status of the target review window; Associating the target requirement with the target review window, and adding the design document SVN path corresponding to the target requirement to the target review window; The review result of the target requirement in the target review window is updated to the preset MySQL database.

5. The method according to claim 1, characterized in that The user demand instruction includes a production scheduling instruction, the full quantity demand file includes a production window, and the response to the user demand instruction is combined with the full quantity demand file to perform processing to obtain a processing result, including: In response to the production scheduling instruction, a target production window is created according to the business requirements included in the production scheduling instruction; the business requirements include front-end packages, back-end system packages, client packages, data scripts and ESB packages; Add the target requirements that have passed the test to the target production window and set the production date; The production result of the target demand in the target production window is updated to the preset MySQL database.

6. The method according to claim 1, characterized in that The method attempts to determine whether the processing result is completed through data statistics and visualization, and obtains the agile development management monitoring result, including: Attempt to obtain the processing progress of the processing results through data statistics and visualization; Determine the processing efficiency according to the development requirements corresponding to the processing results; Whether the current progress is lagging behind is determined according to the processing progress and the preset progress requirement, and in the case of lagging behind, the progress is highlighted and displayed on the web page according to the severity level.

7. The method according to claim 1, characterized in that The method further comprises: In response to the new adding instruction, new management user or new development company information for the example system of the present invention is entered.

8. An agile development management device, characterized in that: include: The management module is used to respond to data docking instructions, identify the full requirement file of user needs from the target IT management service system, and store the full requirement file in a preset MySQL database; respond to user requirement instructions, process the full requirement file to obtain processing results; try to determine whether the processing results are completed through data statistics and visualization, and obtain agile development management monitoring results.

9. A computer device, characterized in that: The computer device comprises a processor and a non-volatile memory storing computer instructions. When the computer instructions are executed by the processor, the computer device executes the method according to any one of claims 1 to 7.

10. A readable storage medium, characterized in that: The readable storage medium includes a computer program, and when the computer program is executed, the computer device where the readable storage medium is located is controlled to execute the method according to any one of claims 1 to 7.

Images