Resource scheduling system, method, electronic device and storage medium

Abstract

The present application discloses a resource scheduling system, method, electronic device and storage medium, which are related to the financial field or other fields, and can flexibly construct a collaborative space module that can complete the project in a self-organized manner, so as to be suitable for the development of complex scenario projects of medium and large enterprises. The resource scheduling system includes: multiple collaborative space modules; a project processing module, which is used to determine candidate collaborative space modules from multiple collaborative space modules according to the target software products required by the project to be processed, and each candidate collaborative space module is configured with at least one target software product; a cross-team collaboration module, which is used to receive and initiate cross-team collaboration requests when the project processing module determines multiple candidate collaborative space modules; the project processing module is also used to determine the target space configuration information according to the feedback results, so that the user can perform collaborative processing on the project to be processed based on the target collaborative space module.

Description

Technical Field

[0001] The present application relates to the financial field or other fields, and in particular to a resource scheduling system, method, electronic device and storage medium. Background Art

[0002] In view of the complex organizational environment, great differences in agile collaboration practices between departments, diversified product types, different sizes of agile teams, and completely different numbers of products developed by each team in medium and large enterprises, medium and large enterprises need to promote agile digital transformation of the organization so that organizational members can work together in a self-organized manner to adapt to project needs and respond agilely.

[0003] In related technologies, online collaborative software is based on a single team responsible for a single product. Figure 1 The system is developed and designed for the application scenario of the enterprise organizational structure shown in the figure. The team formation form is single and there is no direct communication mechanism between teams. Therefore, when it is applied to the complex scenario projects of single team and multiple products, single product and multiple teams, and multiple teams and multiple products of the above-mentioned medium and large enterprises, it is impossible to flexibly build teams according to project requirements to complete the project collaboratively, which leads to problems such as slow project implementation and high cost. Summary of the invention

[0004] The present application provides a resource scheduling system, method, electronic device and storage medium, which can flexibly build an agile team according to project requirements to collaborate to complete projects, thereby improving project implementation efficiency and reducing project implementation costs.

[0005] In order to achieve the above objectives, this application adopts the following technical solutions:

[0006] In a first aspect, a resource scheduling system is provided, including: a plurality of collaboration space modules, each collaboration space module being configured with at least one software product; a project processing module, used to determine candidate collaboration space modules from the plurality of collaboration space modules according to the target software products required for the project to be processed, each candidate collaboration space module being configured with at least one target software product; a cross-team collaboration module, used to receive a cross-team collaboration request initiated by any candidate collaboration space module when the project processing module determines a plurality of candidate collaboration space modules, and send the cross-team collaboration request to the remaining candidate collaboration space modules; receive feedback results of the remaining candidate collaboration space modules on the cross-team collaboration request, and send the feedback results to the project processing module; the project processing module is further used to determine target space configuration information according to the feedback results, and the target space configuration information is used to create a target collaboration space module, so that users can perform collaborative processing on the project to be processed based on the target collaboration space module.

[0007] Optionally, the resource scheduling system also includes: an interface display module for displaying a user interface, the user interface including at least a space configuration interface; a space configuration module for creating a collaborative space module based on space configuration information input by a user in the space configuration interface, the space configuration information including product information of at least one software product.

[0008] Optionally, the space configuration information also includes workgroup information corresponding to the software product and agile member information corresponding to the workgroup information; the feedback results of the candidate collaboration space module to the cross-team collaboration request include positive feedback results or negative feedback results corresponding to each target software product in the candidate collaboration space module; the project processing module is specifically used to: determine the corresponding target workgroup information according to the product information of the target software product corresponding to the positive feedback result in the feedback results of each candidate collaboration space module; and, determine the corresponding target agile member information according to the corresponding target workgroup information, to obtain the target space configuration information including the product information of each target software product, the corresponding target workgroup information and the target agile member information.

[0009] Optionally, the step of the space configuration module creating a collaborative space module according to the input space configuration information specifically includes: generating a collaborative space identifier; associating the collaborative space identifier with the input space configuration information to obtain the collaborative space module.

[0010] Optionally, the project processing module is further configured to: when it is determined that the number of candidate collaboration space modules is one, determine the candidate collaboration space module as the target collaboration space module.

[0011] Optionally, the product identification of the target software product and the product identification of the software product included in the collaborative space module are obtained according to the same identification generation rule, so that the product identification of the target software product matches the product identification of the software product included in the collaborative space module.

[0012] Optionally, the space configuration module is further used to: when receiving a collaboration space deletion instruction input by the user in the space configuration interface, delete the specified collaboration space module.

[0013] Optionally, the interface display module is also used to display the space configuration information editing interface when receiving a collaborative space modification instruction input by the user in the space configuration interface, and the space configuration information of the specified collaborative space module is displayed in the editing interface; the space configuration module is also used to update the configuration information of the specified collaborative space module when receiving a configuration information modification completion instruction input by the user for the specified collaborative space.

[0014] Optionally, the project processing module is also used to: generate collaboration progress information based on the cross-team collaboration request initiated by any candidate collaboration space module and the feedback results of the other candidate collaboration space modules on the cross-team collaboration request; the interface display module is also used to display the collaboration progress information when receiving the input project progress display instruction.

[0015] In a second aspect, a resource scheduling method is provided, comprising: determining a candidate collaboration space from a plurality of pre-created collaboration spaces according to a target software product required for a project to be processed, wherein a collaboration space includes at least one software product and a candidate collaboration space includes at least one target software product; when multiple candidate collaboration spaces are determined, creating a cross-team collaboration request and sending the cross-team collaboration request to the candidate collaboration space; and constructing a target collaboration space including all target software products according to feedback results of the candidate collaboration space on the cross-team collaboration request, so as to collaboratively process the project to be processed based on the target collaboration space.

[0016] Optionally, the feedback results of the candidate collaboration space to the cross-team collaboration request include positive feedback results or negative feedback results corresponding to each target software product in the candidate collaboration space; constructing the target collaboration space based on the feedback results of the candidate collaboration space to the cross-team collaboration request includes: constructing the target collaboration space based on the target software product corresponding to the positive feedback result in the feedback results of each candidate collaboration space.

[0017] Optionally, a software product corresponds to a workgroup, and the workgroup includes at least one agile member; the positive feedback result corresponding to the target software product includes the product identifier of the target software product and the target workgroup identifier corresponding to the target software product; according to the target software product corresponding to the positive feedback result in the feedback result of each candidate collaboration space, a target collaboration space is constructed, including: creating a target collaboration space identifier; determining a target agile member identifier corresponding to the workgroup identifier according to the target workgroup identifier in the positive feedback result; associating the target agile member identifier, the product identifier of the target software product, and the target workgroup identifier with the target collaboration space identifier to obtain the target collaboration space.

