Competency Profile for Software Development Team that Support Project Success

Tien Fabrianti Kusumasari (1), Bambang Riyanto Trilaksono (2), Atya Nur Aisha (3), - Fitria (4)
(1) Information System, School of Industrial Engineering, Telkom University, Bandung, Indonesia
(2) Electrical Engineering, School of Electrical Engineering and Informatics, Institut Teknologi Bandung, Bandung, Indonesia
(3) Industrial Engineering, School of Industrial Engineering, Telkom University, Bandung, Indonesia
(4) Informatic, School of Electrical Engineering and Informatics, Institut Teknologi Bandung, Bandung, Indonesia
Fulltext View | Download
How to cite (IJASEIT) :
Kusumasari, Tien Fabrianti, et al. “Competency Profile for Software Development Team That Support Project Success”. International Journal on Advanced Science, Engineering and Information Technology, vol. 10, no. 6, Dec. 2020, pp. 2244-50, doi:10.18517/ijaseit.10.6.11674.
The success of software development depends very much on the competencies possessed by human resources within the development team. These competencies include hard and soft skills. In this study, a team competency model will be proposed, which consists of the minimum competency level for the project manager, analyst, and programmer job roles. The types of competencies that are focused on in this paper consist of soft competencies and hard competencies. The method used to determine the competency model is to use the Focus Discussion Group (FGD) by adopting the Behavior Event Interview (BEI) technique. The result of FGD validates with expert judgments, questionnaires, and team member interviews. This research provides the results of profiling the competency of the software development team on project manager job analysts, analysts, and programmers. This study's competencies profile stated that the average minimum level of soft competency for project managers is 3, 3 for analysts, and 2 for programmers. In comparison, the average minimum level of hard competency for a project manager is 3, analyst 2, and programmer 2. Job Role for project managers requires high enough competence both in terms of technical (hard competency) and soft competency. A job as an Analyst requires a level of soft competence higher than hard competency. At the same time, the job role programmer requires soft and hard competency at a low level, 2. The results of this paper can be useful for the recruitment team to get the right individuals to ensure the success of the project.

E. Salas, N. J. Cooke and M. A. Rosen, "On Teams, Teamwork, and Team Performance: Discoveries and Developments," Human Factors: The Journal of the Human Factors and Ergonomics Society, p. 543, 2008.

M. H. N. M. Nasir and S. Sahibudin, "Critical success factors for software project: A Comparative study," Scientific research and essays, 2011.

D. Richard and J. B. Forman, "Seven causes of project failure," 2007. [Online]. Available: https://www.pmi.org/learning/library/seven-causes-project-failure-initiate-recovery-7195. [Accessed 12 Januari 2017].

Standish Group, "Chaos Report Worse Project Failure in Decade," Standish Group, 2015.

P. Holtkamp and J. M. Pawiowski, "A competence based view on the global software," Journal of universal computer science, 2015.

F. Lanubile, C. Ebert , R. Prikladnicki and A. Vizcaí­no, "Collaboration Tools for Global Software Engineering," IEEE Software, vol. 27, no. 2, pp. 52-55, 2010.

M. Farhangian, M. Purvis, M. Purvis and T. B. R. Savarimuthu, "Agent-Based Modeling of Resource Allocation in Software Projects Based on Personality and Skill," Communications in Computer and Information Science, pp. 130-146, 2015.

S. Cook, High Performance Team, United Kingdom: IT Governance Publishing, 2009.

P. Holtkamp, "Competency Requirements of Global Software Development Conceptualization, Contextualization, and Consequences," Journal of Universal Science, 2015.

P. Holtkamp, "A competence based view on the global software development process," Jpurnal of Universal Computer Science, 2015.

T. F. Kusumasari, B. R. Trilaksono, A. N. Aisya and Fitria, "Software Development Team Competencies to Support Software Development Project Success," International Journal of Engineering & Technology, vol. in process, no. in process, p. in process, 2018.

E. Moustroufas, I. Stamelos and L. Angelis, "Competency Profiling for Software Engineers: Literature Review and a new Model," in PCI '15 Proceedings of the 19th Panhellenic Conference on Informatics, Athens, 2015.

B. R. v. Konsky, D. Hay and B. Hart, "Skill Set Visualisation for Software Engineering Job Positions at Varying Levels of Autonomy and Responsibility," in Australian Software Engineering Conference, Australia, 2008.

E. S. Mtsweni, T. Hí¶rne and J. A. v. d. Poll, "Soft Skills for Software Project Team Members," International Journal of Computer Theory and Engineering, vol. 8, no. 2, 2016.

L. Markus, H. C. Thomas and N. K. Allpress, "Confounded by Competencies? An Evaluation of the Evolution and Use of competency model," New Zealand Journal of Psycology, 2005.

G. Kolibacova, "The Relationship Between Competency And Performance," ACTA Universitatis Agriculturae Et Silviculturae Mendelianae Brunensis, vol. 62, 2014.

J. G. Rivera-Ibara, J. Rodrí­guez-Jacobo, J. A. Ferní¡ndez-Zepeda and M. M. Serrano-Vargas, "Competency Framework for Software Engineers," in 23rd IEEE Conference on Software Engineering Education and Training, 2010.

J. R. Turner, A. Ledwith and J. Kelly, "Project management in small to medium-sized enterprises: A comparison between firms by size and industry," International Journal of Managing Projects in Business, vol. 2, no. 2, pp. 282-296, 2009.

Authors who publish with this journal agree to the following terms:

    1. Authors retain copyright and grant the journal right of first publication with the work simultaneously licensed under a Creative Commons Attribution License that allows others to share the work with an acknowledgement of the work's authorship and initial publication in this journal.
    2. Authors are able to enter into separate, additional contractual arrangements for the non-exclusive distribution of the journal's published version of the work (e.g., post it to an institutional repository or publish it in a book), with an acknowledgement of its initial publication in this journal.
    3. Authors are permitted and encouraged to post their work online (e.g., in institutional repositories or on their website) prior to and during the submission process, as it can lead to productive exchanges, as well as earlier and greater citation of published work (See The Effect of Open Access).