JP2023150285A - Program, information processing device, and method - Google Patents

Abstract

To objectively evaluate development activity of an engineer who is engaged in product development, or the like.SOLUTION: A server 20 in a business activity evaluation system 1 executes the steps of: acquiring, as first information, information accumulated in an issue management service in association with a business; identifying, on the basis of the first information regarding each engineer team of each of the plurality of businesses, a first parameter that varies in accordance with an activity amount of an activity allocated to each member of the engineer team, for each business; identifying one or more second businesses, constituting the plurality of businesses, to be compared with a first business constituting the plurality of businesses, on the basis of attribute information associated with each of the first business and the second business; and presenting, to a user of the first business, the first parameter of the first business and a second parameter which is calculated in conformity to the first parameter on the basis of information about the second business, in a comparable manner.SELECTED DRAWING: Figure 3

Description

The present disclosure relates to a program, an information processing device, and a method.

Product development in corporate activities is often carried out by teams of multiple engineers. A team that develops a product must appropriately allocate human resources within the company and form a team that maximizes the company's performance.

Patent Document 1 discloses an activity analysis technique for analyzing the organization and individuality of activities in corporate activities. This technology is a method for analyzing the organization of activities where multiple people can be involved at the same time, such as meetings, by acquiring information on participants who were present at the same time at the location where the activity is occurring, based on the location information of the participants. .

Japanese Patent Application Publication No. 2008-027017

By the way, when evaluating the performance of an engineering team that develops a product or the engineers belonging to that engineering team within a company, it is possible to perform quantitative evaluation using various parameters. On the other hand, when evaluating the performance of a company's activities, it is desirable to be able to refer to the performance of competing companies as a comparison target. However, with the conventional technology, it is difficult to objectively understand one's own performance by referring to the performance of competing companies.

Therefore, in the present disclosure, a technology for objectively evaluating the development activities of an engineering team that develops a product or an engineer belonging to the engineering team will be described.

According to one embodiment of the present disclosure, a program to be executed by a computer including a processor and a storage unit is provided. The program causes the processor to access an issue management service that manages activities assigned to engineers, thereby allowing each member of the engineering team of the first company, which is the company to be evaluated, to use the issue management service. a step of associating the information accumulated in the issue management service with the company and acquiring it as first information; and an activity assigned to each member of the engineering team of the first company based on the first information. a step of identifying a first parameter that changes according to the amount of activity of the company; a step of identifying one or more second companies to be compared with the first company; A step of presenting a first parameter of one company and a second parameter corresponding to the first parameter of a second company so as to be comparable is performed.

According to the present disclosure, it is possible to make a team manager, a company's management, etc. recognize that their company has issues, areas for improvement, etc. through comparison with other companies to be compared. This makes it possible to provide materials for considering measures to improve your company's issues, areas for improvement, etc.

1 is a diagram showing the overall configuration of a corporate activity evaluation system 1 according to a first embodiment; FIG. 1 is a block diagram showing a functional configuration of a terminal device 10 that constitutes a corporate activity evaluation system 1 according to a first embodiment. FIG. 2 is a diagram showing a functional configuration of a server 20 that constitutes the corporate activity evaluation system 1 according to the first embodiment. FIG. 3 is a diagram showing the data structure of a repository database 2021 stored in the server 20. FIG. 3 is a diagram showing the data structure of a parameter database 2022 and a company attribute database 2023 stored in the server 20. FIG. 2 is a flowchart illustrating an example of a flow of comparison target company identification processing performed by the corporate activity evaluation system 1 according to the first embodiment. 2 is a flowchart illustrating an example of a flow of comparison target company presentation processing performed by the corporate activity evaluation system 1 of the first embodiment. 3 is a diagram illustrating an example of a display screen of a comparison target company displayed on the terminal device 10. FIG. 3 is a diagram illustrating an example of an engineer team parameter display screen displayed on the terminal device 10. FIG.

Embodiments of the present disclosure will be described below with reference to the drawings. In the following description, the same parts are given the same reference numerals. Their names and functions are also the same. Therefore, detailed description thereof will not be repeated.

<Summary>
The corporate activity evaluation system according to the present disclosure will be explained below. This corporate activity evaluation system identifies other companies for comparison in order to evaluate the activities (performance) of an engineering team that develops products as a corporate activity, or of each engineer (member) that makes up the engineering team. This is a system that will be presented as follows. Here, an engineer team is a team consisting of multiple engineers to proceed with the development of a specific product, for example, a web service, website, etc. provided by so-called SaaS (Software as a Service). Within the team, each engineer divides their roles for each function and output of the service, and progresses development. In addition, the engineers within the team are not limited to employees employed by one specific company, but may also be employees of individual companies involved in a development project that is being jointly developed by multiple companies. Engineers may include independent contractors, so-called freelance engineers.

In order to identify the activity status of engineers, the corporate activity evaluation system according to the present disclosure accesses, for example, GitHub (registered trademark), a software development platform, and shows the achievements of engineers who are members of the engineering team. Get various parameters. GitHub is a software development platform that manages source code, which is the work of engineers, and reviews of source code. In the corporate activity evaluation system according to the present disclosure, the access destination for acquiring various parameters is not limited to GitHub, which is an example of a software development platform, but may also be GitLab (registered trademark) or Bitbucket (registered trademark), etc. Good too. Furthermore, access destinations of the corporate activity evaluation system according to the present disclosure are not limited to software development platforms, but include Jira (registered trademark), which is an issue management tool in software development, Trello (registered trademark), or backlog as an example of a task management tool. (registered trademark) etc. In this specification, the above software development platform or task management tool is collectively referred to as an issue management service. That is, the corporate activity evaluation system according to the present disclosure acquires parameters related to deliverables from an issue management service managed by an external server (cloud server). GitHub will be described below as an example of an issue management service for acquiring various parameters.

GitHub is a source code hosting service, has a repository (management means) for version control of source code that is an artifact, and manages a list of source codes at a certain point in time. GitHub also supports issues (creation) for managing projects and source code issues, push uploading of source code created or modified in an engineer's local environment (local repository) to a remote environment (remote repository), It has functions such as commit to register changes to the source code, pull request to notify that a push has been made and request a review, and merge to finalize review results and integrate history. Here, the source code is a concept that includes a programming language such as Python and a script language that is a type of programming language such as JavaScript (registered trademark).

Also, programming languages are languages used for software development, specifically HTML, CSS, JavaScript (registered trademark), Java (registered trademark), Scala, PHP, Ruby, Python, Go, C#, Node. .js etc. Also, a software framework is a software platform used for software development, specifically jQuery, React, Vue.js, Angular, Nuxt.js, Next.js, ReactNative, Spring Framework, Play Framework, Larav. el, Examples include CakePHP, RubyonRails, Django, Flask, TensorFlow, gin, Unity, and Express.

The corporate activity evaluation system according to the present disclosure acquires, as first information, information managed by GitHub about each member of the engineering team of a company to be evaluated, in association with the company to which they belong. Examples of the first information include, for each member, the number of pushes (uploads) to GitHub, the number of source code creation codes on GitHub, the number of modified codes, the number of commits, the number of pull requests (number of review requests), and the number of merges. (number of integrations), push time (upload time), commit time, pull request time (review request time), merge time (integration time), comment time, etc.