[0018] Optionally, the resource scheduling method further includes: when it is determined that the number of candidate collaboration spaces is one, determining one candidate collaboration space as a target collaboration space.

[0019] Optionally, the resource scheduling method further includes: when it is determined that the number of candidate collaboration spaces is zero, calling software products other than the multiple collaboration spaces and including the target software product to create the target collaboration space.

[0020] Optionally, the product identification of the target software product and the product identification of the software product included in the collaboration space are obtained according to the same identification generation rule, so that the product identification of the target software product matches the product identification of the software product included in the collaboration space.

[0021] In a third aspect, an electronic device is provided, comprising a memory, a processor, a bus and a communication interface; the memory is used to store computer execution instructions, and the processor is connected to the memory through a bus; when the electronic device is running, the processor executes the computer execution instructions stored in the memory, so that the electronic device executes the resource scheduling method provided in the second aspect.

[0022] In a fourth aspect, a computer-readable storage medium is provided, the computer-readable storage medium comprising computer execution instructions, and when the computer execution instructions are executed on a computer, the computer executes the resource scheduling method provided in the second aspect.

[0023] In a fifth aspect, a computer program product is provided, which includes computer instructions. When the computer instructions are executed on a server, the server executes the resource scheduling method provided in the second aspect and any possible design thereof.

[0024] In the resource scheduling system provided by the present application, multiple collaboration space modules, project processing modules and cross-team collaboration modules are provided. The project processing module determines the candidate collaboration space module that can contain at least one target software product from multiple collaboration space modules according to all the target software products required for the project to be processed. When the project processing module determines that the number of candidate collaboration space modules is at least two, each candidate collaboration space module initiates or receives a cross-team collaboration request through the cross-team collaboration module. At the same time, each candidate collaboration space module needs to feedback the received cross-team collaboration request, and the feedback result is summarized in the cross-team collaboration module. The cross-team collaboration module sends it to the project processing module, and the project processing module determines the target space configuration information according to the feedback result. The target space configuration information is used to create a target collaboration space module so that the user can collaborate on the project to be processed based on the target collaboration space module. Through the resource scheduling system of the present application, it is possible to flexibly construct a collaboration space module that can complete the project in a self-organized manner according to the software products required in the project to be processed, which can be applied to the development of complex scenarios of single-team multi-product, single-product multi-team and multi-team multi-product projects of medium and large enterprises, improve the efficiency and flexibility of project implementation, and reduce the communication cost of project implementation.

[0025] It can be understood that any of the resource scheduling methods, electronic devices, computer-readable storage media, computer program products or chips provided above can be applied to the corresponding systems provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding systems and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] Figure 1 A schematic diagram of an organizational structure of the prior art;

[0027] Figure 2 A schematic diagram of the structure of a resource scheduling system provided in an embodiment of the present application;

[0028] Figure 3 A schematic diagram of the organizational structure of a hierarchical agile team provided in an embodiment of the present application;

[0029] Figure 4 One of the flowcharts of a resource scheduling method provided in an embodiment of the present application;

[0030] Figure 5 A second flowchart of a resource scheduling method provided in an embodiment of the present application;

[0031] Figure 6 A third flowchart of a resource scheduling method provided in an embodiment of the present application;

[0032] Figure 7 A fourth flowchart of a resource scheduling method provided in an embodiment of the present application;

[0033] Figure 8 A fifth flow chart of a resource scheduling method provided in an embodiment of the present application;

[0034] Fig. 9 A sixth flow chart of a resource scheduling method provided in an embodiment of the present application;

[0035] Fig.10 One of the schematic diagrams of the collaboration process of a collaboration space provided in an embodiment of the present application;

[0036] Fig.11 A second schematic diagram of a collaboration process of a collaboration space provided in an embodiment of the present application;

[0037] Fig.12 One of the schematic diagrams of the relationship between the spatial configuration information provided in the embodiment of the present application;

[0038] Fig.13 A second schematic diagram of the relationship between space configuration information provided in an embodiment of the present application;

[0039] Fig.14 A schematic diagram of role permissions for a collaborative space provided in an embodiment of the present application;

[0040] Fig.15 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0041] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0042] It should be noted that, in the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

[0043] In order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, the words "first" and "second" are used to distinguish the same or similar items with basically the same functions and effects. Those skilled in the art can understand that the words "first" and "second" are not limiting the quantity and execution order. It should be noted that the collaborative space in the present application is equivalent to the collaborative space module.

[0044] In related technologies, online collaborative software is based on a single team responsible for a single product. Figure 1 The enterprise organizational structure diagram shown in the application scenario development and design has a single team formation form and no direct communication mechanism between teams. Therefore, when applied to the complex scenario projects of single team and multiple products, single product and multiple teams, and multiple teams and multiple products of the above-mentioned medium and large enterprises, it is impossible to flexibly build teams according to project requirements to collaborate to complete the project, resulting in slow project implementation and high costs.

[0045] In view of the above problems, an embodiment of the present application provides a resource scheduling system, which includes: multiple collaboration space modules, a project processing module and a cross-team collaboration module. Among them, each collaboration space module is configured with at least one software product. The project processing module determines a candidate collaboration space module that can contain at least one target software product from multiple collaboration space modules based on all target software products required for the project to be processed. When the project processing module determines that the number of candidate collaboration space modules is at least two, any candidate collaboration space module can initiate a cross-team collaboration request to the cross-team collaboration module, so as to forward the cross-team collaboration request to the remaining candidate collaboration space modules through the cross-team collaboration module, thereby establishing a liaison mechanism between the various collaboration space modules. In addition, the candidate collaboration space module needs to feedback the received cross-team collaboration request and generate a feedback result. Further, based on the generated feedback result, the target space configuration information corresponding to all target software products is determined, so as to create a target collaboration space module through the above-determined target space configuration information, so that the user can perform collaborative processing on the project to be processed based on the target collaboration space module. Through the resource scheduling system of this application, it is possible to flexibly construct a collaborative space module that can complete the project according to the software products required in the pending project, which can be applied to single-team multi-product, single-product multi-team and multi-team multi-product complex scenario projects of medium and large enterprises. On the one hand, it improves the efficiency and flexibility of project implementation. For example, through the collaborative space, each agile team can collaborate online across regions, so that the collaborative matters between agile teams can be communicated in time, improve the efficiency of problem tracking, reduce the cost of agile cross-team collaboration, and improve the efficiency of collaboration. On the other hand, the online collaborative space model of this application can also solve the problem of tight resources in the working environment of offline collaborative teams working in a centralized office. For example, a large team of 100+ works together in a shared online collaborative space when collaborating online, without the need for centralized physical office, and also achieves the effect of agile collaboration. For example, when the organization is geographically restricted or during the epidemic, the team cannot come to the site to work, through the online collaborative space system, it can be convenient to work collaboratively, ensuring the business continuity of the work, and not being affected by the physical environment.

