Demand management method, device and terminal

By setting requirements levels and categories on the office document sharing platform and classifying requirements, the problem of inefficient demand management in the existing technology is solved, and the requirements consistency and homologous requirements of cross-organization teams are achieved, saving time and learning costs .

CN119027061APending Publication Date: 2024-11-26PING AN TECH (SHENZHEN) CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411177404.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-26
Publication Date
2024-11-26

AI Technical Summary

Technical Problem

Existing online document tools only provide the basic capabilities of storing and sharing editing in demand management, and cannot classify the requirements in the system, resulting in poor system coordination efficiency, increasing team workload, and inefficient demand management.

Method used

By presetting the requirements levels and categories on the office document sharing platform, detecting the requirements entry instructions, obtaining the levels and categories of requirements to be entered, performing classification and hierarchical management, entering the requirements development stage, verifying and archiving, and counting quality progress indicators. .

Benefits of technology

Maximize the alignment of requirements consistency and demand homologous requirements for cross-organization teamwork, save time and learning costs due to multiple systems and tools, and improve the efficiency of demand management.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119027061A_ABST
    Figure CN119027061A_ABST
Patent Text Reader

Abstract

The invention discloses a demand management method and device and a terminal. The method comprises the following steps: setting the level and category of a demand in advance; detecting a demand input instruction, obtaining the level and category of a to-be-input demand, inputting the to-be-input demand into the office document sharing platform according to the level and category, and recording the to-be-input demand as a target demand; obtaining a confirmation result of the target demand, and if confirmation of the target demand is completed, entering a demand development stage; the development progress of the demand development stage is obtained, and if it is detected that the demand development stage is completed, the target demand is verified; and if the target demand is successfully verified, judging that the target demand is completed, and archiving the completed target demand according to the version. According to the embodiment of the invention, on the premise that the complexity is not introduced, the demand consistency and demand homology requirements of cross-organization team cooperation are aligned to the maximum extent. And industry, production and research have the same frequency and high efficiency, and time cost and learning cost caused by multiple systems and tools are saved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of financial technology, and in particular to a method, device and terminal for demand management. Background Art

[0002] With the development of the times and the continuous changes in market demand, enterprises' requirements for scientific and technological technologies and software systems are gradually increasing, and IT R&D capabilities are gradually transforming into the core competitiveness of enterprises. Improving the R&D capabilities and efficiency of enterprise IT departments and improving the response speed to market demand have become the core force for enterprises to improve their market competitiveness.

[0003] The software development industry is constantly developing, and the number of IT department personnel is increasing. In order to better manage the development team and work progress, the development team is usually divided according to the project or product. As the complexity of IT system architecture and business processes is also increasing, cross-team or cross-departmental collaboration often occurs, which has become a difficult problem for business system managers to allocate work and synchronize progress. In response to this problem, some tools for sharing and collaboration have emerged in the prior art, such as Tencent Docs, NetEase Cloud Notes, ONEs Wiki, etc., and well-known foreign software such as Atlassian's Confl uence. These shared editing tools have played a good role in the homology of demand management, reducing a lot of misunderstandings and development rework caused by the management of individual requirements.

[0004] Some existing team collaboration systems need to support an operating system with more than 2,000 human agents. The requirements involved are diverse and complex, and a set of clearly classified and easy-to-implement requirements management mechanisms is urgently needed as a guarantee. Existing online document tools only provide the basic capabilities of storing and sharing requirements, and are unable to classify the requirements in the system, resulting in poor system collaboration efficiency, increased team workload, and low efficiency in requirements management.

[0005] Therefore, the prior art still needs to be improved and developed. Summary of the invention

[0006] In view of the above-mentioned deficiencies in the prior art, the present invention provides a method, device and terminal for demand management, aiming to solve the problem that the online document tools in the prior art only provide the basic capabilities of storing and sharing requirements and are unable to classify the requirements in the system, thereby resulting in poor system collaboration efficiency, increased team workload, and inefficient demand management.

[0007] The technical solution of the present invention is as follows:

[0008] A first embodiment of the present invention provides a method for demand management, which is applied to an office document sharing platform. The method includes:

[0009] Set the level and category of requirements in advance;

[0010] Detecting a demand entry instruction, obtaining the level and category of the demand to be entered, and entering the demand to be entered into the office document sharing platform according to the level and category, and recording it as a target demand;

[0011] Obtain the confirmation result of the target demand. If the confirmation of the target demand has been completed, enter the demand development stage;

[0012] Obtaining the development progress of the demand development phase, and if it is detected that the demand development phase has been completed, verifying the target demand;

[0013] If the target requirement is successfully verified, it is determined that the target requirement has been completed, and the completed target requirement is archived according to the version.

[0014] Furthermore, after detecting the demand entry instruction, obtaining the level and category of the demand to be entered, entering the demand to be entered into the office document sharing platform according to the level and category, and recording it as the target demand, the method further includes:

[0015] Collect statistics on the quality progress indicators of the target requirements.

[0016] Furthermore, the pre-setting of the level and category of the requirements includes:

[0017] Requirements are divided into three levels in advance according to the workload, namely epic requirements, feature requirements and story requirements;

[0018] Categorize story-level requirements into business stories, technical stories, and defect stories in advance.

[0019] Further, the detecting of the demand input instruction, obtaining the level and category of the demand to be input, and inputting the demand to be input into the office document sharing platform according to the level and category, and recording it as the target demand, includes:

[0020] Preset the estimation expression;

[0021] Detecting a demand entry instruction, obtaining the level and category of the demand to be entered, estimating the demand according to the obtained level and category of the demand to be entered and a preset estimation expression, and obtaining an estimation result;

[0022] The estimation result is entered into the office document sharing platform according to a preset format and recorded as the target demand.

[0023] Furthermore, after entering the estimation result into the office document sharing platform in a preset format and recording it as a target demand, the method further includes:

[0024] If the estimated result is not entered into the office document sharing platform according to the preset format, the entered demand is recorded as the target demand, and it is determined that the current target demand is in the unestimated stage.

[0025] Furthermore, after detecting the demand entry instruction, obtaining the level and category of the demand to be entered, entering the demand to be entered into the office document sharing platform according to the level and category, and recording it as the target demand, the method further includes:

[0026] Obtain the granularity of the target requirements and limit the granularity of the requirements according to the length of the development iteration cycle.

[0027] Furthermore, the statistics of the quality progress indicators of the target requirements include:

[0028] Statistics are collected on the number of released versions, business story ratio, defect rate and average team rate of the target requirements.

[0029] Another embodiment of the present invention provides a demand management device, which is applied to an office document sharing platform, and the device includes:

[0030] Classification and grading setting module, used to set the level and category of requirements in advance;

[0031] A demand entry module, used for detecting a demand entry instruction, obtaining the level and category of the demand to be entered, and entering the demand to be entered into the office document sharing platform according to the level and category, and recording it as a target demand;

[0032] The demand confirmation module is used to obtain the confirmation result of the target demand. If the confirmation of the target demand is completed, the demand development stage is entered;

[0033] A requirement verification module is used to obtain the development progress of the requirement development phase, and if it is detected that the requirement development phase has been completed, the target requirement is verified;

[0034] The requirement classification module is used to determine that the target requirement has been completed if the target requirement is successfully verified, and to archive the completed target requirement according to the version.

[0035] Another embodiment of the present invention provides a terminal, the terminal comprising at least one processor; and

[0036] a memory communicatively connected to the at least one processor; wherein,

[0037] The memory stores instructions that can be executed by the at least one processor. The instructions are executed by the at least one processor so that the at least one processor can perform the above-mentioned demand management method.

[0038] Another embodiment of the present invention further provides a non-volatile computer-readable storage medium, wherein the non-volatile computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by one or more processors, the one or more processors can execute the above-mentioned demand management method.

[0039] Beneficial effect: The method of demand management in the embodiment of the present invention maximizes the alignment of demand consistency and demand homology requirements for cross-organizational team collaboration without introducing complexity. The industry, production and research are synchronized and efficient, saving time and learning costs caused by multiple systems and tools. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] The present invention will be further described below with reference to the accompanying drawings and embodiments, in which:

[0041] Figure 1 A flowchart of a preferred embodiment of a method for demand management of the present invention;

[0042] Figure 2 A schematic diagram of functional modules of a preferred embodiment of a demand management device of the present invention;

[0043] Figure 3 The figure is a schematic diagram of the hardware structure of a preferred embodiment of a terminal of the present invention. DETAILED DESCRIPTION

[0044] In order to make the purpose, technical solution and effect of the present invention clearer and more specific, the present invention is further described in detail below. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0045] The embodiments of the present invention are described below in conjunction with the accompanying drawings. Those skilled in the art will appreciate that, with the development of technology and the emergence of new scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0046] The terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequential order. It should be understood that the terms used in this way can be interchangeable under appropriate circumstances, which is merely a way of distinguishing the objects of the same attributes when describing them in the embodiments of the present application. Here, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, so that the process, method, system, product or equipment comprising a series of units need not be limited to those units, but may include other units that are not clearly listed or inherent to these processes, methods, products or equipment.

[0047] In view of the above problems, the present invention provides a method for demand management. Figure 1 , Figure 1 FIG. 1 is a flow chart of a preferred embodiment of a method for demand management of the present invention. Figure 1 As shown, it includes:

[0048] Step S100, pre-setting the level and category of the demand;

[0049] Step S200: Detecting a demand entry instruction, obtaining the level and category of the demand to be entered, and entering the demand to be entered into the office document sharing platform according to the level and category, and recording it as a target demand;

[0050] Step S300, obtaining the confirmation result of the target demand, if the confirmation of the target demand has been completed, entering the demand development stage;

[0051] Step S400: obtaining the development progress of the demand development phase, and if it is detected that the demand development phase has been completed, verifying the target demand;

[0052] Step S500: If the target requirement verification succeeds, it is determined that the target requirement has been completed, and the completed target requirement is archived according to the version.

[0053] During specific implementation, the method for demand management in the embodiment of the present invention is used to manage the demand in the office document sharing platform. The office document sharing platform in the embodiment of the present invention is a cloud document for real-time collaboration among multiple people, which creates a cloud office solution based on document collaboration for enterprises. It supports multiple types of online documents, tables, collection tables, and Markdown, and supports multiple people to edit and comment on the content at the same time. The team can use documents to efficiently and conveniently complete solution discussions, information synchronization, information sharing, data storage, knowledge precipitation and other tasks, covering the entire project process of project establishment, goal setting, progress tracking, and project review.