In addition, the corporate activity evaluation system according to the present disclosure assigns information to each member of the engineering team of the company being evaluated based on each value managed in GitHub acquired as the first information. The first parameter that changes depending on the amount of activity is specified for each company to which the company belongs. Examples of the first parameter are the number of merged pull requests, average time from first commit to pull request, average time from pull request creation to review, average closing time per pull request, and so on. These first parameters are calculated from the first information obtained from GitHub.

Furthermore, the corporate activity evaluation system according to the present disclosure allows each company to have one or more companies (second companies) to be compared with the company (first company) that is the user of this corporate activity evaluation system. Identification based on associated attribute information. Examples of attribute information include the number of accounts of the company in the corporate activity evaluation system (the number of accounts of members linked to the company's account), the type of account (in-house personnel/ information on the code (source code) to be used (for example, type). In addition, examples of attribute information include information regarding predetermined job offers for each company (including wage information), information regarding members (including information regarding the skills of members), information regarding each company's industry, and management status. (including corporate value information, stock price information, and survey information), and information regarding members. Then, the first parameter of the user company and the second parameter of one or more competing companies calculated corresponding to the first parameter are presented so as to be comparable. This makes it possible to objectively evaluate the development activities of each company for comparison.

<First embodiment>
Hereinafter, a corporate activity evaluation system 1, which is a first embodiment, will be described. In the following description, for example, when the terminal device 10 accesses the server 20, the server 20 responds with information for generating a screen on the terminal device 10. The terminal device 10 generates and displays a screen based on the information received from the server 20.

<1 Overall configuration of corporate activity evaluation system 1>
FIG. 1 is a diagram showing the overall configuration of a corporate activity evaluation system 1. As shown in FIG. As shown in FIG. 1, the corporate activity evaluation system 1 includes a plurality of terminal devices (in FIG. 1, a terminal device 10A and a terminal device 10B are shown. Hereinafter, they may also be collectively referred to as "terminal devices 10"). , a server 20 , and a repository server 30 . The terminal device 10, the server 20, and the repository server 30 are connected to each other via a network 80 so that they can communicate with each other. The network 80 is configured by a wired or wireless network.

The terminal device 10 is a device operated by each user. Here, the user is a person who uses the terminal device 10 to receive presentations of other companies to be compared by the corporate activity evaluation system 1, but is not limited to being a member of the engineering team, and is This includes managers (not part of the team), personnel in charge of human resources, management, etc. The terminal device 10 is realized by a stationary PC (Personal Computer), a laptop PC, or the like. In addition, the terminal device 10 may be, for example, a tablet compatible with a mobile communication system or a mobile terminal such as a smartphone.

The terminal device 10 is communicably connected to the server 20 and the repository server 30 via the network 80. The terminal device 10 is a wireless base station 81 compatible with communication standards such as 4G, 5G, and LTE (Long Term Evolution), and a wireless LAN (Local Area Network) standard such as IEEE (Institute of Electrical and Electronics Engineers) 802.11. It is connected to the network 80 by communicating with a corresponding communication device such as a wireless LAN router 82. As shown as a terminal device 10B in FIG. 1, the terminal device 10 includes a communication IF (Interface) 12, an input device 13, an output device 14, a memory 15, a storage section 16, and a processor 19.

The communication IF 12 is an interface for inputting and outputting signals so that the terminal device 10 communicates with an external device. The input device 13 is an input device (for example, a keyboard, a touch panel, a touch pad, a pointing device such as a mouse, etc.) for receiving input operations from a user. The output device 14 is an output device (display, speaker, etc.) for presenting information to the user. The memory 15 is for temporarily storing programs and data processed by the programs, and is a volatile memory such as DRAM (Dynamic Random Access Memory). The storage unit 16 is a storage device for storing data, and is, for example, a flash memory or an HDD (Hard Disc Drive). The processor 19 is hardware for executing a set of instructions written in a program, and is composed of an arithmetic unit, registers, peripheral circuits, and the like.

The server 20 is a device that manages various management values (first information) in GitHub and information on first parameters that change depending on the amount of activity assigned to each member of the engineering team. The server 20 receives information identifying the company to which the user belongs (first company), identifies the first parameter of the company and one or more companies to be compared (second company), and specifies the first parameter of the company and one or more companies to be compared (second company). The second parameter of the comparison target company calculated corresponding to the first parameter is presented to the user in a manner that allows comparison.

Server 20 is a computer connected to network 80. The server 20 includes a communication IF 22 , an input/output IF 23 , a memory 25 , a storage 26 , and a processor 29 .

The communication IF 22 is an interface for inputting and outputting signals so that the server 20 communicates with external devices. The input/output IF 23 functions as an interface with an input device for accepting input operations from a user and an output device for presenting information to the user. The memory 25 is for temporarily storing programs and data processed by the programs, and is a volatile memory such as DRAM (Dynamic Random Access Memory). The storage 26 is a storage device for storing data, and is, for example, a flash memory or an HDD (Hard Disc Drive). The processor 29 is hardware for executing a set of instructions written in a program, and is composed of an arithmetic unit, registers, peripheral circuits, and the like.

The repository server 30 is a device that manages a remote repository (management means) in GitHub. The repository server 30 accepts, stores and manages source code pushed by users, and accepts commits, pull requests, comments, merges, and the like.

<1.1 Configuration of terminal device 10>
FIG. 2 is a block diagram showing the functional configuration of the terminal device 10 that constitutes the corporate activity evaluation system 1 of the first embodiment. As shown in FIG. 2, the terminal device 10 includes a plurality of antennas (an antenna 111, an antenna 112), a wireless communication section (a first wireless communication section 121, a second wireless communication section 122) corresponding to each antenna, and an operation It includes a reception section 130 (including a keyboard 131 and a display 132), an audio processing section 140, a microphone 141, a speaker 142, a camera 150, a storage section 160, and a control section 170. The terminal device 10 also has functions and configurations that are not particularly illustrated in FIG. 2 (for example, a battery for holding power, a power supply circuit that controls the supply of power from the battery to each circuit, etc.). As shown in FIG. 2, each block included in the terminal device 10 is electrically connected by a bus or the like.

The antenna 111 radiates a signal emitted by the terminal device 10 as a radio wave. Further, the antenna 111 receives radio waves from space and provides a received signal to the first wireless communication unit 121.

The antenna 112 radiates a signal emitted by the terminal device 10 as a radio wave. Further, the antenna 112 receives radio waves from space and provides a received signal to the second wireless communication unit 122.

The first wireless communication unit 121 performs modulation and demodulation processing for transmitting and receiving signals via the antenna 111 so that the terminal device 10 communicates with other wireless devices. The second wireless communication unit 122 performs modulation and demodulation processing for transmitting and receiving signals via the antenna 112 so that the terminal device 10 communicates with other wireless devices. The first wireless communication unit 121 and the second wireless communication unit 122 are communication modules including a tuner, an RSSI (Received Signal Strength Indicator) calculation circuit, a CRC (Cyclic Redundancy Check) calculation circuit, a high frequency circuit, and the like. The first wireless communication unit 121 and the second wireless communication unit 122 perform modulation/demodulation and frequency conversion of wireless signals transmitted and received by the terminal device 10 and provide received signals to the control unit 170.

The operation reception unit 130 has a mechanism for accepting user input operations. Specifically, operation reception unit 130 includes a keyboard 131 and a display 132. Note that the operation reception unit 130 may be configured as a touch screen that detects the position of the user's touch on the touch panel by using, for example, a capacitive touch panel.

The keyboard 131 receives input operations from the user of the terminal device 10 . The keyboard 131 is a device for inputting characters, and outputs input character information to the control unit 170 as an input signal.

The display 132 displays data such as images, videos, and text under the control of the control unit 170. The display 132 is realized by, for example, an LCD (Liquid Crystal Display) or an organic EL (Electro-Luminescence) display.

The audio processing unit 140 modulates and demodulates the audio signal. The audio processing unit 140 modulates the signal provided from the microphone 141 and provides the modulated signal to the control unit 170. The audio processing unit 140 also provides an audio signal to the speaker 142. The audio processing unit 140 is realized, for example, by a processor for audio processing. The microphone 141 receives a voice input and provides a voice signal corresponding to the voice input to the voice processing unit 140 . The speaker 142 converts the audio signal provided from the audio processing unit 140 into audio and outputs the audio to the outside of the terminal device 10 .

The camera 150 is a device that receives light with a light receiving element and outputs it as a photographed image. The camera 150 is, for example, a depth camera that can detect the distance from the camera 150 to the object to be photographed.

The storage unit 160 is configured with, for example, a flash memory, and stores data and programs used by the terminal device 10. In one aspect, storage unit 160 stores user information 161 and local repository 162.

The user information 161 is information about a user who uses the terminal device 10 to receive the first parameter of the company and the second parameter of another company (second company) identified as a comparison target. be. The user information includes information for identifying the user (user ID), the user's name, organizational information such as the company to which the user belongs, ID information and password for signing in to GitHub, and the like.

The local repository 162 stores information such as source code for users to work in their own local environment when developing software using GitHub. The user stores the created source code in the local repository 162 and modifies the source code stored in the local repository 162. After completing the creation and modification, the user pushes the source code to the repository server 30. Note that the local repository 162 is stored when the user who owns the terminal device 10 is a member of an engineering team and uses GitHub; , the local repository 162 does not need to be stored.

The control unit 170 controls the operation of the terminal device 10 by reading a program stored in the storage unit 160 and executing instructions included in the program. The control unit 170 is, for example, an application installed in the terminal device 10 in advance. The control unit 170 functions as an input operation reception unit 171, a transmission/reception unit 172, a data processing unit 173, and a notification control unit 174 by operating according to a program.

The input operation reception unit 171 performs a process of accepting a user's input operation on an input device such as the keyboard 131.

The transmitting/receiving unit 172 performs processing for the terminal device 10 to transmit and receive data with an external device such as the server 20 according to a communication protocol.

The data processing unit 173 performs calculations on the data input by the terminal device 10 according to a program, and outputs the calculation results to a memory or the like.

The notification control unit 174 performs a process of presenting information to the user. The notification control unit 174 performs processes such as displaying a display image on the display 132, outputting audio to the speaker 142, and generating vibrations on the camera 150.

<1.2 Functional configuration of server 20>
FIG. 3 is a diagram showing the functional configuration of the server 20 that constitutes the corporate activity evaluation system 1 of the first embodiment. As shown in FIG. 3, the server 20 functions as a communication section 201, a storage section 202, and a control section 203.

The communication unit 201 performs processing for the server 20 to communicate with external devices.

Storage unit 202 stores data and programs used by server 20. The storage unit 202 stores a repository database 2021, a parameter database 2022, a company attribute database 2023, and the like.

The repository database 2021 stores values managed by GitHub acquired from the repository server 30 in the corporate activity evaluation system 1, such as the number of source code creation codes, the number of commits, the commit time, the number of pull requests, and the pull requests for the remote repository. This is a database for holding various information such as time. Details will be described later.

The parameter database 2022 stores first parameters that change according to the amount of activity assigned to each member, calculated from each value managed in GitHub acquired as the first information in the corporate activity evaluation system 1. A database for holding information. Details will be described later.

The company attribute database 2023 is a database for holding information on attributes associated with each company that has introduced the company activity evaluation system 1. Details will be described later.

The control unit 203 has various modules such as a reception control module 2031, a transmission control module 2032, a repository acquisition module 2033, a parameter identification module 2034, a comparison target company identification module 2035, and a team extraction module by the processor of the server 20 performing processing according to the program. It exhibits the functions shown in module 2036 and presentation module 2037.

The reception control module 2031 controls the process by which the server 20 receives signals from an external device according to a communication protocol.

The transmission control module 2032 controls the process by which the server 20 transmits a signal to an external device according to a communication protocol.

The repository acquisition module 2033 accesses the issue management service that manages activities assigned to engineers, so that each member of the engineering team of the first company that is the evaluation target company uses the issue management service. This controls the process of associating the information accumulated in the issue management service with the company and acquiring it as first information. Issue management services include, for example, GitHub (source code hosting), GitLab, and Bitbucket, which are software development platforms, Jira, which is an issue management tool in software development, and Trello, and backlog, which are task management tools. When the issue management service is GitHub, each member of the engineering team develops source code using GitHub, so the first information accumulated on GitHub is the push to GitHub. number (number of uploads), number of source code creation codes on GitHub, number of source code modification codes, number of commits to register changes to the source code, number of pull requests requesting reviews, finalizing review results. The repository server 30 records each value such as the number of merges to integrate the histories. Therefore, the repository acquisition module 2033 accesses the repository server 30 and acquires the first information stored in GitHub.

In order to perform source code version control, the repository server 30 records the user's information and the date and time when a certain user pushes source code from the local repository 162 as log information. Similarly, for each action, such as when a source code commit is made, when a pull request is made about the source code, when a comment is created, when a reply to a comment is created, when there is a merge, etc. Information about the user who performed the action and the date and time of the action are recorded as log information. This information is recorded for each member of the engineering team, for each engineer team, and for each source code file created within that project. The repository acquisition module 2033 acquires these log information from the repository server 30.

Further, the repository acquisition module 2033 stores the acquired first information in the repository database 2021 in association with the introducing company.

The parameter identification module 2034 determines, based on the first information acquired by the repository acquisition module 2033, a first parameter that changes depending on the amount of activity assigned to each member of the engineering team of the first company. Control the specified process. Here, the parameter means a specific numerical value. The parameter identification module 2034 calculates and identifies the first parameter by calculating each value, for example, based on each value managed by GitHub that is acquired as the first information.

Examples of the first parameter calculated by the parameter identification module 2034 are the number of merged pull requests, average time from first commit to pull request, average time from pull request creation to review, and average closing time per pull request. , self-merge rate, average number of comments per pull request. The number of merged pull requests is the number of pull requests that have already been merged on GitHub in a predetermined period. The average time from the first commit to the pull request is the average time from the commit to the pull request over a predetermined period. The average time from creation of a pull request to review is the average time over a predetermined period of time from creation of a pull request to implementation of a review. The average closing time per pull request is the average time in a predetermined period from when a pull request is made until it is closed. Self-merge rate is the percentage of source code that is merged without being reviewed. The average number of comments per pull request is the average number of comments on source code that has been pulled. The parameter identification module 2034 calculates these values from the first information.

Furthermore, the parameter identification module 2034 stores the identified first parameter in the parameter database 2022 for each introducing company.

The comparison target company identification module 2035 controls the process of identifying one or more companies (second companies) to be compared with the user company. The second company is an introduction company different from the first company, for example, a company similar in industry and size to the user company. Further, a single company, a plurality of companies, or even all introducing companies may be specified as the second company. The attribute information associated with the user company or the attribute information associated with the comparison target company is information included in the first information acquired by the repository acquisition module 2033, for example, identifying the members of the engineering team. It may include information associated with an account or information associated with a member's work. Specifically, the information associated with an account is the number of accounts of the company, or information by account type (in-house personnel/other company's personnel, etc.) (the number of each account or the ratio of each). Specifically, the information associated with the artifact includes the type of source code used for development, the number of codes created for the source code that is the artifact, the number of pull requests, the number of comments in reviews, the number of modified codes, and the number of commits. , number of merges, etc.