[0046] like Figure 2 The illustrated embodiment of the present application provides a structural diagram of a resource scheduling system, wherein the resource scheduling system includes: a plurality of collaboration space modules 21, a project processing module 22 and a cross-team collaboration module 23.

[0047] In the embodiment of the present application, the resource scheduling system includes at least two collaboration space modules 21, wherein each collaboration space module 21 is configured with at least one software product.

[0048] It is understandable that the multiple collaborative space modules 21 include one or more software products. The above software products can be understood as software tools required to complete the project to be processed. In other words, the software product refers to computer software provided to users in accordance with national standards, software embedded in information systems or devices, or computer software provided when providing technical services such as computer information system integration and application services.

[0049] Among them, the collaboration space module 21 can be understood as an online collaboration space provided for self-organizing scaled agile teams based on the basic theory of agility and the self-organizing scaled agile operation needs of medium and large enterprises. And one online collaboration space corresponds to one agile team. Usually, an agile team can establish one collaboration space, and it also supports agile teams to establish multiple collaboration spaces according to the specific needs of team collaboration.

[0050] Furthermore, in the resource scheduling system of the embodiment of the present application, the project processing module 22 is used to execute the following Figure 4 Step S41 in the resource scheduling method shown.

[0051] Step S41 , according to the target software product required by the project to be processed, candidate collaboration space modules are determined from the plurality of collaboration space modules 21 , each candidate collaboration space module being configured with at least one target software product.

[0052] It is understandable that at least one target software product is configured in each candidate collaboration space module, and it should be understood that the candidate collaboration space module is a collaboration space module 21 including one or more target software products. The project processing module 22 first determines all target software products that need to be processed for the project to be processed. Then, according to the target software product, a collaboration space module 21 that can contain one or more target software products is matched from multiple collaboration space modules 21, and the collaboration space module 21 that can contain one or more target software products is used as a candidate collaboration space module. Among them, the target software product required for the project to be processed is one or more.

[0053] For example, taking the target software products required for the project to be processed as product A and product B, among the existing multiple collaboration space modules 21, the collaboration space modules including product A are collaboration space module 1 and collaboration space module 2, while the collaboration space module including product B is only collaboration space module 3, then collaboration space module 1, collaboration space module 2 and collaboration space module 3 are taken as candidate collaboration space modules.

[0054] For example, when implementing an online banking transfer function project, it is necessary to involve the development of multiple software products for the front-end online banking, the intermediate interface platform, and the back-end core system, and it is necessary to involve collaboration between multiple agile teams responsible for these products. If the multiple software products of the front-end online banking, the intermediate interface platform, and the back-end core system are product A1, product A2, and product A3, respectively, and the collaboration space modules corresponding to the agile teams corresponding to their software products are collaboration space B1, collaboration space B2, and collaboration space B3, respectively. Then, the work group responsible for product A1 in collaboration space B1, the work group responsible for product A2 in collaboration space B2, and the work group corresponding to product A3 in collaboration space B3 are respectively constructed in the target collaboration space module, and an embodiment of the method of online collaboration for the online banking transfer function project is implemented.

[0055] In some embodiments, a collaboration space module 21 is set to correspond to an agile team, that is, a collaboration space module 21 corresponds to an agile team, and a target collaboration space module 21 corresponds to a target agile team. And a collaboration space module 21 includes one or more software products.

[0056] For example, Fig.11 The collaborative process diagram of the collaborative space shown in the figure shows that the working group includes agile members composed of PO (Product Owner), SM (Scrum Master), development, testing and other roles. According to the products A and B required by the pending project, the candidate collaborative space A1 and the candidate collaborative space B1 determine the working group A of the candidate collaborative space A1 and the working group B of the candidate collaborative space B1 through cross-team collaboration requests. When executing the pending project, it is determined that the working group of the target collaborative space C is composed of working group A and working group B. Its working group A includes four roles: PO, SM, development and testing, and working group B includes four roles: PO, SM, development and testing. In other words, the agile team corresponding to the target collaborative space C is composed of agile members whose corresponding roles in the agile team are product owner (Product Owner, PO), agile expert (Scrum Master, SM), development and testing. At the same time, the software products included in the target collaborative space C are product A and product B.

[0057] It should be noted that agile teams undertake software development work for a certain business area or a certain product in accordance with Scrum (agile development) or Kanban (kanban development). For medium and large enterprises, the organizational environment is relatively complex and agile teams vary in size. Therefore, agile teams can be agile teams of various sizes, namely large agile teams, medium agile teams or small agile teams.

[0058] Furthermore, in the resource scheduling system of the present application, the cross-team collaboration module 23 is used to execute the following Figure 4 Steps S42 and S43 in the resource scheduling method shown.

[0059] Step S42: when the project processing module 22 determines a plurality of candidate collaboration space modules, a cross-team collaboration request initiated by any candidate collaboration space module is received, and the cross-team collaboration request is sent to the remaining candidate collaboration space modules.

[0060] It is understandable that one collaboration space module 21 corresponds to one agile team. When the project processing module 22 determines that the pending project requires the collaboration of multiple (i.e., at least two) candidate collaboration space modules to complete the project, a liaison mechanism between different agile teams corresponding to different collaboration space modules 21 is established based on initiating a cross-team collaboration request, thereby enabling different agile teams to directly and flexibly self-organize and form agile teams on a large scale through cross-team collaboration requests to collaborate on the pending project, avoiding the drawback of the team formation between departments in the related technology that requires step-by-step negotiation from department to team to working group.

[0061] Step S43 , receiving feedback results of the remaining candidate collaboration space modules on the cross-team collaboration request, and sending the feedback results to the project processing module 22 .

[0062] It is understandable that when the project to be processed requires multiple candidate collaboration space modules corresponding to multiple target agile teams to complete, each candidate collaboration space module can initiate a cross-team collaboration request and receive feedback from other candidate collaboration space modules on the cross-team collaboration request, so as to achieve information exchange between the candidate collaboration space modules.

[0063] It should be noted that a cross-team collaboration request can be initiated during the process of an agile team corresponding to a certain collaboration space module 21 processing a pending project. A cross-team collaboration request can also be initiated before processing the pending project, that is, when at least one collaboration space module 21 that participates in the collaborative processing of the pending project is determined. A cross-team collaboration request can also be initiated both before and during the processing of the pending project, and the embodiments of the present application do not limit this. It can also be understood that the timing of initiating a cross-team collaboration request is determined based on whether there is already at least one collaboration space processing the pending project.

