Development process creating system
The development process creation system addresses skill set diversity in agile development by using a role activity database to match participant attributes with appropriate activities, improving process efficiency and reducing inconsistencies.
Patent Information
- Application Number
- JP2023077432
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-09
- Publication Date
- 2024-11-21
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
Existing agile development methods fail to account for the diverse skill sets of participants, leading to inconsistencies and inefficiencies in activity allocation.
A development process creation system that includes a role activity database to define role activities and evaluate their compatibility with participant attributes, ensuring appropriate activity assignment based on skill sets.
The system ensures consistent and efficient activity allocation by considering participant attributes, reducing inconsistencies and enhancing development process efficiency.
Smart Images

Figure 2024162153000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a technique for creating a process for developing software. [Background technology]
[0002] Agile development methods are a general term for development processes that repeatedly carry out small development cycles. For example, a development cycle such as requirements definition → design → implementation → testing is treated as one unit, and by repeatedly carrying this out, the final deliverable is obtained. An example of an agile development method is Scrum. The iterative unit in Scrum is called a sprint.
[0003] The patent document 1 listed below aims to "provide a development process creation system by project characteristic evaluation that can accommodate various development processes, and a development process creation method using the same," and describes a technology in which "a process configuration unit 11 receives project characteristics as input, synthesizes the process architecture received from a process architecture database 12 and the activities received from an activity acquisition unit 21, and returns a development process for the requested project. In response to an activity acquisition request from the process configuration unit, the activity acquisition unit acquires multiple activities from the activity database 22. At this time, based on the project characteristics passed from the process configuration unit and past activity selection history information, it narrows down and acquires only activities that are deemed appropriate. The acquired activities are returned to the process configuration unit" (see abstract). [Prior art documents] [Patent documents]
[0004] [Patent Document 1] JP 2004-341804 A Summary of the Invention [Problem to be solved by the invention]
[0005] The method of Patent Document 1 selects activities that can increase productivity based on the characteristics of a development project. Since the method of Patent Document 1 does not handle personal information about developers, it is considered to be an effective method when the skill sets within a development team are homogenous.
[0006] On the other hand, in digital solution development, members with various backgrounds (designers, system engineers, etc.) are involved, and if activities are selected based only on project characteristics, appropriate activities may not be set. In order to make the development process more efficient, it is considered necessary to divide roles and assign activities while taking into account the backgrounds of the members. In this way, it is difficult for the method of Patent Document 1 to take into account the personal attributes of those participating in the development process.
[0007] The present invention has been made in consideration of the above-mentioned problems, and aims to provide a technology that, when constructing a development process, can assign appropriate activities according to the attributes of the participants in the development process. [Means for solving the problem]
[0008] The development process creation system of the present invention includes a role activity database that defines role activities that a role may perform in activities that constitute a development process, together with evaluation parameters that represent the results of the evaluation of the role in the activity, and presents the role activities that the role should perform in the activity as components of the development process in accordance with the evaluation parameters. Effect of the Invention
[0009] According to the development process creation system of the present invention, when constructing a development process, it is possible to assign appropriate activities according to the attributes of the participants who will participate in the development process. Other objects, configurations, advantages, etc. of the present invention will become apparent with reference to the following embodiments. [Brief description of the drawings]
[0010] [Figure 1] FIG. 1 is a configuration diagram of a development process creation system 1. [Diagram 2] FIG. 2 is a diagram showing a configuration of a process architecture database 12 and an example of data. [Diagram 3] 3 is a diagram showing a configuration of an activity database 14 and an example of data. FIG. [Figure 4] An example of the activities of the requirements definition process configured according to the activity database 14 will be shown. [Diagram 5] 5 is a schematic diagram illustrating the roles of participants participating in the data model definition activity of FIG. 4. [Figure 6] 3 is a diagram showing a configuration of a role activity database 16 and an example of data. FIG. [Figure 7] 13 is a schematic diagram showing an example of a data model definition activity configured in accordance with a role activity acquired by a role activity acquisition unit 15. FIG. [Figure 8] 1 shows an example of an activity of the requirement definition process configured by the role activity acquisition unit 15. [Figure 9] 11 is a diagram illustrating an example of an evaluation result by the role activity evaluation unit 17. FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0011] <Embodiment 1> FIG. 1 is a configuration diagram of a development process creation system 1 according to a first embodiment of the present invention. The development process creation system 1 is a system that creates a software development process. The development process here is made up of processes such as requirements definition → design → implementation → test. Each process is made up of one or more activities. The development process creation system 1 is a system that creates processes suitable for a development project and their order, activities to be performed in each process and their order, and so on.
[0012] The development process creation system 1 comprises a process configuration unit 11, a process architecture database 12, an activity acquisition unit 13, an activity database 14, a role activity acquisition unit 15, a role activity database 16, and a role activity evaluation unit 17.
[0013] The process architecture database 12 is a database that defines the structure of processes. For example, the process architecture database 12 can be configured by records that define the context of processes. As an example, a development process consisting of four processes, requirements definition → design → implementation → test, can be defined by records that define the context of these processes. When two or more processes are performed in parallel, two or more subsequent processes are associated with one preceding process.
[0014] The process configuration unit 11 receives the characteristics of a development project as an input, and acquires a process structure that matches the characteristics from the process architecture database 12. The process configuration unit 11 outputs the acquired process structure together with the activities to be performed in each process as a development process configuration for the project.
[0015] The activity database 14 defines the activities that may be performed in each process. The activity database 14 further defines the suitability of the activity for each item of project characteristics. A specific example of the suitability will be described later.
[0016] The activity acquisition unit 13 acquires, based on the specified project characteristics (received by the process configuration unit 11), activities that match the project characteristics from the activity database 14.
[0017] The role activity database 16 defines the roles that participants have in each activity and the role activities (further subdivisions of the activities) that the roles may perform in the activities. The role activity database 16 further describes evaluation parameters that indicate the results of evaluating the contribution of the roles in the role activities. Specific examples will be described later.
[0018] The role activity acquisition unit 15 acquires role activities to be performed in an activity from the role activity database 16 according to the role attributes and the role evaluation parameters. The role activity acquisition unit 15 presents the acquired role activities as components of a development process (or as components of an activity).
[0019] The role activity evaluation unit 17 receives evaluation feedback for the role activity presented by the role activity acquisition unit 15 and reflects the evaluation feedback as evaluation parameters in the role activity database 16 .
[0020] 2 is a diagram showing the configuration and example data of the process architecture database 12. The process architecture database 12 has a process field 121 and a previous process field 122. The process field 121 describes the processes that make up the development process. The previous process field 122 describes the process that should be performed immediately before the process specified by the process field 121.
[0021] The data example in Fig. 2 defines a development process in which four processes, requirement definition → design → implementation → test, are performed in this order. In addition to this, a similar process structure may be defined for each project's characteristics. Alternatively, the user may select the first process, and the process configuration unit 11 may obtain the subsequent processes according to the records in the process architecture database 12.
[0022] FIG. 3 is a diagram showing a configuration of the activity database 14 and an example of data. The activity database 14 has an activity field 141, an associated process field 142, and a project characteristic field 143. The activity field 141 describes an activity that may be performed in a process. The associated process field 142 describes a process to which the activity specified by the activity field 141 belongs. The project characteristic field 143 describes, for each item of the project characteristic, a compatibility level indicating the degree to which the activity matches the project characteristic. The project characteristic field 143 is provided for each item of the project characteristic. Examples of project characteristics are "application development experience" and "network architecture". In this example, the number of project characteristic items is two, but it may be one or three or more.
[0023] The process configuration unit 11 receives, for example, "Application development experience = Yes" and "Network architecture = Web application" as project characteristics. The project characteristic field 143 describes, for each item of the project characteristics, the degree of suitability that indicates the degree to which each activity is suitable for the project of that characteristic. For example, for the project characteristic "Network architecture", when "Network architecture = Web application", the suitability of the activity "Web configuration definition" is set high. The activity acquisition unit 13 selects an activity that matches the specified value according to the specified value for each item of the project characteristics.
[0024] Figure 4 shows an example of structuring activities in the requirements definition phase according to the activity database 14. In the data example of Figure 3, three activities, "architecture definition," "data model definition," and "web configuration definition," have been selected as activities to be performed in the requirements definition phase. In this way, it is possible to configure a development process by defining the activities to be performed in each phase according to the activity database 14. However, there is a possibility that problems will arise, as described below.
[0025] Figure 5 is a schematic diagram illustrating the roles of participants participating in the data model definition activity in Figure 4. Each participant has a role. The role here is roughly synonymous with the skill set that the participant possesses. Here, an example is shown in which Role A and Role B participate in the data model definition activity, and Role B receives the data model design document created by Role A.
[0026] The project characteristics explained in Figures 3 and 4 specify "Application development experience = Yes", so there is a possibility that roles with application development experience will participate in the data model definition activity. However, the example explained in Figures 3 and 4 does not take into consideration the attributes (skill sets) of the roles participating in the development process. Therefore, when an activity is configured according to the activity database 14, there is a possibility that the work to be performed in the activity and the skill sets possessed by each role will not be consistent.
[0027] For example, assume that Role A has no experience in application development, while Role B does. Since Role A has no experience in application development, he creates a data model design document without fully understanding the table definition items required to implement the application. Role B develops the application according to that data model design document. This may result in bugs in the application, for example, due to inconsistencies in the data model.
[0028] The inventor's research has revealed that in agile development, in particular, the relationship between activities and roles can be set relatively freely, making such inconsistencies likely to occur. One of the reasons for this is thought to be that participants in agile development are assumed to be multi-skilled (people with multiple different skill sets).
[0029] In this invention, in order to resolve such inconsistencies in role skill sets, the work that a role should perform in an activity is defined as a role activity, and the compatibility between the role activity and the role is evaluated. This is realized by the role activity database 16, the role activity acquisition unit 15, and the role activity evaluation unit 17, which will be described below.
[0030] 6 is a diagram showing a configuration of the role activity database 16 and an example of data. The role activity database 16 has a role activity field 161, an assigned activity field 162, and a role attribute field 163. The role activity field 161 defines a task that a role may perform in an activity as a role activity. The assigned activity field 162 describes an activity to which the role activity specified by the role activity field 161 belongs. The role attribute field 163 describes the result of evaluation (evaluation parameters) of the degree to which the role attribute has contributed to the role activity for each role attribute (skill set possessed by the role).
[0031] According to the data example in Fig. 6, in the data model definition activity, there are two possible role activities: "algorithm I / O definition" and "table definition." Furthermore, the role attribute field 163 describes that (a) a role with application development experience will make a large contribution by implementing table definition, and (b) a role without application development experience will make a large contribution by implementing algorithm I / O definition. For the sake of convenience, other role attributes have been omitted.
[0032] The role activity acquisition unit 15 acquires the role activities to be performed in the activity and the roles that perform the role activities from the role activity database 16. In the data example of Fig. 6, two things, "algorithm I / O definition" and "table definition", are performed within the data model definition activity, the former being performed by a role with no application development experience and the latter being performed by a role with application development experience.
[0033] FIG. 7 is a schematic diagram showing an example of configuring a data model definition activity according to the role activity acquired by the role activity acquisition unit 15. Roles A and B are the same as in FIG. 5. Role A has no experience in application development, so it performs "algorithm I / O definition" and creates an algorithm I / O definition document. The I / O here does not mean function arguments in a program, but input and output defined in a natural language that humans can understand. Therefore, it should be noted that it is possible to define it even if you have no development experience. Role B has experience in application development, so it understands the necessary data set based on such I / O definition, performs "table definition" based on the result, and creates a data model design document.
[0034] Fig. 8 shows an example of an activity of the requirement definition process configured by the role activity acquisition unit 15. The data model definition activity in Fig. 4 is replaced by two role activities "algorithm I / O definition" and "table definition".
[0035] FIG. 9 is a diagram illustrating an example of an evaluation result by role activity evaluation unit 17. Role activity acquisition unit 15 presents the activity configurations described in FIG. 7 and FIG. 8 to the user. The user inputs evaluation feedback on this to role activity evaluation unit 17. Role activity evaluation unit 17 reflects the evaluation feedback in role activity database 16. In this example, since the activity configurations in FIG. 7 and FIG. 8 were useful, the corresponding evaluation parameters in role attribute field 163 have each increased by one from the data example in FIG. 6.
[0036] In the above explanation, an example was shown in which a role inconsistency occurred when an activity was configured according to the activity database 14, but configuring a role activity is not necessarily limited to when an inconsistency occurs, and a development process may be configured using role activities from the beginning. In this case, the process configuration unit 11 receives the project characteristics, and the role activity acquisition unit 15 receives in advance the role attributes (skill sets) of the development process participants, and these are used to configure the development process according to the procedure explained above.
[0037] In the above explanation, an example was shown in which the evaluation parameters of role activities were added in conjunction with improving the activity configuration of Fig. 5 to the role activity configuration of Fig. 7, but this evaluation parameter does not necessarily have to be added only when the development process is improved. For example, even if a development process is configured using role activities from the beginning, evaluation feedback indicating that the development process was useful may be received and the evaluation parameter may be added accordingly.
[0038] <First embodiment: Summary> In the development process creation system 1 according to this embodiment, the role activity database 16 defines role activities that a role may perform in an activity together with evaluation parameters (role attribute field 163) that indicate the result of the role contribution evaluation in the role activity. The role activity acquisition unit 15 presents the role activities that a role should perform in an activity as components of a development process (or activity) according to the evaluation parameters. This makes it possible to configure an activity using role activities according to role attributes. In other words, it is possible to suppress inconsistencies between role attributes and activities.
[0039] <Embodiment 2> In the first embodiment, a configuration example in which the development process creation system 1 suppresses inconsistencies between role attributes and activities has been described. This function provided by the development process creation system 1 can also be used in related peripheral applications. In the second embodiment of the present invention, these peripheral applications of the development process creation system 1 will be described. The configuration of the development process creation system 1 is the same as in the first embodiment.
[0040] In agile development, even if each role selects an activity that they think suits them, there is a possibility that the selection is not appropriate. The development process creation system 1 visualizes that the activity selected by the role does not suit them, so that the role can realize this and support their growth. Specifically, by presenting the evaluation parameters of the role attributes described in the role activity database 16 to the participants in the development process, the role itself can check whether or not its own skill set matches the role attributes. The user interface may have a screen configuration similar to that of a table and data values as shown in FIG. 6, for example.
[0041] When looking back on an iterative unit in an agile development process (e.g., a sprint in Scrum development), it is desirable for the development process creation system 1 to provide feedback on whether the activity selection was appropriate or whether there were other activities that were more suitable. Specifically, by simultaneously presenting a list of role activities described in the role activity database 16 and evaluation parameters of role attributes, participants in the development process can check whether there were other activities that were more suitable for their own skill set. The user interface may have a screen configuration similar to that of a table and data values, for example, as shown in Figure 6.
[0042] It is conceivable to select a recommended role activity by considering not only information about one role but also attributes of related roles. This is because there may be a plurality of roles suitable for performing a certain role activity, and in order to optimize the efficiency of the entire development process, it may not be desirable to assign the most suitable role to each role activity. Specifically, when the role activity acquisition unit 15 selects a role activity, it acquires the role attributes of a plurality of participants in advance, and selects a combination of role activities and roles so that the total sum of evaluation parameters when a role activity is assigned to each role is maximized. This makes it possible to optimize the efficiency of the entire role activities performed within the activity. Alternatively, the role activity acquisition unit 15 may present only combinations of role activities and roles, and the user may select one of the combinations.
[0043] Since role attributes differ for each development project, there are cases where a role that is unknown to the person creating the development process (i.e., the user of the development process creation system 1, for example, the scrum master in scrum development) participates in the process. Even in such a case, the development process creation system 1 can assist in creating a development process. Specifically, if the skill set possessed by a role is input to the role activity acquisition unit 15 as a role attribute, a role activity suitable for that role attribute can be selected. In other words, even if the user of the development process creation system 1 does not know about the role itself, an appropriate role activity can be configured by knowing the attributes of that role.
[0044] A person who creates a development process needs to identify the skill set (or role attributes) required for the development process, but there may be cases where it is not easy to grasp what kind of skill set is required. In such cases, the development process creation system 1 can suggest the necessary skill set. For example, when the characteristics of a development project are input to the development process creation system 1, the process configuration unit 11 configures a process by referring to the process architecture database 12, the activity acquisition unit 13 configures an activity by referring to the activity database 14, and the role activity acquisition unit 15 identifies the role attributes (skill sets) required to perform each activity by referring to the role activity database 16. By presenting the identified role attributes, the skill sets required for the development process can be grasped.
[0045] <Modifications of the present invention> In the above embodiments, the process configuration unit 11, activity acquisition unit 13, role activity acquisition unit 15, and role activity evaluation unit 17 can be configured by hardware such as a circuit device that implements these functions, or can be configured by a calculation device such as a CPU (Central Processing Unit) executing software that implements these functions.
[0046] In the above embodiment, the process architecture database 12, the activity database 14, and the role activity database 16 can be configured by storing data describing these records in a storage device.
[0047] In the above embodiment, the user interface provided by the development process creation system 1 can be configured as, for example, a screen interface displayed on a display. Alternatively, the user interface can be provided by a user remotely accessing the development process creation system 1, such as a Web application. Any other type of user interface may also be used. [Explanation of symbols]
[0048] 1: Development process creation system 11: Process configuration section 12: Process Architecture Database 13: Activity acquisition section 14: Activity database 15: Role activity acquisition section 16: Role Activity Database 17: Role activity evaluation section
Claims
1. A development process creation system for creating a process for developing software, A process configuration part that configures steps in the process and their order; an activity acquisition unit that acquires a list of activities to be performed in the process; a role activity database defining the roles that developers have in said activities; a role activity acquisition unit that acquires a list of the roles corresponding to the activity from the role activity database; a role activity evaluator for evaluating the degree to which the role has contributed; Equipped with the role activity database defines role activities that the role may perform in the activity together with evaluation parameters that represent the results of the evaluation of the role in the role activity; The role activity acquisition unit presents the role activity to be performed by the role in the activity as a component of the process according to the evaluation parameters. A development process creation system comprising:
2. The role activity acquisition unit acquires a list of the roles involved in the activity, The role activity acquisition unit uses the acquired list of the activities and the roles to inquire into the role activity database, and presents a combination of the role activity to be performed in the activity and the role that is the performer of the activity as a component of the activity.
2. The development process creation system according to claim 1.
3. the role activity acquisition unit acquires a list of the roles involved in the activity together with a notification that a problem has occurred in the activity; The role activity acquisition unit presents, in response to the notification, a combination of the role activity to be performed in the activity and the role that is the performer of the activity.
2. The development process creation system according to claim 1.
4. the role activity evaluation unit receives evaluation feedback regarding the degree to which the role activity presented by the role activity acquisition unit as a component of the process has contributed to the process; The role activity evaluation unit updates, in accordance with the evaluation feedback, the evaluation parameters defined in the role activity database, which correspond to the role activity specified by the evaluation feedback and the role that is the executor of the role activity.
2. The development process creation system according to claim 1.
5. when the role activity acquisition unit receives a notification that a problem has occurred in the activity, the role activity acquisition unit presents the role activity to be performed by the role in the activity; The role activity evaluation unit receives evaluation feedback on the degree to which the role activity presented by the role activity acquisition unit contributed to the process, The role activity evaluation unit updates the evaluation parameters defined by the role activity database according to the evaluation feedback.
2. The development process creation system according to claim 1.
6. The role activity acquisition unit presents the evaluation parameters defined in the role activity database for each role.
2. The development process creation system according to claim 1.
7. The role activity acquisition unit presents a set of the role activity and the evaluation parameter defined in the role activity database for each combination of the role activity and the evaluation parameter.
2. The development process creation system according to claim 1.
8. The role activity acquisition unit selects a combination of the role activity and the role so that a sum of the evaluation parameters of the role activities performed by the role in the activity is maximized, and presents the result as a component of the process.
2. The development process creation system according to claim 1.
9. The role activity acquisition unit presents a plurality of combinations of the role activities and the roles to be performed by the roles in the activity according to the evaluation parameters.
2. The development process creation system according to claim 1.
10. The role activity database defines a skill set possessed by the role; The role activity acquisition unit presents the role activity to be performed by the role in the activity together with the skill set.
2. The development process creation system according to claim 1.
11. The process configuration unit receives characteristics of the process and configures configurations and sequences of the process based on the characteristics; the activity acquisition unit acquires the activity to be performed in the step configured by the process configuration unit based on the characteristics; The role activity acquisition unit presents a list of the roles corresponding to the activities acquired by the activity acquisition unit, thereby presenting the roles required in the process having the characteristics.
2. The development process creation system according to claim 1.
Citation Information
Patent Citations
Development process formation system by evaluation of project characteristic and development process formation method using it
JP2004341804A