Further, the attribute information may include information on a predetermined user company. Specifically, user company information includes information regarding each company's job openings (including wage information), information regarding member skills, and information regarding management status (including corporate value information, stock price information, and survey information). , is information regarding the industry of each company.

The comparison target company identification module 2035 identifies the comparison target companies based on the attribute information associated with the user company, the attribute information associated with the comparison target companies, and the second parameter corresponding to the first parameter of each company. (the second company) may be specified. For example, the comparison target company identification module 2035 identifies the second company based on attribute information associated with the information selected by the user. Specifically, the comparison target company identification module 2035 determines the user company's attributes for a predetermined percentage or more (for example, 50% or more) of all items for each item indicating information on the user company's attributes. A company that is similar to the information may be specified as the second company, or a company that is always similar to the information may be specified as the second company. Specifically, when the items indicating attribute information are approximate, it means that compared to the attribute item of the user company, the item whose value is within a predetermined value or ratio is approximated. Alternatively, an item whose number of digits matches the value of the item may be approximated. For example, if a user selects company size as attribute information, based on the attribute information of the user company and each company, companies with the same or similar number of accounts, sales, corporate value, etc. of the user company are selected as second companies. If the user selects the industry as the attribute information, based on the attribute information of the user company and each company, a company in the same or similar industry as the user company is selected as a second company. It can be specified as .