[0064] For example, if the target software products required by the project to be processed are product A and product B, if the existing multiple collaboration space modules 21 include the collaboration space module 21 of product A as collaboration space module 211 and the collaboration space module 21 of product B as collaboration space module 212, then the collaboration space module 211 and the collaboration space module 212 are used as candidate collaboration space modules. The collaboration space module 211 and the collaboration space module 212 can receive cross-team collaboration requests or initiate cross-team collaboration requests to each other.

[0065] In some embodiments, Fig.10 In the collaborative process diagram of the collaborative space shown in the figure, a cross-team collaborative request may include a collaborative ticket, which includes: collaborative ticket ID, collaborative ticket name, collaborative matter description, initiator collaborative space ID, initiator contact, initiator product, recipient collaborative space ID, recipient contact, recipient product, tracking record and collaborative status. All the above information in the cross-team collaborative request can be displayed and configured on the display interface.

[0066] For example, Fig.10 As shown in the figure, when the collaboration space E corresponding to a certain agile team in area E needs the collaboration space F corresponding to the agile team in area F to collaborate on the development of product 4 and product 5. Collaboration space E initiates a cross-team collaboration request to collaboration space F. Collaboration space F receives the cross-team collaboration request and responds on the collaboration form of the cross-team collaboration request to agree to receive it. Then collaboration space G is established, and the products corresponding to collaboration space G are maintained as product 4 and product 5.

[0067] Specifically, Fig.11 and Fig.10 As shown, after the user enters the collaboration space, the collaboration between agile teams is completed through the cross-team collaboration module 23. The cross-team collaboration request includes an initiator and a receiver, and the initiator and the receiver belong to different collaboration space modules 21. When the user is working in a certain collaboration space module 21, if he finds that there is a problem that needs to be handled by other collaboration space modules 21, he will initiate a cross-team collaboration request, create a new collaboration form, enter the name of the collaboration form, the problem description, the initiator's contact person, the receiver's product ID, and the receiver's collaboration space. Through the product ID, the collaboration space corresponding to the product (i.e., the collaboration space module 21) is queried. The receiver of the collaboration form included in the cross-team collaboration request can view the collaboration form of this collaboration space module 21 as the receiver through the interface display module 24, fill in the problem handling status, the information of the processor, and reply to the collaboration form. The initiator of the collaboration form can view the processing progress of the collaboration form through the interface display module 24, fill in the remarks information, close the cross-team collaboration request, that is, close the collaboration form.

[0068] Through the collaboration sheet of cross-team collaboration request, the barriers between teams can be broken and cross-team collaboration can be achieved. The collaboration sheet is the carrier of cross-team collaboration. Agile teams can collaborate across teams through the collaboration sheet. The agile team corresponding to any collaboration space module 21 can establish cross-team collaboration requests for other agile teams as needed. The cross-team collaboration request will be automatically pushed to the collaboration space module 21 where the collaborating agile team is located, and convenient cross-team collaboration can be carried out directly on the target collaboration space module 21, avoiding the drawback of related technologies that cross-team assistance still needs to be communicated and collaborated through telephone or email.

[0069] Furthermore, in the resource scheduling system of the present application, the project processing module 22 is also used to execute the following Figure 4 Step S44 in the resource scheduling method shown.

[0070] Step S44 , determining target space configuration information according to the feedback result, where the target space configuration information is used to create a target collaboration space module 21 , so that users can collaborate on the items to be processed based on the target collaboration space module 21 .

[0071] It can be understood that, through the feedback results of each candidate collaboration space module on the cross-team collaboration request feedback, the target space configuration information is determined from at least two candidate collaboration space modules that participate in the collaborative processing of the pending project from each candidate collaboration space module. And the target space configuration information determined above is used as the space configuration information of the target collaboration space module 21, and the target collaboration space configuration module 25 is created, so that the user can perform collaborative processing on the pending project based on the target collaboration space module 21, ensuring that an agile team can be quickly formed according to the requirements of the pending project.

[0072] In other words, through cross-team collaboration requests, the enterprise organization level forms a large number of collaboration space modules 21 created by various agile teams. In addition, the cross-collaboration space module 21 communication established through cross-team collaboration, that is, the cross-team collaboration communication mechanism, builds an enterprise-level large-scale online collaboration space network without geographical restrictions. In other words, the resource scheduling system of this application builds the following Figure 3 The organizational structure environment of the hierarchical agile team organizational structure diagram based on the collaborative space is shown, so that the resource scheduling system of the present application can support both the common agile collaboration scenario of a single team and a single product, and the complex scenarios of a single team with multiple products, a single product with multiple teams, and multiple teams with multiple products. Figure 1The organizational structure with a two-dimensional plane perspective in a tree-like structure (such as: organization-department-team), and the three-dimensional perspective organizational structure with a three-dimensional hierarchical network structure constructed by this application (such as: organization-department-team, different work groups within the team) have achieved the purpose of decentralization and are more adaptable to the needs of self-organized large-scale agile teaming in enterprises. Among them, large agile teams can be refined through the collaboration space module 21, for example, one or more work groups can be subdivided within the collaboration space module 21. And the collaboration space supports dynamic teaming of subdivided work groups within agile teams, configures a visualization panel for each agile team, supports flexible and agile collaboration within the team, and also supports cross-team collaboration.

[0073] The visualization panel can be understood as a visualization panel for collaborative work of work groups (or agile groups). It replaces the whiteboard used by offline agile teams and realizes more powerful online information sharing, online communication, remote collaboration and other functions of the whiteboard. The work group can flexibly configure the work items displayed on the visualization panel through filters, that is, the visualization panel can realize content configuration, and the work group can also flexibly configure the users, roles or other work groups in the collaborative space to which the visualization panel is shared. The flexible and configurable visualization panel allows the work group to focus on the development of high-value requirements or tasks within a certain period of time.

[0074] A work group can be understood as one or more work groups that can be subdivided within an agile team according to the size of the agile team. From the perspective of building a collaborative space module, a work group is one or more work groups set up under a collaborative space. The work group in a collaborative space corresponds to a small agile team (or agile group) that is subdivided from a large agile team in actual work.

[0075] A role can be understood as a role set up according to the division of responsibilities in order to collaboratively complete development or management tasks.

[0076] Based on the above embodiments of the present application, Figure 2 As shown in the schematic diagram of the resource scheduling system structure, the resource scheduling system is also provided with an interface display module 24 and a space configuration module 25.

[0077] The interface display module 24 is used to display a user interface, which at least includes a space configuration interface.

[0078] The space configuration module 25 is used to create the collaboration space module 21 according to the space configuration information input by the user in the space configuration interface, and the space configuration information includes product information of at least one software product.