[0054] The office document sharing platform has the following features:

[0055] Information synchronization reduces docking. In the process of work execution, multi-party docking often consumes a lot of time and energy, thus delaying the progress of execution. Therefore, information synchronization is particularly important. The office document sharing platform can provide efficient solutions for version management and information synchronization of the solution. For example, in R&D management, the product manager, as the project leader, can collaborate with designers and R&D on the office document sharing platform to complete the communication and confirmation of the solution. After confirming the requirements, the designer can insert pictures or upload attachments to complete the online design review with the team. All requirements and designs will automatically save historical versions, support viewing and comparison at any time, and can be restored with one click. R&D engineers can follow the document with one click to obtain update notifications of requirements and designs and achieve information synchronization. The office document sharing platform does not require face-to-face communication or storage of N final versions, which realizes the efficient contact and accumulation of information in the team.

[0056] Data storage and backup are also one of the factors that affect the efficiency of online collaborative office. Sometimes when you change computers, data files need to be copied again. Special circumstances such as power outages and computer freezes and restarts can also cause content loss. With an office document sharing platform, you can open a web page to write, without downloading and installing, and view and edit anytime, anywhere; documents are saved in the cloud in real time, transcending the limitations of time, space and physical carriers, and say goodbye to the trouble of data loss.

[0057] Optimize daily management. In terms of team management, the office document sharing platform can also play a role, allowing leaders to timely understand the work progress of team members through the daily reports updated by team members and the staged work lists, better supervise the progress of work, and effectively manage the team.

[0058] The embodiment of the present invention specifically grades and classifies the initial requirements in advance according to the workload and characteristics of the requirements. Specifically, the requirements can be divided into two or more categories, and the workload of different categories is different. Then, the minimum workload corresponding level is further classified according to the functions and defects of the story, so that the staff of the platform using it can quickly obtain the summary information of the requirements and improve the collaboration efficiency.

[0059] After setting the level and category of the demand, start entering the demand into the office document sharing platform. The user can trigger the demand entry instruction through the demand entry button of the office document sharing platform. Detect the demand entry instruction, obtain the demand to be entered, obtain the level and category information corresponding to the demand to be entered, enter the level and category information of the demand into the office document sharing platform, and record the entered demand as the target demand;

[0060] After the requirements are entered into the office document sharing platform, the requirements confirmation phase begins. This is usually done through the confirmation results of the salesperson. The salesperson's confirmation results for the requirements are obtained; corresponding operations are performed based on the confirmation results; when confirming the requirements, the salesperson must be able to explain and respond to the requirements at any time. In the iteration, the business needs to keep the instant chat tool in the office document sharing platform online to respond to development and product issues at any time.

[0061] If the salesperson confirms that it is completed, the process will enter the demand development stage. If the business has not confirmed that it is completed, the process will continue to wait for the salesperson's confirmation until the salesperson confirms that it is completed, and then enter the demand development stage.

[0062] Get the development progress of the demand development phase. If it is detected that the demand development phase has been completed, enter the business verification phase to verify the target demand. The developed demand requires business UAT testing, and the business can select a percentage to determine the completion. Get the demand completion degree. If the demand completion degree meets the preset conditions, the target demand verification is determined to be successful. The preset condition can be that the completion degree is greater than a certain ratio threshold. Preferably, the ratio threshold can be selected as 60%.

[0063] UAT testing, the full name of which is User Acceptance Testing, is a key stage in the system development life cycle methodology. In this stage, relevant users or independent testers test and accept the system according to the test plan and results to decide whether to accept the system.

[0064] UAT testing is an important testing task in the software development process, which aims to verify whether the software meets user needs and ensure that the software functions and performs well in the user environment. Through UAT testing, it can ensure that the software's functions, performance and user experience meet user expectations, and improve software stability and user satisfaction.

[0065] The main features of UAT testing are as follows:

[0066] User participation: UAT testing emphasizes user participation, requires users to participate in the testing process, and obtains user approval of the software. Destructive testing: Encourage users to design and conduct destructive testing to fully expose system design and functional problems. Requirements verification: UAT testing is also an important verification of whether the software meets user requirements. It confirms whether the software functions meet user requirements by simulating actual user operations.

[0067] The main steps of UAT testing are:

[0068] Development of test strategy: Develop appropriate test strategy based on the actual situation of the test object and testers. Determination of test users: Select representative users from the trainees as testers to ensure the comprehensiveness and accuracy of the test results. Preparation of test environment: Build a test environment with the same hardware, operating system, network environment, etc. as the end user to simulate the real user environment. Creation of test cases: Create detailed test cases covering all important functions based on the functions of the software and user needs. Execution of tests: Execute tests according to the test cases, record and track all problems found, and classify them according to the severity and priority of the problems. Collection of user feedback: During the testing process, users are encouraged to provide feedback, and these feedbacks are analyzed and processed in a timely manner. Problem fixing and iterative testing: Fix the problems found, and conduct iterative testing to ensure that all problems are effectively resolved. Result report: After the test is completed, a detailed test report is generated, including the test objectives, problems found, solutions, and user feedback.

[0069] UAT testing can achieve: Improve user experience: Through UAT testing, problems that may exist in the actual use of the software can be fully exposed, such as complex operations, unfriendly interfaces, slow responses, etc., thereby improving user experience. Discover potential problems in advance: UAT testing can discover problems that will only appear in the late stages of development or after going online, so that these problems can be fixed before they affect users and avoid losses. Verify that requirements are met: UAT testing is an important verification of whether the software meets user requirements.