In addition, the comparison target company identification module 2035 determines the comparison target based on the median value of the second parameter or a predetermined condition of the second parameter as the second parameter corresponding to the first parameter of each company. A company (second company) may be specified. Specifically, for example, it may be possible to identify (average) comparable companies whose predetermined second parameters are close to the median, or whose predetermined (some or all) second parameters are close to the top 25%. A comparative company that corresponds to (superior) may be identified, or a comparative company that stands out (overwhelmingly superior) with respect to a predetermined second parameter may be identified. For example, when comparing the parameters of the number of created codes of user companies based on the second parameter corresponding to the first parameter of each company, the comparison target company identification module 2035 determines that the number of created codes is in the top 25%. The company included in is identified as the second company. Here, the second parameter corresponding to the first parameter of each company is a comparison of a specific first parameter (for example, the number of created codes of the first company in the above example) among the multiple parameters of the user company. When doing this, the first parameter in another user company must be the same as the first parameter (in the above example, the number of codes created by the other company) or a related parameter (in the above example, the first parameter is related to the code called the number of codes created). (The number of pull requests related to the code, number of modified code, etc.)

The comparison target company identification module 2035 acquires attribute information for identifying the second company by reading the company attribute database 2023.

Further, the comparison target company identification module 2035 stores information on the identified comparison target companies in the parameter database 2022 for each introducing company.

Note that the comparison target company identification module 2035 may extract one comparison target company or may extract a plurality of comparison target companies.

The team extraction module 2036 compares the first parameter of the user company (first company) and the second parameter corresponding to the first parameter based on the information of the comparison target company (second company). , controls a process of extracting an engineering team at the first company that meets predetermined conditions based on the comparison results. The second parameter corresponding to the first parameter is a parameter specified for the second company, and specific examples are the number of merged pull requests, the number of merged pull requests, the number of pull requests from the first commit to the pull request, etc. The average time, average time from pull request creation to review, average closing time per pull request, self-merge rate, and average number of comments per pull request, but the first and second parameters are the same. It may be any parameter type, or it may be a different parameter type as long as it is related to the first parameter. An engineer team that meets a predetermined condition is, for example, an engineer team that has excellent parameters (high activity amount) extracted according to the amount of activity, or an engineer team that is extracted according to the amount of activity due to user operation or settings. Engineer teams whose parameters are inferior (low activity level) may be extracted by comparing their activity levels, or those that deviate by more than a certain level may be extracted. Here, the amount of activity is, for example, a numerical value indicating the activities assigned to the members of the engineering team, specifically, a value obtained by totaling the first parameter for each engineer team.

The presentation module 2037 enables the user (user company) to compare the first parameter of the user company (first company) and the second parameter corresponding to the first parameter of the second company. Control the processing to be presented. For example, the presentation module 2037 displays parameters such as the number of merged pull requests and the average time from first commit to pull request, which are examples of the first parameter of the user company, and parameters such as the average time from the first commit to the pull request, which are examples of the second parameter of the comparison target company. In order to enable comparison with parameters such as the number of merged pull requests and the average time from the first commit to the pull request, they are displayed and presented in parallel on the terminal device 10. The presentation module 2037 may present a value specified based on the first information for either or both of the first parameter and the second parameter, and the presentation module 2037 may present a value specified based on the first information. Statistical values calculated from the above may also be presented. Here, the statistical value includes an average value, median value, maximum value, minimum value, and moving average value.

At this time, the presentation module 2037 may present the second parameter of a single comparison target company, or may present the second parameters of a plurality of comparison target companies. In addition, at this time, the company name of the comparison target company may be hidden. The second parameter of the plurality of comparison target companies may be a parameter (a plurality of parameters) of each of the plurality of comparison target companies, or may be a statistical value of the parameter of the plurality of comparison target companies. The presentation module 2037 may also present the relative value of the first parameter of the user company based on the second parameter of the comparison target company. Furthermore, the presentation module 2037 displays the median value of the second parameter of the plurality of comparison companies identified by the comparison company identification module 2035, or the comparison companies (for example, top 25%) that are superior in terms of a predetermined second parameter. The second parameter of the comparative company that is overwhelmingly superior in terms of the second parameter may be presented. As a result, user companies can recognize their own position and the extent of improvement by comparing with parameters of other companies, median values of parameters of multiple companies, and parameters of a group of superior companies. becomes possible.

Furthermore, the presentation module 2037 may present the first parameter of a specific engineering team in the user company and the second parameter of the specific engineering team in the comparison target company so that they can be compared. At this time, the presentation module 2037 may present the statistical value of the first parameter of the specific engineering team or the statistical value of the second parameter of the specific engineering team. Note that the presentation module 2037 may extract a specific engineering team in the comparison target company so as to correspond to an attribute (such as the number of accounts) associated with the engineering team of the user company.