[0079] It is understandable that if Fig.12A schematic diagram of the relationship between the spatial configuration information of the resource scheduling system shown. A collaborative space module (or collaborative space) corresponds to an agile team, and a collaborative space module corresponds to N software products and N workgroups. A collaborative space module corresponds to M users and M visualization panels, where the user's role is marked as a role when it is added to the collaborative space module to become an agile member. The visualization panel is used to display the collaborative information and the entire process of adding users, roles, and workgroups, and M is greater than N.

[0080] When a user needs to create a collaborative space module 21, the user can enter the space configuration information required for the collaborative space module 21 on the space configuration interface displayed on the interface to create the collaborative space module 21. The space configuration information includes product information corresponding to all software products required to create the collaborative space module 21. In other words, the user can create a new collaborative space module based on the space configuration information in the existing collaborative space module 21, or the user can create a new collaborative space module 21 based on the space configuration information obtained by the user, that is, the space configuration information is not necessarily the space configuration information in the existing collaborative space module 21.

[0081] Based on any of the above embodiments of the present application, the step of determining the target space configuration information according to the feedback result in step S44 executed by the project processing module 22 can also be performed as follows: Figure 5 The project processing module 22 is used to specifically perform the following steps: Figure 5 Step S54 and step S55 are shown.

[0082] Step S54, determining the corresponding target workgroup information according to the product information of the target software product corresponding to the positive feedback result in the feedback result of each candidate collaboration space module.

[0083] It can be understood that, in this embodiment, all positive feedback results are determined from all feedback results of all candidate collaboration space modules, that is, all positive feedback results are a set consisting of positive feedback results in each candidate collaboration space module.

[0084] It should be noted that the positive feedback result corresponding to each target software product is used to characterize the candidate collaboration space modules that have been determined to participate in the collaborative processing of the project to be processed, and the target software products included in the candidate collaboration space that participates in the collaborative processing of the project to be processed.

[0085] Step S55, determining the corresponding target agile member information according to the corresponding target workgroup information, and obtaining the target space configuration information including the product information of each target software product, the corresponding target workgroup information and the target agile member information.

[0086] In this embodiment, there is a mapping relationship between the product information of the target software product, the corresponding target workgroup information and the target agile member information and the target software product.

[0087] The space configuration information includes: workgroup information corresponding to the software product and agile member information corresponding to the workgroup information. The feedback result of the candidate collaboration space module to the cross-team collaboration request includes positive feedback results or negative feedback results corresponding to each target software product in the candidate collaboration space module. Fig.11 As shown, the workgroup information includes agile member information and role information corresponding to the agile members. Each workgroup corresponds to a software product, and a collaborative space module 21 corresponds to at least one workgroup.

[0088] like Fig.13 The relationship diagram of the space configuration information shown in the figure includes the collaboration space ID, collaboration space name, collaboration space type ID, collaboration space keyword, collaboration space department, collaboration space team, collaboration space person in charge, collaboration space description, collaboration space image logo, creator information, usage status information, modifier information, whether encrypted, multiple workgroup IDs and multiple collaboration space software product IDs. The product information of the software product in its space configuration information includes product identification, product name and product contact person. The user role information corresponding to its collaboration space includes the role and user ID of the agile member. The user information of each user includes the user name, user local password, user real name, user region, user department ID, user agile team, user type and email address.

[0089] It is understandable that the meaning of the positive feedback result corresponding to each target software product is described in step S54, which will not be repeated here. The negative feedback result corresponding to each target software product is used to represent the candidate collaboration space module that has been determined not to participate in the collaborative processing of the pending project.

[0090] Based on any of the above embodiments of the present application, optionally, the step of creating the collaborative space module 21 according to the input space configuration information in step S44 executed by the project processing module 22 can also be performed as follows: Figure 5 Step S56 and step S57 in the resource scheduling method shown are implemented. The project processing module 22 specifically executes step S56 and step S57.

[0091] Step S56, generating a collaborative space identifier;

[0092] It is understandable that the collaborative space identifier is generated after determining the configuration information of the collaborative space module 21, or the collaborative space identifier is created first and then the space configuration information is acquired. That is, the collaborative space identifier can be generated before or after the step of acquiring the space configuration information.

[0093] Step S57 , associating the collaborative space identifier with the input space configuration information to obtain the collaborative space module 21 .

[0094] It can be understood that by configuring the relevant information for the collaborative space identifier through the space configuration information, the collaborative space module 21 is obtained. In other words, the collaborative space module 21 includes the space configuration information and the collaborative space identifier information.

[0095] It should be noted that when the input space configuration information is the target space configuration information, the target collaborative space module 21 is generated.

[0096] Based on any of the above embodiments, the project processing module 22 is further configured to execute the following steps: Figure 6 S62 in the resource scheduling method shown.

[0097] Step S62 : when it is determined that the number of candidate collaboration space modules is one, the candidate collaboration space module is determined as the target collaboration space module 21 .

[0098] In this embodiment, when there is a collaboration space module 21 among multiple collaboration space modules 21 and the software products in the collaboration space module 21 can include all target software products, that is, the number of modules in the candidate collaboration space is one, the candidate collaboration space module is directly used as the target collaboration space module 21.

[0099] It should be noted that when there are multiple collaboration space modules 21 that can include all target software products, any candidate collaboration space module is selected from the multiple collaboration space modules 21 that can include all target software products as the target collaboration space module 21, that is, the number of candidate collaboration space modules is one.

[0100] For example, if the target software products required by the project to be processed are product C and product D, if among the existing multiple collaboration space modules 21, the collaboration space modules 21 that include product C and product D have collaboration space modules 211 and collaboration space modules 212, then any one of the collaboration space modules 211 and collaboration space modules 212 is selected as a candidate collaboration space module. Then, this candidate collaboration space module is selected as the target collaboration space module 21.

[0101] Based on any of the above embodiments, the product identification of the target software product and the product identification of the software product included in the collaboration space module 21 are obtained according to the same identification generation rule so that the product identification of the target software product matches the product identification of the software product included in the collaboration space module 21.

[0102] In this embodiment, the product identification of the target software product and the product identification of the software product included in the collaboration space module 21 are generated according to the same identification generation rule, thereby ensuring that the product identification of the target software product matches the product identification of the software product included in the collaboration space module 21, thereby avoiding the problem of high project implementation costs caused by the need for secondary development of the software product during project implementation due to the inconsistency between the concept represented by the product identification of the target software product in the project to be processed and the concept represented by the product identification of the software product included in the collaboration space module 21.

[0103] Based on any of the above embodiments, the space configuration module 25 is further configured to execute: when receiving a collaborative space deletion instruction input by the user in the space configuration interface, deleting the specified collaborative space module 21.

