Classification of Task Types in Software Development Projects

Round 1

Reviewer 1 Report

General comments：

The article is devoted to the problems of managing software development processes and proposed a classification algorithm for the manual recognition of task types. 

In the experiments, authors used real software projects from the financial sector, managed by the Jira system. The developed model can be connected with the Jira system enabling easy data acquisition for analysis.

However, there are some issues that need to be checked:

- The article discusses the model of the programming process oriented towards manual recognition of task types, which enables effective support for planning tasks carried out in innovative IT projects.

However, comparisons of advantages and disadvantages with other related works in recent years are not found in the manuscript.

- Can the quantified indicators be added to the manuscript to verify the robustness of the model? 

- Sometimes unsubstantiated conclusions are used.

Minor comments: 

- The figures in the manuscript are clear and consistent, however, please check the format of the titles of figure 4, figure 7, figure 8, figure 9, and figure11.

- Please check the title of table 2: ' Types of state and recurring tasks used by the model.'  -> stateful.

This paper was well written, but the above issues should be verified clearly.

Author Response

Dear Reviewer,
We would like to express our appreciation for the reviews. Thank you very much for suggestions, which were clear and very accurate. We made the necessary corrections. We have incorporated all the suggestions because we agreed with them, and thank you especially for such good suggestions to improve our article.
We would like to refer to the detailed reviewer’s suggestions below:
The article is devoted to the problems of managing software development processes and proposed a classification algorithm for the manual recognition of task types.
In the experiments, authors used real software projects from the financial sector, managed by the Jira system. The developed model can be connected with the Jira system enabling easy data acquisition for analysis.
Authors’ response: Thank you for the positive reception of the article.
However, there are some issues that need to be checked:
- The article discusses the model of the programming process oriented towards manual recognition of task types, which enables effective support for planning tasks carried out in innovative IT projects.
However, comparisons of advantages and disadvantages with other related works in recent years are not found in the manuscript.
- Can the quantified indicators be added to the manuscript to verify the robustness of the model?
- Sometimes unsubstantiated conclusions are used.
Authors’ response: We have made the appropriate corrections with the indications, the comparative analysis with related scientific works was extended, and a part regarding the verification of the model was added along with quantitative indicators. The conclusions section has been improved in terms of content and the whole work in terms of style. Those changes are highlighted within the revised manuscript file with tracked changes.
Minor comments:
- The figures in the manuscript are clear and consistent, however, please check the format of the titles of figure 4, figure 7, figure 8, figure 9, and figure11.
- Please check the title of table 2: ' Types of state and recurring tasks used by the model.' -> stateful. This paper was well written, but the above issues should be verified clearly.
Authors’ response: We made the necessary corrections. The methodology has been clarified and more precisely described. The analysis was extended based on new sources, including those indicated by other reviewers. Relevant paragraphs have been added for a clearer presentation of quantitative data together with an analysis of their implications. We have also reviewed the suggested bibliographic items and added them in the appropriate places, as well as other current references on the topic in question among scientific journals.
1. Zaydi, M. and Nassereddine, B. DevSecOps practices for an agile and secure it service management, J. Manag. Inf. Decis. Sci., 23 (2), 2020, pp. 1-16.
2. Akbar, M.A., Smolander, K., Mahmood S. and Alsanad A. Toward successful DevSecOps in software development organizations: A decision-making framework, Information and Software Technology, vol. 147, 2022, https://doi.org/10.1016/j.infsof.2022.106894.
3. Myrbakken, H. and Colomo-Palacios, R. DevSecOps: a multivocal literature review, Proceedings of the International Conference on Software Process Improvement and Capability Determination, Springer, 2017, pp. 17-29.
4. Mccallum, Andrew, and Kamal Nigam. Text Classification by Bootstrapping with Keywords, EM and Shrinkage, 17 August 2001.
5. Attri, R.; Grover, S.; Dev, N. and Kumar, D. Analysis of barriers of total productive maintenance (TPM), Int. J. Syst. Assur. Eng. Manag., 4 (4), 2013, pp. 365-377.
6. Akbar, M.A.; Sang, J.; Khan, A.A.; Mahmood, S.; Quadri S.F.; Hu, H. and Xiang H. Success factors influencing requirements change management process in global software development, J. Comput. Lang., 51, 2019, pp. 112-130.
We have incorporated all the suggestions made by the reviewers. Those changes are highlighted within the revised manuscript file with tracked changes.
Thanks again for the clear review and suggestions for corrections to improve our article.