Furthermore, the presentation module 2037 may present the first parameter of a specific member of the engineering team of the user company and the second parameter of the specific member of the engineering team of the comparison target company so that they can be compared. . At this time, the presentation module 2037 may present the statistical value of the first parameter of the specific member or the statistical value of the second parameter of the specific member. Note that the presentation module 2037 may extract specific members of the comparison target company so as to correspond to attributes (position, etc.) associated with the members of the user company.

<2 Data structure>
FIG. 4 is a diagram showing the data structure of the repository database 2021 stored in the server 20. Further, FIG. 5 is a diagram showing the data structure of the parameter database 2022 and the company attribute database 2023 stored in the server 20.

As shown in FIG. 4, each record in the repository database 2021 includes an item "organization ID", an item "repository ID", an item "address", an item "repository information", and the like.

The item “organization ID” is information that identifies each organization, such as a user company, which is the target of the first information acquired from the repository server 30 in the corporate activity evaluation system 1.

The item "Repository ID" is information that identifies each repository set for each engineering team within the user company, which is the target of the first information acquired from the repository server 30 in the corporate activity evaluation system 1.

The item "address" is information indicating the address (URL) of the repository server 30 from which the corporate activity evaluation system 1 acquires the first information, and stores the address of the remote repository created for each project. Using this address, it is possible to identify a common file name (README.txt, etc.) for each project.

The item "repository information" is information related to the action for GitHub stored in the repository server 30, which acquires the first information in the corporate activity evaluation system 1. Specifically, the item "action" and the item It includes "worker", item "title", item "source code", item "creation date and time information", etc. This item "repository information" is action management information such as source code version control and comments in GitHub.

The item “action” is information about the type of action for the source code stored in the repository server 30.

The item “worker” is information that identifies each member who has performed an action on the source code stored in the repository server 30.

The item "title" is information indicating the name of the project, repair, correction, etc. that is the basis of the action.

The item "source code" is information indicating the file name of the source code that performed the action.

The item “creation date and time information” is information on the date and time when an action was performed on the source code stored in the repository server 30.

The repository acquisition module 2033 of the server 20 updates the repository database 2021 along with acquiring the first information from the repository server 30.

As shown in FIG. 5, each record in the parameter database 2022 includes an item "organization ID", an item "parameter information", and the like.

The item “Organization ID” is information that identifies each organization such as a user company for which the first parameter has been acquired in the corporate activity evaluation system 1, and corresponds to the item “Organization ID” in the repository database 2021. There is.

The item "parameter information" is information about the value that changes according to the amount of activity assigned to each member of the engineering team, which is the first parameter specified in the corporate activity evaluation system 1, and is specific information. contains the item ``Number of Issues'', the item ``Issue to Close Time'', the item ``Number of Merged Pull Requests'', the item ``Commit to Pull Request Average Time'', and the item ``Pull Request to Review Average Time''. , including the item "average closing time per pull request", the item "self-merge rate", the item "average number of comments per pull request", etc.

The item "number of issues" is information indicating the number of issues created by the company as set in GitHub.

The item "Issue-to-close time" is information indicating the average time from the creation of an issue on GitHub to its closure by the company.

The item "number of merged pull requests" is information indicating the number of pull requests already merged on GitHub by the company in a predetermined period.

The item "commit-pull request average time" is information indicating the average time from a commit to a pull request in a predetermined period by the company.

The item "pull request to review average time" is information indicating the average time in a predetermined period from when a pull request is created to when a review is conducted by the company.

The item "average closing time per pull request" is information indicating the average time in a predetermined period from when a pull request is made until it is closed by the company.

The item "self-merging rate" is information indicating the rate of source code merged without being reviewed by the company.

The item "average number of comments per pull request" is information indicating the average number of comments made by the company to pull-requested source code.

The parameter identification module 2034 of the server 20 updates the parameter database 2022 in conjunction with identifying the first parameter.

As shown in FIG. 5, each record in the company attribute database 2023 includes an item "organization ID", an item "company attribute information", and the like.

The item “Organization ID” is information that identifies each organization such as a user company for which the first parameter has been acquired in the corporate activity evaluation system 1, and corresponds to the item “Organization ID” in the repository database 2021. There is.