[0104] In this embodiment, when the user needs to delete the created collaboration space module 21, the user can input a collaboration space deletion instruction in the space configuration interface to delete the instruction that the user wants to delete.

[0105] It should be noted that the user who executes the collaborative space deletion instruction is usually an administrator user of the collaborative space module 21 who is configured to have this authority.

[0106] For example, the administrator user is a system administrator, a department administrator, or a team administrator. Fig.14 As shown in the role permission diagram of the collaboration space, the system administrator, department administrator or team administrator has the permission to delete, modify and create the collaboration space module 21.

[0107] Based on any of the above embodiments, the interface display module 24 is also used to display the space configuration information editing interface when receiving a collaborative space modification instruction input by the user in the space configuration interface, and the space configuration information of the specified collaborative space module 21 is displayed in the editing interface; the space configuration module 25 is also used to update the configuration information of the specified collaborative space module 21 when receiving a configuration information modification completion instruction input by the user for the specified collaborative space.

[0108] It is understandable that when the user needs to modify the collaborative space module, a collaborative space modification instruction is initiated, and the interface display module 24 will display the space configuration information editing interface, and the space configuration information editing interface will display the space configuration information corresponding to the collaborative space module 21 to be modified. The user modifies the space configuration information corresponding to the collaborative space module 21 to be modified displayed on the space configuration information editing interface.

[0109] Specifically, the users of the resource scheduling system include three types: in-house personnel, external personnel, and other types of users. For example, in-house personnel information is obtained from the enterprise's human resources management system, external personnel information is obtained from the enterprise's external personnel management system, and other types of users are users built by the resource scheduling system.

[0110] Among them, the resource scheduling system administrator sets the role of each user in the collaboration space module 21 through the system management function. Users include: system administrator, department administrator, team administrator and ordinary user. The system administrator can set the role type of the collaboration space through the system management function. The role type can be configured according to the needs of organizational management. The above configuration is implemented by adding a new collaboration space role type or deleting a collaboration space role type. Usually, the collaboration space role types include: PO, SM, development and testing roles.

[0111] Among them, the system administrator, department administrator, and team administrator have the authority to create a collaborative space module 21. After the user logs in, the system queries the user's system role. If the user has the authority to create a collaborative space module 21, he can click the "Create collaborative space module 21" function and enter the basic information of the collaborative space module 21. The basic information includes: space name, space keywords, department, team, space person in charge, and space description. The system creates a collaborative space module 21.

[0112] After the space manager logs in to the resource scheduling system, he can manage the collaborative space module 21. The space manager clicks on the collaborative space module 21 for which he has management authority, enters the collaborative space module 21, and clicks on "Space Settings" to set the basic information of the space, the users and roles of the space, and the work groups.

[0113] The space manager sets the software product of the collaborative space module 21 through the "Space Settings - Product Information" function. Usually, the product developed by the agile team is selected. A collaborative space module 21 can set multiple software products. The software product of the collaborative space module 21 can be modified. When setting the software product of the collaborative space module 21, the resource scheduling system needs to determine whether the software product is an existing software product in the system.

[0114] The space manager can add role members to the various role types of the collaboration space through the "Space Settings - User / Role" function. The role types include: space administrator, PO, SM, developer, tester, etc.

[0115] For example, Zhang San and Zhang Si are added to the PO role of the collaboration space module 21, and Li San and Li Si are added to the SM role of the collaboration space. When adding members to the role of the collaboration space module 21, the members are usually users supported by the resource scheduling system. After the user is added as a role of the collaboration space module 21, the user can enter the collaboration space module 21.

[0116] The space manager can add a workgroup to the collaborative space through the "Space Settings - Workgroup" function. When adding a workgroup, you need to enter the name of the workgroup and add workgroup members to the workgroup. The workgroup members must be a role in the collaborative space.

[0117] When an ordinary user logs into the system, the system determines which collaborative space roles the user plays, displays a list of collaborative spaces that the user has permission to operate, and displays a list of collaborative spaces in which the user plays a space role. The user selects a collaborative space module 21 and can click to enter the collaborative space module 21.

[0118] Based on any of the above embodiments, the project processing module 22 is also used to: generate collaboration progress information based on the cross-team collaboration request initiated by any candidate collaboration space module, and the feedback results of the other candidate collaboration space modules on the cross-team collaboration request; the interface display module 24 is also used to display the collaboration progress information when receiving the input project progress display instruction.

[0119] Among them, a part of the collaboration progress information is generated according to the cross-team collaboration request initiated by any candidate collaboration space module, and the part of the collaboration progress information is displayed. It should be understood that when a candidate collaboration space initiates a cross-team collaboration request to another candidate collaboration space, the candidate collaboration space to which the cross-team collaboration request is initiated can see the collaboration progress information shared by the candidate collaboration space that initiated the cross-team collaboration request on the interface display module 24.

[0120] In this embodiment, after the cross-team collaboration request is initiated and before the target collaboration space is determined, all candidate collaboration space modules can share collaboration progress information in their respective interface display modules 24. After all candidate collaboration space modules have responded to the cross-team collaboration request and the target collaboration space module 21 has been determined, only the corresponding candidate collaboration space modules in the target collaboration space module 21 can share collaboration progress information in their respective interface display modules 24, that is, the agile members corresponding to the same collaboration space module 21 can share the corresponding collaboration progress information through the interface display module 24. The display content includes the display of the processing progress of the collaboration order in the cross-team collaboration request.

[0121] For example, a visualization panel is provided in the interface display module 24. When establishing a collaborative space, the person in charge of the space enables the permission of the visualization panel for the agile members.

[0122] It should be noted that based on the setting of a visualization panel on the interface display module 24, users of different roles can customize the display visualization panel suitable for their own needs, so that users can more quickly and intuitively understand the progress of task implementation and the task status assigned to each person.

[0123] As a possible implementation method, the interface display module 24 can also display various statistical reports at the organization level, department level, and team level to users based on the data provided by the resource scheduling system after analysis and statistics, so that users can intuitively understand the overall task implementation status of each organization, department, and team, and better help users to better control the macro-control of the organization-level large-scale agile operation.

[0124] like Figure 7 As shown, this embodiment provides a resource scheduling method, which can be used in the resource scheduling system in any of the above embodiments. Any collaboration space in the resource scheduling method corresponds to a collaboration space module in the above resource scheduling system, and a target collaboration space module corresponds to a target collaboration space. The resource scheduling method includes steps S71 to S73.

[0125] Step S71 : determining candidate collaboration spaces from a plurality of pre-created collaboration spaces according to a target software product required by the project to be processed, wherein a collaboration space includes at least one software product, and a candidate collaboration space includes at least one target software product.