[0070] If the target requirement is successfully verified, the target requirement is determined to be completed, and the completed target requirement is classified according to version.

[0071] The embodiment of the present invention maximizes the alignment of the requirements consistency and homology requirements of cross-organizational teamwork without introducing complexity. The industry, production and research are synchronized and efficient, saving time and learning costs caused by multiple systems and tools (requirements management, document management, work item management, test management, project management).

[0072] In one embodiment, after detecting a demand entry instruction, obtaining the level and category of the demand to be entered, entering the demand to be entered into the office document sharing platform according to the level and category, and recording it as a target demand, the process further includes:

[0073] Collect statistics on the quality progress indicators of the target requirements.

[0074] During the specific implementation, statistics can be collected based on the published target requirements, and the statistical content is mainly quality progress indicators. Quality progress indicators include but are not limited to development process versions, development speed, defects and other data.

[0075] In one embodiment, the level and category of the requirements are set in advance, including:

[0076] Requirements are divided into three levels in advance according to the workload, namely epic requirements, feature requirements and story requirements;

[0077] Categorize story-level requirements into business stories, technical stories, and defect stories in advance.

[0078] During the specific implementation, the requirements are graded and classified in advance, and the requirements are divided into three levels: epic / feature / story according to the workload. Among them, epic: epic crosses iterations and teams, and the workload is generally more than 20 man-days. Generally, a top-level requirement proposed by a business leader is an epic; epic cross-iteration usually refers to a complex and large-scale business requirement that cannot be completed in one or a few iterations. It has the characteristics of cross-iteration, that is, it needs to cross multiple iterations to be gradually completed. Epic is usually broken down into multiple smaller, independently deliverable units, namely UserStories. These User Stories will be assigned and completed in different iterations to gradually realize the complex business requirements represented by the Epic. The development team will use agile management tools (such as J IRA, Trello, etc.) to track and manage the progress of the Epic. After each iteration, the team will evaluate the completed User Stories and plan the work of the next iteration.

[0079] Since the business requirements involved in Epic are complex and large, it usually requires multiple development teams to work together to complete them. These teams may focus on different technology stacks, business areas or functional modules. In order to achieve cross-team collaboration, effective communication mechanisms and collaboration processes need to be established between development teams. This may include regular stand-up meetings, review meetings, planning meetings, etc. to ensure information synchronization and coordination between teams. There may be dependencies between different User Stories or functional modules, which requires the team to pay attention to coordination and integration during the development process. The development team needs to ensure that each functional module can be integrated and tested according to the predetermined schedule and quality standards.

[0080] Features: single feature iteration or single development team, the general workload is about 10-20 man-days. Feature single iteration development refers to taking the functional features (Feature) of the software as the iteration goal in the agile development or iterative development process, and each iteration cycle focuses on implementing, testing and delivering these functional features. Functional features include: Focus: Each iteration cycle revolves around specific functional features to ensure that the team can concentrate on completing these tasks. Deliverable: At the end of each iteration cycle, there should be deliverable results, that is, functional features that are completed and tested. Flexibility: If a functional feature encounters insurmountable obstacles during the iteration process, the team can flexibly adjust the plan to ensure the smooth delivery of other functional features.

[0081] Feature single-iteration development implementation steps: Requirements analysis and planning:

[0082] Before the iteration begins, the team needs to conduct a detailed requirements analysis of the functional features to be implemented, clarify the specific requirements, expected effects and possible constraints of the functions. Based on the results of the requirements analysis, a detailed iteration plan is formulated, including task allocation, time nodes, milestones, etc.

[0083] Design and development: According to the iteration plan, team members start design work, including architecture design, interface design, database design, etc. After the design is completed, it enters the development phase and implements coding according to the design documents.

[0084] Testing and verification: During the development process, team members need to continuously perform unit testing, integration testing, etc. to ensure the quality and stability of the code. At the end of the iteration cycle, comprehensive testing and verification are performed to ensure that the functional features meet the requirements of the requirements specification.

[0085] Delivery and feedback: Deliver the completed and tested features to users or test teams for acceptance. Collect feedback from users or test teams, and fix and optimize existing problems.

[0086] Story: A single team completes a story in an iteration, and the workload is generally within 10 man-days. Story (user story) is a method of describing user needs concisely, usually consisting of a single sentence, which includes the user's role, expectations and value. It describes the functions that are valuable to users, systems or software buyers, and is the basic unit for capturing and communicating requirements in the agile development process. It emphasizes dialogue rather than documents to ensure that all relevant personnel can understand. The size is suitable for planning and encourages postponing consideration of details, that is, stories can also be iterated. It consists of three parts: Card, Conversation, and Test, commonly known as "3C".

[0087] Iteration is a period of repeated cycles in the software development process, usually one to four weeks. During each iteration, the team completes a series of user stories or features and conducts testing, evaluation, and feedback.

[0088] Relationship with Story:

[0089] Before the start of an iteration, the team will select high-priority stories from the product backlog as the goals of this iteration. These stories will be further broken down into smaller tasks and assigned to team members for development. During the iteration process, the team will continue to write code, test, integrate, and provide feedback to ensure that each story can be completed on time and meet quality requirements.