The item "corporate attribute information" is attribute information for specifying comparison target companies in the corporate activity evaluation system 1, and specifically, the item "number of accounts", the item "internal/external number of people", It includes the item ``Development language'', the item ``Job offered wage'', the item ``Average skill deviation value'', the item ``Sales'', the item ``Stock price'', the item ``Survey information'', etc. In addition, in the above attribute information, the item ``Number of accounts'' represents the number of accounts of the company in question, the item ``Internal/external number of people'' represents the information by account type, and the item ``Development The item ``Language'' is information regarding job openings at each company, the item ``Job offer wage'' is information regarding the skills of members, and the item ``Average skill deviation value'' is information regarding the management status (corporate value information, stock price information, survey information). The item ``stock price'' and the item ``corporate value information'' are shown as examples (including information on each company's industry), and the item ``sales'' is shown as information on the industry of each company.

The item "number of accounts" is information indicating the number of accounts of members belonging to the company registered in GitHub.

The item "internal/external number of people" is information indicating the number of accounts of company personnel and the number of accounts of other company's (external) personnel among the number of accounts of members belonging to the company registered in GitHub.

The item "development language" is information about the programming language that the company uses for development, which is registered on GitHub.

The item "Job Offered Wage" is information that is set in advance by the user and indicates the amount of the wage that the company has presented in the job offer information.

The item "Average skill deviation value" is a numerical value that indicates the degree of skill of engineers at the company (value expressed as a deviation value after performing statistical processing on the numerical value of the engineer's skill), which has been set in advance by the user. It is information.

The item "sales" is information indicating the sales amount of the company in a predetermined period (quarterly, yearly, etc.), which is preset by the user.

The item "stock price" is information that is set in advance by the user and indicates the stock price of the company at a predetermined time.

The item "survey information" is survey information of the company set in advance by the user, and specifically, information on the results of a survey regarding the health condition or state of mind of the members of the company.

Note that the item "Company attribute information" may store information for each member of the engineering team, for example, information on the skills of the members, information on the development language, information on the position, information on the account type, etc. May be included.

The repository acquisition module 2033 of the server 20 may update the item "number of accounts" and the item "number of internal/external" of the company attribute database 2023 in conjunction with acquiring the first information from the repository server 30. Further, the item "company attribute information" in the company attribute database 2023 may be a value set in advance by an employee of the company.

<3 Operation>
Hereinafter, with reference to FIGS. 6 and 7, comparison target company identification processing and comparison target company presentation processing by the corporate activity evaluation system 1 in the first embodiment will be described.

FIG. 6 is a flowchart illustrating an example of the flow of the comparison target company identification process by the corporate activity evaluation system 1 of the first embodiment.

Each member of the engineering team operates the terminal device 10 to perform actions such as pushing and commenting from the GitHub local repository to the remote repository of the repository server 30, and inputs the input operation reception section of the terminal device 10. 171 receives instructions for the action from the user. In step S111, the transmitting/receiving unit 172 transmits information on the received action to the server 20. The server 20 receives action information via the communication unit 201.

In step S112, the repository acquisition module 2033 of the server 20 calculates the number of pushes (uploads) to GitHub and the number of source code creation codes on GitHub, which are recorded in the repository server 30 for each member of the engineering team. , the number of code modifications to the source code, the number of commits to register changes to the source code, the number of pull requests requesting reviews, the number of merges to finalize the review results and integrate the history, etc. In order to obtain the information, the repository server 30 is accessed and a request signal is sent. The repository acquisition module 2033 acquires first information from the repository server 30 via the communication unit 201. Further, the repository acquisition module 2033 stores the acquired first information in the repository database 2021 in association with the introducing company.

The first information acquired in step S112 is, for example, information uploaded online by each member within a certain period of time in order to create a product as an engineer, such as push (upload) to GitHub, A value that counts actions such as source code creation code, modification code, commits to register changes to source code, pull requests to request reviews, merges to finalize review results and integrate history, etc. over a certain period of time. It is.

In step S113, the parameter identification module 2034 of the server 20 changes the amount of activity assigned to each member of the engineering team based on the first information managed by GitHub acquired in step S112. Specify the first parameter. Furthermore, the parameter identification module 2034 stores the identified first parameter in the parameter database 2022 for each introducing company.

The first parameters identified in step S113 include, for example, the number of merged pull requests, the average time from the first commit to the pull request, the average time from pull request creation to review, the average closing time per pull request, Merge rate, average number of comments per pull request.

In step S114, the comparison target company identification module 2035 of the server 20 selects one or more companies (second companies) to be compared with the user company, based on attribute information associated with the user company (first company). Identify. The comparison target company identification module 2035 acquires attribute information for identifying the second company by reading the company attribute database 2023. Further, the comparison target company identification module 2035 stores information on the identified comparison target companies in the parameter database 2022 for each introducing company, but illustration thereof is omitted.

As described above, in the corporate activity evaluation system 1, the first information, which is information about the activities assigned to engineers recorded in GitHub, is acquired, and based on the first information, each component of the engineer team is evaluated. A first parameter that changes depending on the amount of activity assigned to the user is specified, and a comparison target company to be compared with the user company is specified. Thereby, it is possible to specify a company to be compared for objectively evaluating the performance of the user company.

FIG. 7 is a flowchart illustrating an example of the flow of subject extraction and presentation processing performed by the corporate activity evaluation system 1 of the first embodiment.

As a premise for performing the process of step S211, user registration is performed to sign in to the corporate activity evaluation system 1 (not shown in FIG. 7). The input operation reception unit 171 of the terminal device 10 receives information input from the user for a user ID (a temporary one may be used) and a password to identify the user in order to sign in to the corporate activity evaluation system 1. The transmitter/receiver 172 transmits the received user ID, password, and information about the user's engineering team to the server 20 . The server 20 receives the transmitted user ID and password via the communication unit 201 and registers the user information. The input operation reception unit 171 of the terminal device 10 accepts the selection of GitHub or other services as a service to be linked, selects an organization (company, etc.) registered with the service, and selects the engineer team and members associated with the organization. (member) receives the repository selection and sends it to the server 20. The server 20 receives various transmitted selection information via the communication unit 201 and registers the selection information.

In step S211, the input operation receiving unit 171 of the terminal device 10 provides an organization ID for identifying the organization of the user and user information (user ID and password) of the user as information for signing in to the corporate activity evaluation system 1. input from the user. The transmitting/receiving unit 172 transmits the received organization ID and user information to the server 20.

In step S221, the server 20 receives the organization ID and user information transmitted from the terminal device 10 via the communication unit 201, performs predetermined authentication, and accepts the user's sign-in.

In step S222, the presentation module 2037 of the server 20 displays the first parameter of the user company (first company) and the second parameter of the comparison target company (second company) identified in step S114. Read from parameter database 2022.

In step S223, the presentation module 2037 of the server 20 transmits the first parameter of the user company and the second parameter of the comparison target company read out in step S222 to the terminal device 10 via the communication unit 201.

In step S213, the transmitting/receiving unit 172 of the terminal device 10 receives information about the first parameter of the user company and the second parameter of the comparison target company transmitted from the server 20. The notification control unit 174 causes the display 132 to display the received information on the first parameter of the user company and the second parameter of the comparison target company. At this time, the notification control unit 174 displays the received first parameter information of the user company and the second parameter information of the comparison target company, for example, in parallel so that they can be compared.

In step S214, the input operation receiving unit 171 of the terminal device 10 receives an input of instruction information from the user, since the user performs an instruction operation to extract an engineering team in the first company that corresponds to a predetermined condition. The transmitting/receiving unit 172 transmits the received instruction information to the server 20. The transmitting/receiving unit 172 of the terminal device 10 receives information about the extracted engineer team transmitted from the server 20. The notification control unit 174 displays the received engineering team information on the display 132.

In step S224, the server 20 receives the instruction information transmitted from the terminal device 10 via the communication unit 201. The team extraction module 2036 of the server 20 extracts the engineer team in the first company that corresponds to the predetermined conditions of the instruction information, and transmits information on the extracted engineer team to the terminal device 10 via the communication unit 201.

As described above, the corporate activity evaluation system 1 allows the user to compare the first parameter of the user company and the second parameter of the comparison target company with respect to the comparison target company to be compared with the user company. present. This makes it possible to objectively understand the development activities of the user company's engineers by comparing them with those of comparable companies.

<4 Screen example>
Hereinafter, with reference to FIGS. 8 and 9, a screen example of the comparison target company presentation process by the corporate activity evaluation system 1 will be described.

FIG. 8 is a diagram showing an example of a display screen of comparison target companies displayed on the terminal device 10. The example screen in FIG. 8 shows an example screen in which the first parameter of the user company and the second parameter of the comparison target company are presented so as to be comparable. This corresponds to step S213 in FIG.

As shown in FIG. 8, the display 132 of the terminal device 10 displays the user company's first parameter and the comparison target company's second parameter for a certain period of time. The comparison target company display screen displayed on the display 132 includes a company name display field 1031a that displays the name of the user company, and a period display field 1031b that displays the period covered by the first parameter and the second parameter. A parameter display column 1031c that displays the first parameter of the user company and the second parameter of the comparison target company is displayed.

The first parameter and second parameter displayed in the parameter display field 1031c are parameters for each company stored in the parameter database 2022, and the first parameter of the user company is in column 1031c1, and the first parameter in column 1031c2 is The second parameter of the comparison target companies is displayed, and in addition, the median value of all the companies that have introduced the system and words indicating the trends of the data are displayed. The first and second parameters displayed in the parameter display field 1031c include, for example, the number of merged pull requests, the average time from the first commit to the pull request, and the average time from the creation of the pull request to the review. , average close time per pull request, self-merge rate, and average number of comments per pull request are displayed. Thereby, it is possible to refer to the user company's first parameter and the comparison target company's second parameter so that they can be compared.

FIG. 9 is a diagram showing an example of an engineer team parameter display screen displayed on the terminal device 10. The screen example in FIG. 9 shows a screen example in which the first parameter of the engineering team at the first company, which corresponds to the predetermined condition operated by the user, is displayed. This corresponds to step S214 in FIG.

As shown in FIG. 9, the display 132 of the terminal device 10 displays the user company's first parameter and the extracted engineer team's first parameter for a certain period of time. The engineering team parameter display screen displayed on the display 132 includes a company name display field 1032a that displays the name of the user company, a period display field 1032b that displays the target period of the first parameter, and the user company's first parameter display screen. 1 and a parameter display field 1032c that displays the first parameter of the extracted engineer team.

The first parameter displayed in the parameter display column 1032c is a parameter for each company stored in the parameter database 2022, with the first parameter for the entire user company in column 1032c1 and the first parameter for each engineer team in column 1032c2. The first parameter of is displayed, and the median value of the engineering team within the user company is also displayed. The first parameters displayed in the parameter etc. display field 1032c are the number of merged pull requests, the average time from the first commit to the pull request, the average time from the creation of the pull request to the review, and 1. Average close time per pull request, self-merge rate, and average number of comments per pull request are displayed. Thereby, it is possible to refer to the first parameter for each engineer team in a comparable manner.

<Summary>
As described above, according to the present embodiment, the first information, which is information about activities assigned to engineers recorded in GitHub, is acquired, and based on the first information, each member of the engineer team A first parameter that changes depending on the amount of activity assigned to the user company is specified, and a comparison target company to be compared with the user company is specified. The first parameter of the user company and the second parameter of the comparison target company are then presented to the user so that they can be compared with respect to the comparison target company that is to be compared with the specified user company. Therefore, it becomes possible to objectively understand the development activities of the user company's engineers by comparing them with those of comparable companies. This allows team managers and company management to recognize that their company has issues and areas for improvement through comparison with other comparable companies, so they can improve their own issues and areas for improvement. This makes it possible to provide materials for considering measures for achieving this goal.

Further, according to the present embodiment, an engineer team in a first company that meets a predetermined condition is extracted, and the first parameter of the extracted engineer team is presented to the user. Through this, for example, it is possible to understand which engineering teams are superior in parameters extracted according to the amount of activity (higher amount of activity), or which are inferior in parameters extracted according to the amount of activity (lower amount of activity). becomes possible. This makes it possible to understand the individual situation of each engineering team.

Although the disclosed embodiments have been described above, they can be implemented in various other forms, and can be implemented with various omissions, substitutions, and changes. These embodiments and modifications, as well as omissions, substitutions, and changes, are included within the technical scope of the claims and their equivalents.

<Additional notes>
The matters described in each of the above embodiments are additionally described below.

(Additional Note 1) A program to be executed by a computer including a processor 29 and a storage unit 202, the program allows the processor 29 to access an issue management service that manages activities assigned to engineers. A step of associating information accumulated in the issue management service by each member of the engineering team of the first company that is the evaluation target company using the issue management service with the company and acquiring it as first information. (S112); and a step of identifying, based on the first information, a first parameter that changes depending on the amount of activity assigned to each member of the engineering team of the first company (S113); A step of identifying one or more second companies to be compared with the first company (S114); A program that executes a step (S223) of presenting one parameter and a second parameter corresponding to the second parameter in a comparative manner.

(Additional Note 2) In the step of identifying the second company, attribute information associated with the first company, attribute information associated with the second company, and a second The program according to (Appendix 1), which identifies the second company based on the parameters.

(Additional Note 3) The program according to (Appendix 2), wherein in the step of specifying the second company, the second company is specified based on attribute information included in the first information.

(Additional Note 4) The attribute information includes information associated with an account that identifies each member in the issue management service, and in the step of identifying the second company, the attribute information includes information associated with the account. The program described in (Appendix 3) that identifies the companies in Item 2.

(Additional note 5) The attribute information includes the number of accounts of the first company or the type of account indicating the type of each member in the first company, and in the step of specifying the second company, The program according to (Appendix 4), which identifies the second company based on attribute information including the number of accounts of the company or the type of accounts.

(Additional Note 6) The attribute information includes information associated with the deliverables of each member in the issue management service, and in the step of identifying the second company, the attribute information includes the information associated with the deliverables. The program according to any one of (Appendix 3) to (Appendix 5) that identifies the company specified in Item 2.

(Additional note 7) The attribute information includes information regarding the code used by each member in the issue management service, and in the step of identifying the second company, the second company is identified based on the attribute information including the information regarding the code. Specify the program described in (Appendix 6).

(Additional Note 8) In the step of identifying the second company, information regarding job openings at the first company, information regarding the skills of members at the first company, included in the predetermined attribute information, Specify any one of (Appendix 2) to (Appendix 7) that specifies the second company based on information regarding the business condition of the company, information regarding each member of the first company, or information regarding the performance of the first company. program.

(Additional Note 9) In the step of presenting the first parameter and the second parameter in a comparable manner, the first parameter and the second parameter calculated based on the first information of the single second company are Parameter, a second parameter calculated based on the first information of a plurality of second companies, or both are presented in a manner that can be compared with (Appendix 1) to (Appendix 8). Programs listed.

(Additional Note 10) In the step of presenting the first parameter and the second parameter in a comparable manner, the relative value of the first parameter of the first company based on the second parameter of the specific second company. The program according to any one of (Appendix 1) to (Appendix 9), which presents a value.

(Additional Note 11) In the step of presenting the first parameter and the second parameter in a comparable manner, the first parameter of the engineering team in the first company and the second parameter of the engineering team in the second company The program according to any one of (Appendix 1) to (Appendix 10), which presents the following in a comparable manner.

(Additional Note 12) The statistical value of the first parameter of the engineering team in the first company or the statistical value of the second parameter of the engineering team in the second company is presented in a comparable manner, as described in (Appendix 11). program.

(Additional Note 13) In the step of presenting the first parameter and the second parameter so that they can be compared, the first parameter of each member in the first company and the second parameter of each member in the second company The program according to any one of (Appendix 1) to (Appendix 12), which presents parameters in a manner that allows comparison.

(Additional Note 14) In (Appendix 13), the statistical value of the first parameter of each member in the first company or the statistical value of the first parameter of each member in the second company is presented in a comparable manner. Programs listed.

(Additional Note 15) A first parameter for each member in the first company, and a second parameter for each member in the second company, which corresponds to an attribute associated with each member in the first company; The program according to (Appendix 13), which presents the following in a comparable manner.

(Additional Note 16) Compare the first parameter of the first company and the second parameter of the second company, and extract the engineering team in the first company that meets predetermined conditions based on the comparison result. The program according to any one of (Appendix 1) to (Appendix 15), which causes the program to execute the step (S224) and the step of presenting the extracted engineer team information.

(Additional Note 17) In the step of extracting engineer teams, in the first company, there are engineering teams whose members have a high amount of activity to create deliverables, or whose members have a low amount of activity to create deliverables. The program described in (Appendix 16) that extracts an engineer team.

(Additional Note 18) An information processing device comprising a control unit 203 and a storage unit 202, in which the control unit 203 is configured to determine whether a company is an evaluation target company by accessing an issue management service that manages activities assigned to engineers. a step of associating information accumulated in the issue management service when each member of the engineering team of the first company uses the issue management service with the company and acquiring it as first information (S112); a step (S113) of identifying a first parameter that changes depending on the amount of activity assigned to each member of the engineering team of the first company based on the first information; a step of identifying one or more second companies to be compared (S114), and determining, for the first company, a first parameter of the first company and a first parameter of the second company An information processing apparatus that executes a step (S223) of presenting a second parameter for comparison with a second parameter.

(Additional Note 19) A method to be executed by a computer including a processor 29 and a storage unit 202, the method being performed by the processor 29 accessing an issue management service that manages activities assigned to engineers. , each member of the engineering team of the first company that is the evaluation target company uses the issue management service, and the information accumulated in the issue management service is associated with the company and acquired as first information. a step (S112); and a step (S113) of identifying, based on the first information, a first parameter that changes depending on the amount of activity assigned to each member of the engineering team of the first company. , a step of identifying one or more second companies to be compared with the first company (S114); A method comprising: presenting a first parameter and a corresponding second parameter so as to be comparable (S223).

1: Corporate activity evaluation system 10: Terminal device 10A: Terminal device 10B: Terminal device 13: Input device 14: Output device 15: Memory 16: Storage unit 19: Processor 20: Server 25: Memory 26: Storage 29: Processor 30: Repository server 80: Network 81: Wireless base station 82: Wireless LAN router 111: Antenna 112: Antenna 121: First wireless communication unit 122: Second wireless communication unit 130: Operation reception unit 131: Keyboard 132: Display 140: Audio processing Unit 141: Microphone 142: Speaker 150: Camera 160: Storage unit 161: User information 162: Local repository 170: Control unit 171: Input operation reception unit 172: Transmission/reception unit 173: Data processing unit 174: Notification control unit 201: Communication unit 202: Storage unit 203: Control unit 1031a: Organization ID input field 1031b: Email address input field 1031c: Password input field 1031d: Login button 1032a: Team name display field 1032b: Member name display field 1032c: Parameter etc. display field 1032d: Period change input field 1032e: Condition change input field 1033a: Name display field 1033b: Parameter etc. display field 1033c: Graph display field 1033d: Period change input field 1034a: Business name display field 1034b: Team name display field 1034c: Parameter etc. display Column 1034d: Period change input column 1034e: Condition change input column 2021: Repository database 2022: Member performance database 2023: Team performance database 2031: Reception control module 2032: Transmission control module 2033: Repository management module 2034: Parameter identification module 2035: Target extraction module 2036: User attribute information acquisition module 2037: Presentation module

Claims (19)

A program to be executed by a computer including a processor and a storage unit,
The program causes the processor to:
By accessing the issue management service that manages activities assigned to engineers, each member of the engineering team of the first company, which is the company to be evaluated, can use the issue management service. a step of associating information accumulated in the company with the company and acquiring it as first information;
identifying, based on the first information, a first parameter that changes depending on the amount of activity assigned to each member of the engineering team of the first company;
identifying one or more second companies to be compared with the first company;
presenting to the first company the first parameter of the first company and a second parameter corresponding to the first parameter of the second company so that they can be compared; A program to be executed. In the step of identifying the second company, information on attributes associated with the first company, information on attributes associated with the second company, and a second parameter corresponding to the first parameter in each company are provided. The program according to claim 1, wherein the program identifies the second company based on a parameter. The program according to claim 2, wherein in the step of identifying the second company, the second company is identified based on information on the attribute included in the first information and associated with the first company. . The attribute information includes information associated with an account that identifies each member in the issue management service,
4. The program according to claim 3, wherein in the step of specifying the second company, the second company is specified based on information on the attribute including information associated with the account. The attribute information includes the number of the accounts of the first company or the type of the account indicating the type of each member of the first company,
5. The method according to claim 4, wherein in the step of identifying the second company, the second company is identified based on the attribute information including the number of accounts of the first company or the type of the account. program. The attribute information includes information associated with a product of each member in the issue management service,
According to any one of claims 3 to 5, in the step of identifying the second company, the second company is identified based on information on the attributes including information associated with the deliverable. program. The attribute information includes information regarding a code used by each member in the issue management service,
7. The program according to claim 6, wherein in the step of specifying the second company, the second company is specified based on information on the attribute including information regarding the code. In the step of identifying the second company, information regarding job openings at the first company, information regarding the skills of the members at the first company, and information regarding the skills of the members at the first company, which are included in the predetermined attribute information, are included in the predetermined attribute information. The second company is specified based on information regarding the business status of the company, information regarding each of the members of the first company, or information regarding the performance of the first company. The program described in any one of the paragraphs. In the step of presenting the first parameter and the second parameter so that they can be compared,
the first parameter;
the second parameter calculated based on the first information of the single second company;
9. The second parameter calculated based on the first information of a plurality of second companies is presented in a manner that can be compared with either or both of the second parameters. The program described in. In the step of presenting the first parameter and the second parameter so as to be comparable, the first parameter of the first company is based on the second parameter of the specific second company. The program according to any one of claims 1 to 9, which presents a relative value of. In the step of presenting the first parameter and the second parameter so as to be comparable, the first parameter of the engineering team in the first company and the first parameter of the engineering team in the second company 11. The program according to any one of claims 1 to 10, wherein the program presents two parameters in a manner that can be compared. 11. A statistical value as the first parameter of the engineering team in the first company or a statistical value as the second parameter of the engineering team in the second company is presented so as to be comparable. The program described in. In the step of presenting the first parameter and the second parameter in a comparable manner, the first parameter of each of the members in the first company and the first parameter of each of the members in the second company The program according to any one of claims 1 to 12, wherein the program presents the second parameter so as to be comparable. A statistical value as the first parameter of each member in the first company or a statistical value as the first parameter of each member in the second company is presented in a comparable manner. The program described in item 13. the first parameters of each of the members in the first company; and the second parameters of each of the members in the second company, corresponding to the attributes associated with each of the members in the first company. 14. The program according to claim 13, which presents parameters of and in a comparable manner. The first parameter of the first company and the second parameter of the second company are compared, and the engineer team at the first company satisfies a predetermined condition based on the result of the comparison. a step of extracting
The program according to any one of claims 1 to 15, causing the program to execute the step of presenting extracted information about the engineer team. In the step of extracting the engineering team, in the first company, the engineering team whose members have a high amount of activity for creating deliverables, or whose members have a high amount of activity for creating deliverables; 17. The program according to claim 16, which extracts the engineering team that is low. An information processing device comprising a control unit and a storage unit,
The control unit includes:
By accessing the issue management service that manages activities assigned to engineers, each member of the engineering team of the first company, which is the company to be evaluated, can use the issue management service. a step of associating information accumulated in the company with the company and acquiring it as first information;
identifying, based on the first information, a first parameter that changes depending on the amount of activity assigned to each member of the engineering team of the first company;
identifying one or more second companies to be compared with the first company;
presenting to the first company the first parameter of the first company and a second parameter corresponding to the first parameter of the second company so that they can be compared; An information processing device that executes. A method executed by a computer comprising a processor and a storage unit, the method comprising:
The method includes the processor:
By accessing the issue management service that manages activities assigned to engineers, each member of the engineering team of the first company, which is the company to be evaluated, can use the issue management service. a step of associating information accumulated in the company with the company and acquiring it as first information;
identifying, based on the first information, a first parameter that changes depending on the amount of activity assigned to each member of the engineering team of the first company;
identifying one or more second companies to be compared with the first company;
presenting to the first company the first parameter of the first company and a second parameter corresponding to the first parameter of the second company so that they can be compared; way to execute.