[0126] It can be understood that, through step S71, the collaboration space corresponding to the required target software product is determined as the candidate collaboration space.

[0127] Optionally, when the candidate spaces are determined, the corresponding visualization panels in each candidate collaboration space can be shared.

[0128] It should be noted that step S71 can be performed by the project processing module in the resource scheduling system. The explanation of this step and the description of its beneficial effects can all be referred to step S41 in the above corresponding system embodiment, which will not be repeated here.

[0129] Step S72: when multiple candidate collaboration spaces are determined, a cross-team collaboration request is created and sent to the candidate collaboration spaces.

[0130] It is understandable that when the completion of pending projects requires the collaboration of multiple collaboration spaces, a liaison mechanism among the candidate collaboration spaces is established through cross-team collaboration requests.

[0131] Optionally, this process can be displayed on a visualization panel.

[0132] It should be noted that step S72 can be performed in the cross-team collaboration module of the resource scheduling system. The explanation of this step and the description of the beneficial effects can all refer to step S42 in the above corresponding system embodiment, which will not be repeated here.

[0133] Step S73: construct a target collaboration space including all target software products according to the feedback result of the candidate collaboration space to the cross-team collaboration request, so as to perform collaborative processing on the pending project based on the target collaboration space.

[0134] It can be understood that, through the cross-team collaboration request, each candidate collaboration space establishes a liaison mechanism, and after the liaison, the target software products corresponding to the Q candidate collaboration spaces are determined from the P candidate collaboration spaces to confirm the participation in the collaboration of the pending project. Wherein, P is greater than or equal to Q. Wherein, the feedback result of the candidate collaboration space to the cross-team collaboration request includes a positive feedback result or a negative feedback result corresponding to each target software product in the candidate collaboration space.

[0135] It should be noted that this step can be performed by the project processing module in the resource scheduling system. The explanation of this step and the description of the beneficial effects can all refer to the steps S43 and S44 in the above corresponding system embodiment, which will not be repeated here.

[0136] Optionally, a target collaboration space is constructed based on the target software product corresponding to the positive feedback result in the feedback results of each candidate collaboration space, wherein the feedback results of the candidate collaboration space to the cross-team collaboration request include the positive feedback result or the negative feedback result corresponding to each target software product in the candidate collaboration space.

[0137] It should be noted that the positive feedback result corresponding to each target software product is used to characterize the candidate collaboration space that has been determined to participate in the collaborative processing of the pending project, and the target software products included in the candidate collaboration space that participates in the collaborative processing of the pending project. The negative feedback result is used to characterize the candidate collaboration space that is confirmed not to participate in the collaborative processing of the pending project.

[0138] As a possible implementation, step S73 may include: Figure 8 Steps S83 to S85 are shown.

[0139] Step S83, creating a target collaborative space identifier;

[0140] Step S84, determining the target agile member identifier corresponding to the workgroup identifier according to the target workgroup identifier in the positive feedback result;

[0141] Step S85, associate the target agile member identifier, the product identifier of the target software product, the target workgroup identifier and the target collaboration space identifier to obtain the target collaboration space, wherein one software product corresponds to one workgroup, the workgroup includes at least one agile member, and the positive feedback result corresponding to the target software product includes the product identifier of the target software product and the target workgroup identifier corresponding to the target software product.

[0142] It can be understood that the target agile member ID corresponding to the workgroup ID is determined according to the target workgroup ID corresponding to the target software product in the positive feedback result. In other words, in the collaborative space, one software product corresponds to one workgroup, so the information of the two can be converted to each other.

[0143] It should be noted that this step can be performed by the project processing module in the resource scheduling system. The explanation of this step and the description of the beneficial effects can all refer to the steps S56 and S57 in the above corresponding system embodiment, which will not be repeated here.

[0144] like Fig. 9 As shown, the resource scheduling method also includes:

[0145] Step S92: when it is determined that the number of candidate collaboration spaces is one, determine one candidate collaboration space as a target collaboration space.

[0146] It can be understood that one collaborative space can complete pending projects without the need for collaboration in other collaborative spaces.

[0147] It should be noted that step S92 can be performed by the project processing module in the resource scheduling system. The explanation of this step and the description of the beneficial effects can all refer to step S62 in the above corresponding system embodiment, which will not be repeated here.

[0148] Optionally, the product identification of the target software product and the product identification of the software product included in the collaboration space are obtained according to the same identification generation rule, so that the product identification of the target software product matches the product identification of the software product included in the collaboration space.

[0149] For the specific description of the above optional methods, please refer to the above system embodiments, which will not be repeated here. In addition, the explanation of any resource scheduling method provided above and the description of the beneficial effects can refer to the above corresponding system embodiments, which will not be repeated here.

[0150] Reference Fig.15 As shown, an embodiment of the present invention further provides an electronic device, including a memory 41, a processor 42, a bus 43 and a communication interface 44; the memory 41 is used to store computer execution instructions, and the processor 42 is connected to the memory 41 through the bus 43; when the electronic device is running, the processor 42 executes the computer execution instructions stored in the memory 41, so that the electronic device executes the biometric password verification method provided in the above embodiment. As an example, in combination with Figure 2 The functions implemented by the interface display module 24, the space configuration module 25, the collaboration space module 21, the project processing module 22 and the cross-team collaboration module 23 in the resource scheduling system are similar to those implemented by the interface display module 24, the space configuration module 25, the collaboration space module 21, the project processing module 22 and the cross-team collaboration module 23 in the resource scheduling system. Fig.15 The function of processor 42 in is the same.

[0151] In a specific implementation, as an embodiment, the processor 42 (42-1 and 42-2) may include one or more CPUs, such as Fig.15 As an embodiment, the electronic device may include multiple processors 42, such as CPU0 and CPU1. Figure 8 42-1 and processor 42-2 are shown in FIG. Each CPU in these processors 42 may be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). The processor 42 here may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0152] The memory 41 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 41 may exist independently and be connected to the processor 42 via a bus 43. The memory 41 may also be integrated with the processor 42.

[0153] In a specific implementation, the memory 41 is used to store the data in this application and the computer execution instructions corresponding to the software program for executing this application. The processor 42 can run or execute the software program stored in the memory 41, and call the data stored in the memory 41, and various functions of the electronic device.

[0154] The communication interface 44 uses any transceiver or other device for communicating with other devices or communication networks, such as a control system, a radio access network (RAN), a wireless local area network (WLAN), etc. The communication interface 44 may include a receiving unit to implement a receiving function, and a sending unit to implement a sending function.