Author Response File: Author Response.pdf

Reviewer 2 Report

the paper looks excellent and elaborates on an essential aspect of emerging technology. To improve the article, I suggest a deep proofreading of the paper with the intent to make the paper content more understandable with scientific language. 

There is a need to mention the scope of this paper in the last paragraph of the introduction section.

Furthermore, there is a need to elaborate on the practical implications of this research work, if suits give in conclusion section. 

To consider the references, authors should base their methodology using the references. Toward Successful DevSecOps in Software Development Organizations: A Decision-Making Framework, Prioritization based taxonomy of cloud-based outsource software development challenges: Fuzzy AHP analysis, SRCMIMM: the software requirements change management and implementation maturity model in the domain of global software development industry

 

 

Author Response

Dear Reviewer,
We would like to express our appreciation for the reviews. Thank you very much for suggestions, which were clear and very accurate. We made the necessary corrections. We have incorporated all the suggestions because we agreed with them, and thank you especially for such good suggestions to improve our article.
We would like to refer to the detailed reviewer’s suggestions below:

The paper looks excellent and elaborates on an essential aspect of emerging technology.

Authors’ response: Thank you for the positive reception of the article.

To improve the article, I suggest a deep proofreading of the paper with the intent to make the paper content more understandable with scientific language. There is a need to mention the scope of this paper in the last paragraph of the introduction section. Furthermore, there is a need to elaborate on the practical implications of this research work, if suits give in conclusion section.

Authors’ response: We made the necessary corrections: As suggested, the introductory part of the article has been revised and expanded to clearly define and present the purpose of the article. Changes were also made to the style of the entire article and it was sent to the translator to check the quality of the translation. The comparative analysis with related scientific works was extended, and a part regarding the verification of the model was added along with quantitative indicators. The conclusions section has been improved in terms of content and the whole work in terms of style. Those changes are highlighted within the revised manuscript file with tracked changes

To consider the references, authors should base their methodology using the references. Toward Successful DevSecOps in Software Development Organizations: A Decision-Making Framework, Prioritization based taxonomy of cloud-based outsource software development challenges: Fuzzy AHP analysis, SRCMIMM: the software requirements change management and implementation maturity model in the domain of global software development industry.

The analysis was extended based on new sources, including those indicated by other reviewers. Relevant paragraphs have been added for a clearer presentation of quantitative data together with an analysis of their implications. We have also reviewed the suggested bibliographic items and added them in the appropriate places, as well as other current references on the topic in question among scientific journals.

1. Zaydi, M. and Nassereddine, B. DevSecOps practices for an agile and secure it service management, J. Manag. Inf. Decis. Sci., 23 (2), 2020, pp. 1-16.
2. Akbar, M.A., Smolander, K., Mahmood S. and Alsanad A. Toward successful DevSecOps in software development organizations: A decision-making framework, Information and Software Technology, vol. 147, 2022, https://doi.org/10.1016/j.infsof.2022.106894.
3. Myrbakken, H. and Colomo-Palacios, R. DevSecOps: a multivocal literature review, Proceedings of the International Conference on Software Process Improvement and Capability Determination, Springer, 2017, pp. 17-29.
4. Mccallum, Andrew, and Kamal Nigam. Text Classification by Bootstrapping with Keywords, EM and Shrinkage, 17 August 2001.
5. Attri, R.; Grover, S.; Dev, N. and Kumar, D. Analysis of barriers of total productive maintenance (TPM), Int. J. Syst. Assur. Eng. Manag., 4 (4), 2013, pp. 365-377.
6. Akbar, M.A.; Sang, J.; Khan, A.A.; Mahmood, S.; Quadri S.F.; Hu, H. and Xiang H. Success factors influencing requirements change management process in global software development, J. Comput. Lang., 51, 2019, pp. 112-130.

We have incorporated all the suggestions made by the reviewers. Those changes are highlighted within the revised manuscript file with tracked changes.
Thanks again for the clear review and suggestions for corrections to improve our article.

Author Response File: Author Response.pdf