[0090] The process of Story iteration is as follows:

[0091] Requirements collection and organization: Product managers or related personnel collect and organize user requirements and convert them into user stories.

[0092] Planning meeting: A planning meeting is held, and the team determines the development priority based on the importance of the requirements and the development volume, and makes a workload estimate. High-priority stories are selected from the product backlog as the goals of this iteration.

[0093] Task allocation and refinement: Break down the story into smaller tasks and assign them to team members for development. The workload of each task should be controlled within an appropriate range for easy management and tracking.

[0094] Development and testing: Team members carry out code writing, testing, integration and other tasks according to the plan.

[0095] During the iteration process, the team will continuously provide feedback and make adjustments to ensure that each Story is completed on time and meets quality requirements.

[0096] Review and delivery: At the end of an iteration, a review meeting (also called a demonstration meeting or review meeting) is held to showcase and verify the results of the iteration. If the review passes, the functional increment completed in the iteration is delivered to the user or the test team for acceptance.

[0097] Feedback and Improvement: Collect feedback from users or test teams, fix and optimize existing problems, and adjust subsequent iteration plans and strategies based on feedback results to continuously improve product quality and development efficiency.

[0098] In summary, Story iteration is an integral part of the agile development process. Through continuous iteration and feedback loops, the team can gradually deliver high-quality software products and meet user needs.

[0099] The granules of story-level requirements are classified into: business stories, technical stories and defect stories. Business stories are direct functions that can be perceived by the business, such as a function of sending emails by clicking one button. Business stories focus on describing the goals and value propositions of products or services from a business perspective, as well as how they meet user needs or solve business problems. Such stories are usually closely linked to product vision, market positioning, user needs and business goals. Business stories not only focus on technical implementation, but more importantly, understand why this product or function should be made, how it helps the company achieve its business goals, and how to improve user experience or solve user pain points.

[0100] Example: "In order to increase user retention, we need to develop a personalized recommendation system that can recommend relevant content in real time based on the user's historical behavior and preferences, thereby improving user satisfaction and loyalty."

[0101] Technical stories: functions that the business cannot directly perceive, such as some technical pre-research work or functions added for security / compliance, such as back-end encrypted storage. Technical stories focus on describing how to build, test, deploy and maintain various parts of the software system from the perspective of technical implementation. These stories are usually closely related to architecture design, performance optimization, code refactoring, technology selection, etc. Technical stories focus on ensuring the high availability, scalability, security and maintainability of the system. The technical team ensures that all technical decisions support business goals and solve technical challenges by telling these stories. Example: "In order to implement an efficient caching strategy, we need to design a distributed caching system based on Redis, which will be able to reduce the number of database accesses, improve system response speed, and have automatic failure and failover mechanisms."

[0102] Defect stories: Production defects found during operation are recorded as defect stories and sorted together with other stories. Defect stories focus on problems or errors found during software development and testing. These stories describe the specific manifestations of the defects, steps to reproduce, scope of impact, and fixes. Defect stories are a bridge of communication between the quality assurance team and the development team. They help the team understand the problems and collaborate to solve them. Defect stories are also an important source of data for continuous improvement of product quality and processes. Example: "In the user registration process, when the user enters an email address that does not meet the specifications, the system does not give a clear error prompt, resulting in the user being unable to complete the registration. This problem needs to be fixed to ensure that when the user enters an invalid email address, a clear error message is displayed and the user is guided on how to enter the correct email address."

[0103] In one embodiment, a demand entry instruction is detected, the level and category of the demand to be entered are obtained, and the demand to be entered is entered into the office document sharing platform according to the level and category, and recorded as a target demand, including:

[0104] Preset the estimation expression;

[0105] Detecting a demand entry instruction, obtaining the level and category of the demand to be entered, estimating the demand according to the obtained level and category of the demand to be entered and a preset estimation expression, and obtaining an estimation result;

[0106] The estimation result is entered into the office document sharing platform according to a preset format and recorded as the target demand.

[0107] During the specific implementation, the demand assessment is conducted in the project in the form of regularly scheduled meetings, with the architect making an initial estimate, combined with the team members' open and transparent workload assessment and main considerations.

[0108] Detect the requirement entry instruction, obtain the level and category of the requirement to be entered, estimate the requirement based on the level and category of the requirement to be entered and the preset estimation expression, obtain the estimation result, enter the estimated result into the office document sharing platform according to the preset title format and content format, and record it as the target requirement. For example: Establish an estimation expression system during evaluation: During the requirement entry and evaluation stage, uniformly require the evaluation of the working hours of the requirement title format in the form of (front-end workload + back-end workload + testing workload). The evaluation is a manual evaluation, and the regular expression matching calculation and summation are performed in the office document sharing platform. Among them, in software development projects, the front-end workload, back-end workload and testing workload are important parts of the entire project workload. The size of these workloads depends on multiple factors, including the complexity of the project, functional requirements, technology stack, development cycle, and the experience and capabilities of the team.

[0109] The front-end workload mainly involves the design and implementation of the user interface (UI) and user experience (UX). This includes: Page layout and design: Based on the design draft or prototype, use technology stacks such as HTML, CSS, and JavaScript to build the structure and style of the page. Interaction logic implementation: Implement the interactive logic of the page, such as button clicks, form submissions, data display, etc., through JavaScript or front-end frameworks (such as React, Vue, and Anglar). Performance optimization: Optimize the front-end code by compressing, merging, lazy loading, etc. to improve page loading speed and user experience. Responsive design: Ensure that the website or application can display and work well on different devices and screen sizes. Third-party integration: Integrate third-party services such as payment systems, social media sharing, and map services.