[0155] The bus 43 may be an industry standard architecture (ISA) bus, a peripheral component interconnect (PCI) bus, or an extended industry standard architecture (EISA) bus. The bus 43 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig.15 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0156] An embodiment of the present application further provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed on an electronic device, the electronic device is enabled to perform the actions or steps mentioned in any of the embodiments provided above.

[0157] The embodiment of the present application further provides a chip, in which a circuit and one or more interfaces for realizing the functions of the above-mentioned transfer transaction verification device are integrated.

[0158] Optionally, the chip supports functions based on Figures 4 to 9 The processing actions in the illustrated embodiments are not described in detail here. A person of ordinary skill in the art can understand that all or part of the steps to implement the above embodiments can be completed by instructing the relevant hardware through a program. The program can be stored in a computer-readable storage medium. The storage medium mentioned above can be a read-only memory, a random access memory, etc. The above processing unit or processor can be a central processing unit, a general-purpose processor, an application specific integrated circuit (ASIC), a microprocessor (digital signal processor, DSP), a field programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof.

[0159] The embodiment of the present application also provides a computer program product including instructions, when the instructions are run on an electronic device, the electronic device executes any one of the methods in the above embodiments. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on an electronic device, the process or function described in the embodiment of the present application is generated in whole or in part. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, computer, server or data center to another website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that can be integrated with one or more media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state disk (SSD)), etc.

[0160] It should be noted that the above-mentioned devices for storing computer instructions or computer programs provided in the embodiments of the present application, such as but not limited to the above-mentioned memories, computer-readable storage media and communication chips, etc., are all non-transitory.

[0161] In the process of implementing the claimed application, those skilled in the art may understand and implement other changes to the disclosed embodiments by viewing the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other components or steps, and "one" or "an" does not exclude multiple situations. A single processor or other unit can implement several functions listed in the claims. Certain measures are recorded in different dependent claims, but this does not mean that these measures cannot be combined to produce good results.

[0162] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.

Claims

1. A resource scheduling system, characterized in that: include: A plurality of collaborative space modules, each of which is configured with at least one software product; the software product is a software tool required to complete the project to be processed; A project processing module, configured to determine candidate collaboration space modules from the plurality of collaboration space modules according to the target software product required by the project to be processed, each of the candidate collaboration space modules being configured with at least one of the target software products; A cross-team collaboration module is used to receive a cross-team collaboration request initiated by any candidate collaboration space module when the project processing module determines multiple candidate collaboration space modules, and send the cross-team collaboration request to the remaining candidate collaboration space modules; receive feedback results of the remaining candidate collaboration space modules on the cross-team collaboration request, and send the feedback results to the project processing module; The project processing module is further used to determine target space configuration information according to the feedback result, and the target space configuration information is used to create a target collaboration space module so that the user can collaboratively process the project to be processed based on the target collaboration space module.

2. The resource scheduling system according to claim 1, characterized in that: Also includes: An interface display module, used to display a user interface, wherein the user interface at least includes a space configuration interface; The space configuration module is used to create the collaborative space module according to the space configuration information input by the user in the space configuration interface, wherein the space configuration information includes product information of at least one software product.

3. The resource scheduling system according to claim 2, characterized in that: The space configuration information also includes: workgroup information corresponding to the software product and agile member information corresponding to the workgroup information; the feedback results of the remaining candidate collaboration space modules to the cross-team collaboration request include positive feedback results or negative feedback results corresponding to each target software product in the remaining candidate collaboration space modules; The project processing module is specifically used for: Determine the corresponding target workgroup information according to the product information of the target software product corresponding to the positive feedback result in the feedback results of each of the remaining candidate collaboration space modules; And, according to the corresponding target workgroup information, the corresponding target agile member information is determined to obtain the target space configuration information including the product information of each target software product, the corresponding target workgroup information and the target agile member information.

4. The resource scheduling system according to claim 3, characterized in that: The step of the space configuration module creating the collaborative space module according to the input space configuration information specifically includes: Generate collaborative space logo; The collaborative space identifier is associated with the input space configuration information to obtain the collaborative space module.

5. The resource scheduling system according to claim 2, characterized in that: The space configuration module is further configured to delete a specified collaboration space module upon receiving a collaboration space deletion instruction input by a user in the space configuration interface; The interface display module is further configured to display a space configuration information editing interface when receiving a collaborative space modification instruction input by a user in the space configuration interface, wherein the space configuration information of the specified collaborative space module is displayed in the editing interface; The space configuration module is further configured to update the configuration information of the designated collaborative space module when receiving a user input instruction to complete the modification of the configuration information of the designated collaborative space.

6. A resource scheduling method, characterized in that: include: According to a target software product required by the project to be processed, the software product is a software tool required to complete the project to be processed, determining a candidate collaboration space from a plurality of pre-created collaboration spaces, wherein one of the collaboration spaces contains at least one software product, and the candidate collaboration space includes at least one target software product; When multiple candidate collaboration spaces are determined, creating a cross-team collaboration request, and sending the cross-team collaboration request to the candidate collaboration space; According to the feedback result of the candidate collaboration space to the cross-team collaboration request, a target collaboration space including all target software products is constructed, so as to perform collaborative processing on the to-be-processed project based on the target collaboration space.

7. The resource scheduling method according to claim 6, characterized in that: The feedback result of the candidate collaboration space to the cross-team collaboration request includes a positive feedback result or a negative feedback result corresponding to each target software product in the candidate collaboration space; Constructing a target collaboration space according to the feedback result of the candidate collaboration space to the cross-team collaboration request, including: The target collaboration space is constructed according to the target software product corresponding to the positive feedback result in the feedback result of each candidate collaboration space.

8. The resource scheduling method according to claim 7, characterized in that: One of the software products corresponds to one workgroup, and the workgroup includes at least one agile member; the positive feedback result corresponding to the target software product includes the product identifier of the target software product and the target workgroup identifier corresponding to the target software product; According to the target software product corresponding to the positive feedback result in the feedback result of each candidate collaboration space, constructing the target collaboration space includes: Create the target collaboration space identity; According to the target workgroup identifier in the positive feedback result, determining a target agile member identifier corresponding to the workgroup identifier; The target agile member identifier, the product identifier of the target software product, the target workgroup identifier and the target collaboration space identifier are associated to obtain the target collaboration space.

9. An electronic device, characterized in that: It includes a memory, a processor, a bus and a communication interface; the memory is used to store computer execution instructions, and the processor is connected to the memory through the bus; when the electronic device is running, the processor executes the computer execution instructions stored in the memory, so that the electronic device executes the resource scheduling method as described in any one of claims 6 to 8.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes computer-executable instructions. When the computer-executable instructions are executed on a computer, the computer is enabled to execute the resource scheduling method according to any one of claims 6 to 8.

Images