Project progress tracking method and device, storage medium and electronic equipment
By acquiring and calculating project data, a visual requirements calendar is generated and sent automatically, solving the problem of low efficiency in existing requirements management tools, enabling real-time tracking and management of project progress, and providing intuitive information delivery and risk warning support.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- PING AN INT FINANCIAL LEASING CO LTD
- Filing Date
- 2026-01-23
- Publication Date
- 2026-05-01
AI Technical Summary
Existing requirements management tools require manual tracking and recording of the development, testing, and deployment timelines of requirements, which is inefficient and prone to omissions or errors, affecting project progress.
By acquiring project data, including requirement feature data, development user story data, and defect data, we calculate R&D progress indicators, testing progress indicators, and health indicators, and process them using visualization tools to generate a visual requirement calendar, which is then automatically sent to project personnel.
It provides an intuitive visual interface to ensure timely and efficient information delivery, enabling real-time tracking and management of project requirements, helping teams to fully grasp project dynamics, and effectively identify and warn of potential risks.
Smart Images
Figure CN121961489A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of software development requirements management technology, and can be applied to the fields of financial technology business and medical and health care elderly care business. In particular, it relates to a project progress tracking method, device, storage medium and electronic device. Background Technology
[0002] In software development and project management, requirements management is a crucial step in ensuring successful project implementation. Existing requirements management tools typically require manual tracking and recording of development, testing, and deployment timelines. This approach is not only inefficient but also prone to omissions or errors, impacting the overall project schedule. This application's project progress tracking method can be used for tracking the progress of a fintech business platform development project. This platform supports functions such as shopping, social networking, interactive games, and resource transfer, and includes features for applying for loans, credit cards, or purchasing insurance and financial products. This application's project progress tracking method can also be used for tracking the progress of a healthcare and elderly care business system. This system supports functions such as disease-assisted diagnosis, health management, and remote consultation. Summary of the Invention
[0003] In view of this, the present invention provides a project progress tracking method, apparatus, storage medium, and electronic device, the main purpose of which is to solve the problem of low efficiency in the current requirement management tools that rely on manual tracking and recording of the development, testing, and launch time nodes of requirements.
[0004] To address the aforementioned problems, this application provides a project progress tracking method, comprising: Obtain project data for projects to be tracked, including requirement feature data, development user story data, defect data, and test user story data; Based on the development user story data, the defect data, and the test user story data, progress indicators are calculated and processed to obtain development progress indicators, test progress indicators, and health indicators. The R&D progress indicators, testing progress indicators, and health indicators are visualized using preset visualization tools to obtain a visualized requirements calendar. Based on the account information of project personnel in the demand feature data, the visualized demand calendar is sent to the project personnel of the project to be tracked using a preset email template.
[0005] Optionally, obtaining project data for projects to be tracked specifically includes: Web crawling was used to extract data from the requirements management database to obtain requirements feature data; Data was extracted from the R&D management database using web crawling methods to obtain developer user story data and the aforementioned defect data; Data was extracted from the test management database using web crawling methods to obtain test user story data; The requirement feature data includes basic information and key attribute information. The basic information includes product manager information, development manager information, and test manager information. The key attribute information includes the planned test submission date, the actual test submission date, and the planned launch date. The user story data includes story ID, story title, story status, planned completion time, and completion rate; The defect data includes defect ID, severity, defect status, and defect manager; The test user story data includes test case ID, associated requirements, test results, and execution time.
[0006] Optionally, the step of calculating and processing progress indicators based on the development user story data, the defect data, and the test user story data to obtain development progress indicators, test progress indicators, and health indicators specifically includes: The development progress indicators are obtained by calculating and processing the actual development workload and the planned development workload in the development user story data. The test progress metrics are calculated and processed based on the actual test workload and test plan workload in the test user story data. Based on the planned test date, actual test date, planned launch date, and defect data in the demand characteristic data, a health index is obtained through calculation and processing.
[0007] Optionally, the health index is calculated based on the planned test date, the actual test date, the planned launch date, and the defect data in the demand characteristic data, specifically including: The number of days of test delay is calculated based on the planned test date and the actual test date. The number of days of launch delay risk is calculated based on the expected launch date and the planned launch date. Based on the defect data, a quality index is obtained through calculation and processing. The quality index includes the defect restart rate and the proportion of serious defects. Based on the number of days of test submission delay, the number of days of launch delay risk, and the quality indicators, a health index is obtained by comprehensively evaluating the health index using health rules.
[0008] Optionally, the health index is obtained by comprehensively evaluating the number of days of test submission delay, the number of days of launch delay risk, and the quality indicators using health rules, specifically including: Based on the number of days of test submission delay and the number of days of launch delay risk, progress health rules are used to evaluate and obtain progress health indicators. The quality and health indicators are obtained by evaluating the defect restart rate and the proportion of critical defects using quality and health rules. The health index is obtained by comprehensively evaluating the progress health index and the quality health index.
[0009] Optionally, sending the visualized requirements calendar to the project personnel of the project to be tracked based on the account information of the project personnel in the requirements feature data and using a preset email template specifically includes: The visualized demand calendar is written into the preset email template using a pre-defined reading tool to obtain an initial progress report; The initial progress report is converted to a new format to obtain the target progress report; Based on the account information of the project personnel in the demand feature data, the target progress report is encapsulated using a preset email encapsulation method to generate a target email; In response to the timer's trigger, the target email is sent to the project personnel of the project whose progress is to be tracked.
[0010] Optionally, the step of encapsulating the target progress report using a preset email encapsulation method based on the email address information of the project personnel in the demand feature data to generate a target email specifically includes: The preset communication tool is started using a preset scheduling method; Based on the account information of the project personnel and the organizational structure corresponding to the project personnel in the preset communication tool, the email addresses are concatenated to obtain the sequence of receiving email addresses; Based on the target progress report and the sequence of recipient email addresses, the email configuration is performed to obtain the target email.
[0011] To address the aforementioned problems, this application provides a project progress tracking device, comprising: The acquisition module is used to acquire project data for projects to be tracked, including requirement feature data, development user story data, defect data, and test user story data. The calculation module is used to perform progress indicator calculations based on the development user story data, the defect data, and the test user story data to obtain the development progress indicator, the test progress indicator, and the health indicator. The visualization processing module is used to visualize the R&D progress indicators, testing progress indicators and health indicators using preset visualization tools to obtain a visualized demand calendar. The sending module is used to send the visualized requirements calendar to the project personnel of the project to be tracked based on the account information of the project personnel in the requirements feature data and using a preset email template.
[0012] To address the aforementioned problems, this application provides a storage medium storing a computer program that, when executed by a processor, implements the steps of the project progress tracking method described above.
[0013] To address the aforementioned problems, this application provides an electronic device, comprising at least a memory and a processor, wherein the memory stores a computer program, and the processor, when executing the computer program in the memory, implements the steps of the project progress tracking method described above.
[0014] The beneficial effects of this application include: providing an intuitive visual interface that allows users to clearly view the entire lifecycle status of project requirements; employing an automated push mechanism to send project progress information to relevant personnel and leaders daily, ensuring timely and efficient information delivery; enabling real-time tracking and management of project requirements, helping the team to fully grasp project dynamics; and effectively identifying and warning of potential risks, providing strong support for decision-making.
[0015] The above description is merely an overview of the technical solution of the present invention. In order to better understand the technical means of the present invention and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of the present invention more apparent and understandable, specific embodiments of the present invention are described below. Attached Figure Description
[0016] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the invention. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings: Figure 1 This illustration shows an application environment diagram of a project progress tracking method provided in an embodiment of this application; Figure 2 A flowchart illustrating a project progress tracking method provided in an embodiment of this application is shown. Figure 3 A flowchart illustrating a project progress tracking method according to another embodiment of this application is shown; Figure 4A structural block diagram of a project progress tracking device according to another embodiment of this application is shown; Figure 5 A schematic diagram of the structure of a computer device according to an embodiment of this application is shown; Figure 6 Another structural schematic diagram of a computer device according to one embodiment of this application is shown. Detailed Implementation
[0017] Various embodiments and features of this application are described herein with reference to the accompanying drawings.
[0018] It should be understood that various modifications can be made to the embodiments described herein. Therefore, the above description should not be considered as limiting, but merely as an example of embodiments. Other modifications within the scope and spirit of this application will be apparent to those skilled in the art.
[0019] The accompanying drawings, which are included in and form part of this specification, illustrate embodiments of the present application and, together with the general description of the present application given above and the detailed description of the embodiments given below, serve to explain the principles of the present application.
[0020] These and other features of this application will become apparent from the following description of preferred forms of embodiments given as non-limiting examples, with reference to the accompanying drawings.
[0021] It should also be understood that although this application has been described with reference to some specific examples, those skilled in the art can certainly implement many other equivalent forms of this application.
[0022] The above and other aspects, features and advantages of this application will become more apparent when taken in conjunction with the accompanying drawings and in view of the following detailed description.
[0023] Specific embodiments of this application are described thereafter with reference to the accompanying drawings; however, it should be understood that the claimed embodiments are merely examples of this application, which can be implemented in various ways. Well-known and / or repeated functions and structures are not described in detail to avoid unnecessary or redundant details that could obscure the application. Therefore, the specific structural and functional details claimed herein are not intended to be limiting, but merely serve as the basis and representative basis for the claims to teach those skilled in the art to use this application in a variety of substantially any suitable detailed structures.
[0024] This specification may use the phrases “in one embodiment,” “in another embodiment,” “in yet another embodiment,” or “in other embodiments,” all of which may refer to one or more of the same or different embodiments according to this application.
[0025] The project progress tracking method provided in this application embodiment can be applied to, for example, Figure 1In this application environment, the client communicates with the server via a network. The server can obtain project data for projects under progress tracking, including requirement feature data, development user story data, defect data, and test user story data. Based on the development user story data, defect data, and test user story data, progress indicators are calculated to obtain development progress indicators, testing progress indicators, and health indicators. A preset visualization tool is used to visualize these indicators, resulting in a visualized requirement calendar. Based on the account information of project personnel in the requirement feature data, a preset email template is used to send the visualized requirement calendar to the project personnel of the projects under progress tracking. This application provides an intuitive visualization interface, allowing users to clearly view the entire lifecycle status of project requirements. An automated push mechanism is used to send project progress information to relevant personnel and leaders daily, ensuring timely and efficient information transmission. Real-time tracking and management of project requirements is achieved, helping the team to fully grasp project dynamics. Potential risks are effectively identified and warned of, providing strong support for decision-making.
[0026] This application provides a project progress tracking method, such as... Figure 2 As shown, it includes: Step S101: Obtain project data for the project to be tracked, including requirement feature data, development user story data, defect data, and test user story data; In this step, web crawling is used to extract data from the requirements management database to obtain requirements feature data; web crawling is also used to extract data from the R&D management database to obtain development user story data and defect data; and web crawling is used to extract data from the test management database to obtain test user story data. The requirements feature data includes basic information and key attribute information. The basic information includes product manager information, development lead information, and test lead information. The key attribute information includes the planned test submission date, the actual test submission date, and the planned launch date. The development user story data includes story ID, story title, story status, planned completion time, and completion percentage. The defect data includes defect ID, severity, defect status, and defect lead. The test user story data includes test case ID, associated requirements, test results, and execution time. The financial technology business platform can be an insurance system, a banking system, a trading system, or an order system. The acceptance criteria in the development user story data must clearly include compliance and security requirements to ensure data security.
[0027] Step S102: Based on the development user story data, the defect data, and the test user story data, calculate and process the progress indicators to obtain the R&D progress indicators, test progress indicators, and health indicators. In this step, the actual development workload and planned development workload in the development user story data are calculated to obtain the R&D progress index; the actual testing workload and planned testing workload in the testing user story data are calculated to obtain the testing progress index; and the planned test submission date, actual test submission date, planned launch date, and defect data in the requirement feature data are calculated to obtain the health index.
[0028] Step S103: Use a preset visualization tool to visualize the R&D progress indicators, testing progress indicators, and health indicators to obtain a visualized requirements calendar; In the specific implementation process of this step, the visualized requirement calendar can be generated using a preset chart library; or it can be generated using chart libraries such as HTML / CSS / JavaScript, ECharts, and Python's Matplotlib / Seaborn library. Gantt charts, progress bars, burn-down charts, and quality charts can be used to display R&D progress indicators, testing progress indicators, and health indicators.
[0029] Step S104: Based on the account information of the project personnel in the requirement feature data, the visualized requirement calendar is sent to the project personnel of the project to be tracked using a preset email template.
[0030] In this step, a pre-defined reading tool is used to write the visualized requirements calendar into the preset email template to obtain an initial progress report; the initial progress report is then format-converted to obtain a target progress report; based on the account information of the project personnel in the requirements feature data, the target progress report is encapsulated using a preset email encapsulation method to generate a target email; in response to the timer's trigger operation, the target email is sent to the project personnel of the project whose progress needs to be tracked.
[0031] This application acquires project data for projects under progress tracking, including requirement characteristic data, development user story data, defect data, and test user story data. Based on the development user story data, defect data, and test user story data, progress indicators are calculated to obtain development progress indicators, testing progress indicators, and health indicators. These indicators are then visualized using a pre-set visualization tool to create a visualized requirement calendar. An intuitive visualization interface is provided, allowing users to clearly view the entire lifecycle status of project requirements. Based on the account information of project personnel in the requirement characteristic data, the visualized requirement calendar is sent to the project personnel of the projects under progress tracking using a pre-set email template. An automated push mechanism is employed to send project progress information to relevant personnel and leaders daily, ensuring timely and efficient information transmission. This enables real-time tracking and management of project requirements, helping the team to fully grasp project dynamics. It also effectively identifies and warns of potential risks, providing strong support for decision-making.
[0032] Another embodiment of this application provides another method for project progress tracking, such as... Figure 3 As shown, it includes: Step S201: Obtain project data for the project to be tracked, including requirement feature data, development user story data, defect data, and test user story data; In this step, web crawling is used to extract data from the requirements management database to obtain requirements feature data; web crawling is also used to extract data from the R&D management database to obtain development user story data and defect data; and web crawling is used to extract data from the test management database to obtain test user story data. The requirements feature data includes basic information and key attribute information. The basic information includes product manager information, development lead information, and test lead information. The key attribute information includes the planned test submission date, the actual test submission date, and the planned launch date. The development user story data includes story ID, story title, story status, planned completion time, and completion percentage. The defect data includes defect ID, severity, defect status, and defect lead. The test user story data includes test case ID, associated requirements, test results, and execution time. Alternatively, interface verification can be used to obtain the project data by calling a preset interface. The project for which this application is pending progress tracking can be a medical cloud platform. A medical cloud refers to a cloud platform for healthcare services created using cloud computing, combining medical technology with new technologies such as cloud computing, mobile technology, multimedia, 4G communication, big data, and the Internet of Things. This enables the sharing of medical resources and expands the scope of medical services. Because of the application of cloud computing technology, the medical cloud improves the efficiency of medical institutions and facilitates access to medical care for residents. For example, current hospital appointment booking, electronic medical records, and medical insurance are all products of the integration of cloud computing and the medical field. The medical cloud also has advantages such as data security, information sharing, dynamic expansion, and a global deployment.
[0033] Step S202: Calculate and process the actual development workload and planned development workload in the development user story data to obtain the R&D progress indicators; In this step, the actual completed workload of each development user story in the same project to be tracked is added together to obtain the total actual completed workload; the planned workload of each development user story in the same project to be tracked is added together to obtain the total planned completed workload; and the total actual completed workload and the total planned completed workload are divided to obtain the R&D progress indicator.
[0034] Step S203: Calculate and process the actual test workload and test plan workload in the test user story data to obtain the test progress indicators; In this step, the actual completed workload of each test user story in the same project to be tracked is added together to obtain the total actual completed workload; the planned completed workload of each test user story in the same project to be tracked is added together to obtain the total planned completed workload; and the total actual completed workload and the total planned completed workload are divided to obtain the test progress index.
[0035] Step S204: Calculate the number of days of test delay based on the planned test date and the actual test date; In the specific implementation process, this step involves subtracting the actual test date from the planned test date to obtain the number of days of test delay.
[0036] Step S205: Calculate the number of days of launch delay risk based on the expected launch date and the planned launch date; In this step, the estimated launch date is subtracted from the planned launch date to obtain the number of days of launch delay risk. The estimated launch date can be estimated based on the current progress, and is the date when all test cases pass and there are no serious defects.
[0037] Step S206: Perform calculations based on the defect data to obtain quality indicators; In this step, the following steps are performed: First, the number of defects fixed by developers and marked as "resolved" or "closed" is calculated. Second, the number of defects from the first number that were retested by testers is calculated. Third, the defect restart rate is obtained by dividing the second number by the first number. The defect restart rate measures the effectiveness and first-time success rate of defect fixing. A third, the number of defects with a critical defect level from the first number is counted. A fourth, the number of defects with a severe defect level from the first number is counted. The defect levels include critical defects, severe defects, and minor defects. A fifth, the number of defects from the third and fourth numbers is added together. Finally, a fifth, the percentage of severe defects is divided by the first number. The percentage of severe defects indicates a significant risk in code quality or design.
[0038] Step S207: Based on the number of days of test submission delay, the number of days of launch delay risk, and the quality indicators, a comprehensive evaluation is conducted using health rules to obtain a health index; In this step, the progress health rules are used to evaluate the progress based on the number of days the test submission delay is delayed and the number of days the launch delay risk is risky, resulting in a progress health index. The delay risk level is then determined based on these two numbers. For example: if both the test submission delay and the launch delay risk are less than or equal to 2 days, the project's delay risk level is determined to be low-risk; if either the test submission delay or the launch delay risk is greater than or equal to 3 days and less than or equal to 5 days, the project's delay risk level is determined to be medium-risk; and if either the test submission delay or the launch delay risk is greater than 5 days, the project's delay risk level is determined to be high-risk.
[0039] The quality health index is obtained by evaluating the defect restart rate and the proportion of severe defects using quality health rules. Specifically, when the defect restart rate is greater than or equal to a first preset threshold, or the proportion of severe defects is greater than or equal to a second preset threshold, the quality health index of the project to be tracked is at a high-risk quality level. When the defect restart rate is greater than a third preset threshold and less than the first preset threshold, or the proportion of severe defects is greater than a third preset threshold and less than the first preset threshold, the quality health index of the project to be tracked is at a medium-risk quality level. When the defect restart rate is less than a third preset threshold or the proportion of severe defects is less than the third preset threshold, the quality health index of the project to be tracked is at a low-risk quality level.
[0040] The health index is obtained by comprehensively evaluating the progress health index and the quality health index. The higher risk level among the progress health index and the quality health index is determined as the comprehensive evaluation result of the project currently under progress tracking; for example, if the progress is at a high-risk progress level and the quality is at a low-risk quality level, then the health index is at a high-risk health risk level.
[0041] Step S208: Based on the account information of the project personnel in the requirement feature data, the visualized requirement calendar is sent to the project personnel of the project to be tracked using a preset email template.
[0042] In this step, a pre-defined reading tool is used to write the visualized requirements calendar into the pre-defined email template to obtain an initial progress report. This pre-defined reading tool can use the pandas and openpyxl libraries to write the visualized requirements calendar into the pre-defined email template to obtain the initial progress report. The initial progress report is then formatted to obtain a target progress report. The visualized requirements calendar is converted to HTML format to generate the target progress report. Based on the account information of the project personnel in the requirements feature data, a pre-defined email encapsulation method is used to encapsulate the target progress report, generating a target email. Specifically, a pre-defined scheduling method is used to start a pre-defined communication tool. This pre-defined scheduling method can be the win32.Dispatch scheduling method, and the pre-defined communication tool can be Outlook or a self-developed communication tool. Email addresses are concatenated based on the account information of the project personnel and the organizational structure corresponding to the project personnel in the pre-defined communication tool to obtain a sequence of recipient email addresses. Email configuration is performed based on the target progress report and the sequence of recipient email addresses to obtain the target email. Specifically, the recipients, CC leaders, subject, HTML body, and attachments are set to generate the target email. In response to a timer trigger, the target email is sent to the project personnel involved in the project requiring progress tracking. The Send() method is called to send the target email to the project personnel involved in the project requiring progress tracking.
[0043] This application provides an intuitive visual interface, allowing users to clearly view the entire lifecycle status of project requirements. An automated push mechanism delivers project progress information to relevant personnel and leaders daily, ensuring timely and efficient information transmission. It enables real-time tracking and management of project requirements, helping the team to fully grasp project dynamics. It effectively identifies and warns of potential risks, providing strong support for decision-making.
[0044] Another embodiment of this application provides a project progress tracking device, such as... Figure 4 As shown, it includes: Module 1 is used to acquire project data for projects to be tracked, including requirement feature data, development user story data, defect data, and test user story data. Calculation module 2 is used to perform progress indicator calculations based on the development user story data, the defect data, and the test user story data to obtain R&D progress indicators, test progress indicators, and health indicators. Visualization module 3 is used to visualize the R&D progress indicators, testing progress indicators and health indicators using preset visualization tools to obtain a visualized demand calendar. Sending module 4 is used to send the visualized requirements calendar to the project personnel of the project to be tracked based on the account information of the project personnel in the requirements feature data and using a preset email template.
[0045] In the specific implementation process, the acquisition module 1 is specifically used for: extracting data from the requirement management database using a web crawler to obtain requirement feature data; extracting data from the R&D management database using a web crawler to obtain development user story data and the defect data; and extracting data from the test management database using a web crawler to obtain test user story data. The requirement feature data includes basic information and key attribute information. The basic information includes product manager information, development lead information, and test lead information. The key attribute information includes the planned test submission date, the actual test submission date, and the planned launch date. The development user story data includes story ID, story title, story status, planned completion time, and completion percentage. The defect data includes defect ID, severity, defect status, and defect lead. The test user story data includes test case ID, associated requirement, test result, and execution time.
[0046] In the specific implementation process, the calculation module 2 is specifically used to: calculate and process the actual development workload and planned development workload in the development user story data to obtain the R&D progress index; calculate and process the actual testing workload and planned testing workload in the test user story data to obtain the test progress index; and calculate and process the planned test submission date, the actual test submission date, the planned launch date, and the defect data in the requirement feature data to obtain the health index.
[0047] In the specific implementation process, the calculation module 2 is also used to: calculate the number of days of test submission delay based on the planned test submission date and the actual test submission date; calculate the number of days of launch delay risk based on the expected launch date and the planned launch date; calculate the quality indicators based on the defect data, the quality indicators including the defect restart rate and the proportion of serious defects; and comprehensively evaluate the number of days of test submission delay, the number of days of launch delay risk, and the quality indicators using health rules to obtain health indicators.
[0048] In the specific implementation process, the calculation module 2 is also used to: evaluate the progress health index based on the number of days of test delay and the number of days of launch delay risk using progress health rules; evaluate the quality health index based on the defect restart rate and the proportion of serious defects using quality health rules; and conduct a comprehensive evaluation based on the progress health index and the quality health index to obtain the health index.
[0049] In the specific implementation process, the sending module 4 is specifically used to: use a predetermined reading tool to write the visual requirements calendar into the preset email template to obtain an initial progress report; convert the format of the initial progress report to obtain a target progress report; based on the account information of the project personnel in the requirements feature data, use a preset email encapsulation method to encapsulate the target progress report to generate a target email; and in response to the triggering operation of the timer, send the target email to the project personnel of the project to be tracked.
[0050] In the specific implementation process, the sending module 4 is also used to: start a preset communication tool using a preset scheduling method; perform email concatenation processing based on the account information of the project personnel and the organizational structure corresponding to the project personnel in the preset communication tool to obtain a sequence of receiving email addresses; and configure the email based on the target progress report and the sequence of receiving email addresses to obtain the target email.
[0051] This application provides an intuitive visual interface, allowing users to clearly view the entire lifecycle status of project requirements. An automated push mechanism delivers project progress information to relevant personnel and leaders daily, ensuring timely and efficient information transmission. It enables real-time tracking and management of project requirements, helping the team to fully grasp project dynamics. It effectively identifies and warns of potential risks, providing strong support for decision-making.
[0052] Another embodiment of this application provides a storage medium storing a computer program, which, when executed by a processor, implements the following method steps: Step 1: Obtain project data for the project to be tracked. The project data includes requirement feature data, development user story data, defect data, and test user story data. Step 2: Based on the development user story data, the defect data, and the test user story data, calculate and process the progress indicators to obtain the development progress indicators, test progress indicators, and health indicators. Step 3: Use a preset visualization tool to visualize the R&D progress indicators, testing progress indicators, and health indicators to obtain a visualized requirements calendar. Step 4: Based on the account information of the project personnel in the requirement feature data, send the visualized requirement calendar to the project personnel of the project to be tracked using a preset email template.
[0053] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.
[0054] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is used as an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.
[0055] The specific implementation process of the above method steps can be found in the embodiments of the above project progress tracking methods, which will not be repeated here.
[0056] This application provides an intuitive visual interface, allowing users to clearly view the entire lifecycle status of project requirements. An automated push mechanism delivers project progress information to relevant personnel and leaders daily, ensuring timely and efficient information transmission. It enables real-time tracking and management of project requirements, helping the team to fully grasp project dynamics. It effectively identifies and warns of potential risks, providing strong support for decision-making.
[0057] Another embodiment of this application provides an electronic device, which can be a server, and its internal structure is shown in the figure below. Figure 5As shown, the electronic device includes a processor, memory, network interface, and database connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile and / or volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The network interface is used to communicate with external clients via a network connection. When the processor executes the program, it implements the functions or steps of a project schedule tracking method on the server side.
[0058] In one embodiment, an electronic device is provided, which can be a client. Its internal structure is illustrated below. Figure 6 As shown, the electronic device includes a processor, memory, network interface, display screen, and input device connected via a system bus. The processor provides computing and control capabilities. The memory includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The network interface is used to communicate with an external server via a network connection. When the program is executed by the processor, it implements the functions or steps on the client side of a project progress tracking method.
[0059] Another embodiment of this application provides an electronic device, including at least a memory and a processor. The memory stores a computer program, and the processor, when executing the computer program in the memory, performs the following method steps: Step 1: Obtain project data for the project to be tracked. The project data includes requirement feature data, development user story data, defect data, and test user story data. Step 2: Based on the development user story data, the defect data, and the test user story data, calculate and process the progress indicators to obtain the development progress indicators, test progress indicators, and health indicators. Step 3: Use a preset visualization tool to visualize the R&D progress indicators, testing progress indicators, and health indicators to obtain a visualized requirements calendar. Step 4: Based on the account information of the project personnel in the requirement feature data, send the visualized requirement calendar to the project personnel of the project to be tracked using a preset email template.
[0060] The specific implementation process of the above method steps can be found in the embodiments of the above project progress tracking methods, which will not be repeated here.
[0061] This application provides an intuitive visual interface, allowing users to clearly view the entire lifecycle status of project requirements. An automated push mechanism delivers project progress information to relevant personnel and leaders daily, ensuring timely and efficient information transmission. It enables real-time tracking and management of project requirements, helping the team to fully grasp project dynamics. It effectively identifies and warns of potential risks, providing strong support for decision-making.
[0062] The above embodiments are merely exemplary embodiments of this application and are not intended to limit this application. The scope of protection of this application is defined by the claims. Those skilled in the art can make various modifications or equivalent substitutions to this application within its substance and scope of protection, and such modifications or equivalent substitutions should also be considered to fall within the scope of protection of this application.
Claims
1. A project progress tracking method, characterized in that, include: Obtain project data for projects to be tracked, including requirement feature data, development user story data, defect data, and test user story data; Based on the development user story data, the defect data, and the test user story data, progress indicators are calculated and processed to obtain development progress indicators, test progress indicators, and health indicators. The R&D progress indicators, testing progress indicators, and health indicators are visualized using preset visualization tools to obtain a visualized requirements calendar. Based on the account information of project personnel in the demand feature data, the visualized demand calendar is sent to the project personnel of the project to be tracked using a preset email template.
2. The method as described in claim 1, characterized in that, The acquisition of project data for projects awaiting progress tracking specifically includes: Web crawling was used to extract data from the requirements management database to obtain requirements feature data; Data was extracted from the R&D management database using web crawling methods to obtain developer user story data and the aforementioned defect data; Data was extracted from the test management database using web crawling methods to obtain test user story data; The requirement feature data includes basic information and key attribute information. The basic information includes product manager information, development manager information, and test manager information. The key attribute information includes the planned test submission date, the actual test submission date, and the planned launch date. The user story data includes story ID, story title, story status, planned completion time, and completion rate; The defect data includes defect ID, severity, defect status, and defect manager; The test user story data includes test case ID, associated requirements, test results, and execution time.
3. The method as described in claim 1, characterized in that, The process of calculating progress indicators based on the development user story data, the defect data, and the test user story data yields development progress indicators, test progress indicators, and health indicators, specifically including: The development progress indicators are obtained by calculating and processing the actual development workload and the planned development workload in the development user story data. The test progress metrics are calculated and processed based on the actual test workload and test plan workload in the test user story data. Based on the planned test date, actual test date, planned launch date, and defect data in the demand characteristic data, a health index is obtained through calculation and processing.
4. The method as described in claim 3, characterized in that, The health index is calculated and processed based on the planned test submission date, the actual test submission date, the planned launch date, and the defect data in the demand characteristic data, specifically including: The number of days of test delay is calculated based on the planned test date and the actual test date. The number of days of launch delay risk is calculated based on the expected launch date and the planned launch date. Based on the defect data, a quality index is obtained through calculation and processing. The quality index includes the defect restart rate and the proportion of serious defects. Based on the number of days of test submission delay, the number of days of launch delay risk, and the quality indicators, a health index is obtained by comprehensively evaluating the health index using health rules.
5. The method as described in claim 4, characterized in that, The health index is obtained by comprehensively evaluating the number of days of testing delay, the number of days of launch delay risk, and the quality indicators using health rules. Specifically, the health index includes: Based on the number of days of test submission delay and the number of days of launch delay risk, progress health rules are used to evaluate and obtain progress health indicators. The quality and health indicators are obtained by evaluating the defect restart rate and the proportion of critical defects using quality and health rules. The health index is obtained by comprehensively evaluating the progress health index and the quality health index.
6. The method as described in claim 1, characterized in that, The step of sending the visualized requirements calendar to the project personnel of the project to be tracked based on the account information of the project personnel in the requirements feature data and using a preset email template specifically includes: The visualized demand calendar is written into the preset email template using a pre-defined reading tool to obtain an initial progress report; The initial progress report is converted to a new format to obtain the target progress report; Based on the account information of the project personnel in the demand feature data, the target progress report is encapsulated using a preset email encapsulation method to generate a target email; In response to the timer's trigger, the target email is sent to the project personnel of the project whose progress is to be tracked.
7. The method as described in claim 6, characterized in that, The target progress report is encapsulated using a preset email encapsulation method based on the email address information of the project personnel in the demand feature data to generate a target email, specifically including: The preset communication tool is started using a preset scheduling method; Based on the account information of the project personnel and the organizational structure corresponding to the project personnel in the preset communication tool, the email addresses are concatenated to obtain the sequence of receiving email addresses; Based on the target progress report and the sequence of recipient email addresses, the email configuration is performed to obtain the target email.
8. A project progress tracking device, characterized in that, include: The acquisition module is used to acquire project data for projects to be tracked, including requirement feature data, development user story data, defect data, and test user story data. The calculation module is used to perform progress indicator calculations based on the development user story data, the defect data, and the test user story data to obtain the development progress indicator, the test progress indicator, and the health indicator. The visualization processing module is used to visualize the R&D progress indicators, testing progress indicators and health indicators using preset visualization tools to obtain a visualized demand calendar. The sending module is used to send the visualized requirements calendar to the project personnel of the project to be tracked based on the account information of the project personnel in the requirements feature data and using a preset email template.
9. A storage medium, characterized in that, The storage medium stores a computer program, which, when executed by a processor, implements the steps of the project progress tracking method according to any one of claims 1-7.
10. An electronic device, characterized in that, It includes at least a memory and a processor, wherein the memory stores a computer program, and the processor, when executing the computer program in the memory, implements the steps of the project progress tracking method according to any one of claims 1-7.