[0110] The back-end workload mainly focuses on server-side logic, database management and API interface development. This includes: Server configuration and deployment: configure the server environment, install necessary software and services, such as web servers, database servers, etc. API interface development: design and implement interfaces such as RESTful API or GraphQL for front-end or other system calls. Business logic implementation: implement complex business logic on the back-end according to business needs, such as user authentication, data validation, data processing, etc. Database design and optimization: design database architecture, write SQL statements or ORM queries, and optimize database performance. Security considerations: implement data encryption, prevent SQL injection, cross-site scripting attacks and other security measures.

[0111] The testing workload involves testing the front-end, back-end, and the entire system to ensure the quality and stability of the software. This includes: Unit testing: Testing individual modules or functions to ensure their correctness. Integration testing: Testing whether the interaction and collaboration between different modules work as expected. System testing: Testing the entire system, including functional testing, performance testing, security testing, etc. Compatibility testing: Testing the compatibility of the software on different browsers, operating systems, and devices. Regression testing: After each update or fix, re-execute previous tests to ensure that no new problems have been introduced.

[0112] In one embodiment, after the estimation result is entered into the office document sharing platform in a preset format and recorded as a target demand, the method further includes:

[0113] If the estimated result is not entered into the office document sharing platform according to the preset format, the entered demand is recorded as the target demand, and it is determined that the current target demand is in the unestimated stage.

[0114] In specific implementation, if the estimated result does not have a title filled in according to the standard, it is considered to be in the unestimated stage. In this way, the business / product can split, refine, discard, add and other operations on the demand pool anytime and anywhere (the estimated expression needs to be deleted). Similarly, the development team can also estimate the current demand at any time. Because on a platform, this informal interaction can happen at any time, and there is no need to arrange a special meeting.

[0115] In one embodiment, after detecting a demand entry instruction, obtaining the level and category of the demand to be entered, entering the demand to be entered into the office document sharing platform according to the level and category, and recording it as a target demand, the process further includes:

[0116] Obtain the granularity of the target requirements and limit the granularity of the requirements according to the length of the development iteration cycle.

[0117] During the specific implementation, the granularity of requirements is restricted according to the length of the development iteration cycle. Due to some national holidays, the release time window will change, resulting in rhythm adjustment. It is necessary to dynamically adjust the granularity of stories that can enter the iteration (a two-week iteration is 10 working days - 2 days of meeting time). In this way, the project team can flexibly judge the status of requirement confirmation and verification based on the latest situation, and determine whether additional requirement combing needs to be arranged based on the team rate and iteration time.

[0118] The restriction method is to set the iteration duration in the office document sharing platform. For example, if it is set to 10, then all stories with an estimated workload of more than 8 cannot be included in the iteration, which needs to be further refined. This part of the restriction is achieved by filtering and calculating statistics in the small tool interface of the office document sharing platform.

[0119] In one embodiment, statistics are collected on the quality progress indicators of the target requirements, including:

[0120] Statistics are collected on the number of released versions, business story ratio, defect rate and average team rate of the target requirements.

[0121] During the specific implementation, statistics can be collected on the published target requirements. The main quality progress indicators include business story ratio, defect rate, and team average rate. Business story ratio: the percentage of business story points in the overall story. Defect rate: the percentage of defective work in the overall story development. Team average rate: the overall number of delivered story points / iterations.

[0122] Among them, delivered points: the sum of all archived story points; iteration number: a special term in agile, a small cycle from requirements to test delivery with a fixed period, usually 2-4 weeks, 2 weeks in this case, tool support changes.

[0123] Overall story: the sum of all story points; Defect work: the sum of the story points of defect stories.

[0124] Compared with the prior art, the method for demand management in the embodiment of the present invention sets the level and category of the demand in advance; detects the demand entry instruction, obtains the level and category of the demand to be entered, enters the demand to be entered into the office document sharing platform according to the level and category, and records it as the target demand; obtains the confirmation result of the target demand, and if the confirmation of the target demand has been completed, enters the demand development stage; obtains the development progress of the demand development stage, and if it is detected that the demand development stage has been completed, verifies the target demand; if the target demand verification is successful, it is determined that the target demand has been completed, and the completed target demand is archived according to the version. It realizes the maximum alignment of the demand consistency and demand homology requirements of cross-organization team cooperation without introducing complexity. The industry, production and research are in the same frequency and efficient, saving the time cost and learning cost caused by multiple systems and tools (requirement management, document management, work item management, test management, project management). Without introducing task management, a single office document sharing platform is realized to connect industry, production and research, and the process is standardized through lightweight automation tools, achieving a balance between efficiency and effectiveness.

[0125] It should be noted that there is not necessarily a certain order between the above-mentioned steps. A person skilled in the art can understand, based on the description of the embodiments of the present invention, that in different embodiments, the above-mentioned steps may have different execution orders, that is, they may be executed in parallel, may be executed interchangeably, and so on.

[0126] Another embodiment of the present invention provides a demand management device, which is applied to an office document sharing platform, such as Figure 2 As shown, the device 1 comprises:

[0127] The classification and grading setting module 11 is used to set the level and category of the requirements in advance;

[0128] The demand entry module 12 is used to detect a demand entry instruction, obtain the level and category of the demand to be entered, and enter the demand to be entered into the office document sharing platform according to the level and category, and record it as a target demand;

[0129] The demand confirmation module 13 is used to obtain the confirmation result of the target demand. If the confirmation of the target demand is completed, the demand development stage is entered;

[0130] The requirement verification module 14 is used to obtain the development progress of the requirement development phase, and if it is detected that the requirement development phase has been completed, the target requirement is verified;

[0131] The requirement classification module 15 is used to determine that the target requirement has been completed if the target requirement verification is successful, and archive the completed target requirement according to the version.

[0132] The specific implementation method is shown in the method embodiment, which will not be described in detail here.

[0133] In one embodiment, the apparatus further comprises a statistical module, the statistical module being configured to:

[0134] Collect statistics on the quality progress indicators of the target requirements.

[0135] The specific implementation method is shown in the method embodiment, which will not be described in detail here.

[0136] In one embodiment, the classification and grading setting module 11 is specifically used for:

[0137] Requirements are divided into three levels in advance according to the workload, namely epic requirements, feature requirements and story requirements;

[0138] Categorize story-level requirements into business stories, technical stories, and defect stories in advance.

[0139] The specific implementation method is shown in the method embodiment, which will not be described in detail here.

[0140] In one embodiment, the demand entry module 12 is specifically used for:

[0141] Preset the estimation expression;

[0142] Detecting a demand entry instruction, obtaining the level and category of the demand to be entered, estimating the demand according to the obtained level and category of the demand to be entered and a preset estimation expression, and obtaining an estimation result;

[0143] The estimation result is entered into the office document sharing platform according to a preset format and recorded as the target demand.

[0144] The specific implementation method is shown in the method embodiment, which will not be described in detail here.

[0145] In one embodiment, the demand entry module 12 is further used to:

[0146] If the estimated result is not entered into the office document sharing platform according to the preset format, the entered demand is recorded as the target demand, and it is determined that the current target demand is in the unestimated stage.

[0147] The specific implementation method is shown in the method embodiment, which will not be described in detail here.

[0148] In one embodiment, the device further includes a demand granularity limiting module, the demand granularity limiting module is used to:

[0149] Obtain the granularity of the target requirements and limit the granularity of the requirements according to the length of the development iteration cycle.

[0150] The specific implementation method is shown in the method embodiment, which will not be described in detail here.

[0151] In one embodiment, the statistics module is further configured to:

[0152] Statistics are collected on the number of released versions, business story ratio, defect rate and average team rate of the target requirements.

[0153] The specific implementation method is shown in the method embodiment, which will not be described in detail here.

[0154] Another embodiment of the present invention provides a terminal. The terminal in the present application can be a mobile phone, a tablet computer, a wearable device, a vehicle-mounted device, an augmented reality (AR) / virtual reality (VR) device, a laptop computer, an ultra-mobile personal computer (UMPC), a netbook, a personal digital assistant (PDA), etc., and the embodiment of the present application does not impose any restrictions on this.

[0155] like Figure 3 As shown, the terminal 10 includes:

[0156] One or more processors 110 and memory 120, Figure 3 A processor 110 is used as an example for description. The processor 110 and the memory 120 may be connected via a bus or other means. Figure 3 The example of connecting through bus is taken in the following.

[0157] The processor 110 is used to complete various control logics of the terminal 10, and it can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), a single-chip microcomputer, an ARM (Acorn RISC Machine) or other programmable logic device, a discrete gate or transistor logic, a discrete hardware control, or any combination of these components. In addition, the processor 110 can also be any traditional processor, microprocessor or state machine. The processor 110 can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration.

[0158] The memory 120 is a non-volatile computer-readable storage medium that can be used to store non-volatile software programs, non-volatile computer executable programs and modules, such as program instructions corresponding to the method for demand management in the embodiment of the present invention. The processor 110 executes various functional applications and data processing of the device 10 by running the non-volatile software programs, instructions and units stored in the memory 120, that is, implementing the method for demand management in the above method embodiment.

[0159] The memory 120 may include a program storage area and a data storage area, wherein the program storage area may store applications required for operating the device and at least one function; the data storage area may store data created according to the use of the device 10, etc. In addition, the memory 120 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some embodiments, the memory 120 may optionally include a memory remotely arranged relative to the processor 110, and these remote memories may be connected to the device 10 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0160] One or more units are stored in the memory 120, and when executed by one or more processors 110, the method of demand management in any of the above method embodiments is executed, for example, the method described above is executed. Figure 1 The method comprises steps S100 to S500.

[0161] An embodiment of the present invention provides a non-volatile computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are executed by one or more processors, for example, to execute the above-described Figure 1 The method comprises steps S100 to S500.

[0162] As an example, non-volatile storage media can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) as external cache memory. By way of illustration and not limitation, RAM can be obtained in many forms such as synchronous RAM (SRAM), dynamic RAM, (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synch link DRAM (SLDRAM), and direct Rambus RAM (DRRAM). The disclosed memory controls or memories of the operating environment described herein are intended to include one or more of these and / or any other suitable types of memory.

[0163] Another embodiment of the present invention provides a computer program product, the computer program product includes a computer program stored on a non-volatile computer-readable storage medium, the computer program includes program instructions, when the program instructions are executed by a processor, the processor executes the method of demand management of the above method embodiment. Figure 1 The method comprises steps S100 to S500.

[0164] The embodiments described above are merely illustrative, in which the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0165] Through the description of the above embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus a general hardware platform, and of course can also be implemented by hardware. Based on this understanding, the above technical solution is essentially or the part that contributes to the relevant technology can be embodied in the form of a software product, and the computer software product can exist in a computer-readable storage medium, such as ROM / RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods of each embodiment or some parts of the embodiment.

[0166] Conditional language such as "can," "can," "might," or "may," among other things, unless specifically stated otherwise or otherwise understood within the context as used, is generally intended to convey that particular embodiments can include (while other embodiments do not) particular features, elements, and / or operations. Thus, such conditional language is also generally intended to imply that features, elements, and / or operations are anyway required for one or more embodiments or that one or more embodiments must include logic for determining, with or without input or prompting, whether such features, elements, and / or operations are included or will be performed in any particular embodiment.

[0167] What has been described herein in this specification and the accompanying drawings includes examples of methods and apparatus that can provide demand management. Of course, it is not possible to describe every conceivable combination of elements and / or methods for the purpose of describing the various features of the present disclosure, but it is recognized that many additional combinations and permutations of the disclosed features are possible. Therefore, it is apparent that various modifications can be made to the present disclosure without departing from the scope or spirit of the present disclosure. In addition, or in the alternative, other embodiments of the present disclosure may be apparent from consideration of the present specification and the accompanying drawings and from the practice of the present disclosure as presented herein. It is intended that the examples set forth in this specification and the accompanying drawings be considered in all respects to be illustrative and not restrictive. Although specific terms are employed herein, they are used in a general and descriptive sense and are not used for limiting purposes.

Claims

1. A method of demand management, characterized in that ,applied to an office document sharing platform, the method comprises: Set the level and category of requirements in advance; Detecting a demand entry instruction, obtaining the level and category of the demand to be entered, and entering the demand to be entered into the office document sharing platform according to the level and category, and recording it as a target demand; Obtain the confirmation result of the target demand. If the confirmation of the target demand has been completed, enter the demand development stage; Obtaining the development progress of the demand development phase, and if it is detected that the demand development phase has been completed, verifying the target demand; If the target requirement is successfully verified, it is determined that the target requirement has been completed, and the completed target requirement is archived according to the version.

2. The method according to claim 1, characterized in that After detecting the demand entry instruction, obtaining the level and category of the demand to be entered, entering the demand to be entered into the office document sharing platform according to the level and category, and recording it as the target demand, the method further includes: Collect statistics on the quality progress indicators of the target requirements.

3. The method according to claim 2, characterized in that The pre-setting of the level and category of the requirements includes: Requirements are divided into three levels in advance according to the workload, namely epic requirements, feature requirements and story requirements; Categorize story-level requirements into business stories, technical stories, and defect stories in advance.

4. The method according to claim 3, characterized in that: The detecting of the demand input instruction, obtaining the level and category of the demand to be input, and inputting the demand to be input into the office document sharing platform according to the level and category, and recording it as the target demand, includes: Preset the estimation expression; Detecting a demand entry instruction, obtaining the level and category of the demand to be entered, estimating the demand according to the obtained level and category of the demand to be entered and a preset estimation expression, and obtaining an estimation result; The estimation result is entered into the office document sharing platform according to a preset format and recorded as the target demand.

5. The method according to claim 4, characterized in that After the estimation result is input into the office document sharing platform in a preset format and recorded as a target demand, the method further includes: If the estimated result is not entered into the office document sharing platform according to the preset format, the entered demand is recorded as the target demand, and it is determined that the current target demand is in the unestimated stage.

6. The method according to claim 5, characterized in that After detecting the demand entry instruction, obtaining the level and category of the demand to be entered, entering the demand to be entered into the office document sharing platform according to the level and category, and recording it as the target demand, the method further includes: Obtain the granularity of the target requirements and limit the granularity of the requirements according to the length of the development iteration cycle.

7. The method according to claim 6, characterized in that The statistics of the quality progress indicators of the target requirements include: Statistics are collected on the number of released versions, business story ratio, defect rate and average team rate of the target requirements.

8. A demand management device, characterized in that: Applied to an office document sharing platform, the device comprises: Classification and grading setting module, used to set the level and category of requirements in advance; A demand entry module, used for detecting a demand entry instruction, obtaining the level and category of the demand to be entered, and entering the demand to be entered into the office document sharing platform according to the level and category, and recording it as a target demand; The demand confirmation module is used to obtain the confirmation result of the target demand. If the confirmation of the target demand is completed, the demand development stage is entered; A requirement verification module is used to obtain the development progress of the requirement development phase, and if it is detected that the requirement development phase has been completed, the target requirement is verified; The requirement classification module is used to determine that the target requirement has been completed if the target requirement is successfully verified, and to archive the completed target requirement according to the version.

9. A terminal, characterized in that: The terminal comprises at least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the demand management method described in any one of claims 1 to 7.

10. A non-volatile computer-readable storage medium, characterized in that: The non-volatile computer-readable storage medium stores computer-executable instructions, which, when executed by one or more processors, enable the one or more processors to execute the method for demand management described in any one of claims 1-7.