Examining the attributes of transitions between team roles in the software development projects
Keywords:project management, project team formation, Belbin team roles, Markov chains
In project management, efficiency of team performance is often associated with the balance in terms of its team roles. All explanations, however, as well as conclusions that relate to balancing a project team, were obtained verbally and are not confirmed either theoretically or empirically. Therefore, it is appropriate to examine the transitions between team roles based on mathematical modeling.
To understand regularities in the transitions of team members between team roles, we constructed a transition model based on the discrete Markov chain and defined parameters of the model. Using the simulation, we performed the study and demonstrated that it is natural for a software development project team to balance the team roles. This attribute does not depend on the initial composition of the team in terms of team roles. A difference in initial conditions only affects the rate of change in the probabilities of individual team roles, but the attribute of reducing the difference between the values of probabilities of individual team roles persists.
The results obtained confirm that by helping some team members to take on secondary roles to prevent the duplication of roles or to resolve certain problems, a project manager may influence the balancing of team in terms of team roles.
- Ebert, C., De Neve, P. (2001). Surviving global software development. IEEE Software, 18 (2), 62–69. doi: 10.1109/52.914748
- Belbin, R. M. (2010). Management Teams. Why They Succeed or Fail. Oxford: Butterworth-Heinemann, 208.
- Stevens, K. T. (1998). The Effects of Roles and Personality Characteristics on Software Development Team Effectiveness. Virginia: Blacksburg, 136.
- Ralph, P., Kelly, P. (2014). The dimensions of software engineering success. Proceedings of the 36th International Conference on Software Engineering – ICSE 2014. doi: 10.1145/2568225.2568261
- Syed-Abdullah, S.-L., Omar, M., Idris, M. F. I. M. (2011). Team achievements equality using fuzzy rule-based technique. World Applied Sciences Journal, 15 (3), 359–363.
- Beranek, G., Zuser, W., Grechenig, T. (2005). Functional group roles in software engineering teams. ACM SIGSOFT Software Engineering Notes, 30 (4), 1. doi: 10.1145/1082983.1083108
- Da Silva, F. Q. B., Cesar, A. C. F. (2009). An Experimental Research on the Relationships between Preferences for Technical Activities and Behavioural Profile in Software Development. 2009 XXIII Brazilian Symposium on Software Engineering. doi: 10.1109/sbes.2009.16
- Belbin, R. M. (2014). Method, reliability and validity, statistics and research: A comprehensive review of Belbin team roles. Belbin UK, 1–26. Available at: http://www.belbin.com/media/1158/belbin-uk-2014-a-comprehensive-review.pdf
- DeChurch, L. A., Mesmer-Magnus, J. R. (2010). The cognitive underpinnings of effective teamwork: A meta-analysis. Journal of Applied Psychology, 95 (1), 32–53. doi: 10.1037/a0017328
- Meslec, N., Curşeu, P. L. (2015). Are balanced groups better? Belbin roles in collaborative learning groups. Learning and Individual Differences, 39, 81–88. doi: 10.1016/j.lindif.2015.03.020
- Omar, M., Hasan, B., Ahmad, M., Yasin, A., Baharom, F., Mohd, H., Muhd Darus, N. (2016). Applying Fuzzy Technique in Software Team Formation Based on Belbin Team Role. Journal of Telecommunication, Electronic and Computer Engineering, 8 (8), 109–113.
- Aritzeta, A., Swailes, S., Senior, B. (2007). Belbin's Team Role Model: Development, Validity and Applications for Team Building. Journal of Management Studies, 44 (1), 96–118. doi: 10.1111/j.1467-6486.2007.00666.x
- Van de Water, T., van de Water, H., Bukman, C. (2007). A balanced team generating model. European Journal of Operational Research, 180 (2), 885–906. doi: 10.1016/j.ejor.2006.04.017
- Kemeni, Dzh., Snell, Dzh. (1970). Konechnye cepi Markova. Moscow: Nauka, 272.
- Turchin, V. N., Turchin, E. V. (2016). Markovskie cepi: Osnovnye ponjatija, primery, zadachi. Dnepropetrovsk: Lizunov Press, 192.
How to Cite
Copyright (c) 2017 Vira Liubchenko, Iuliia Sulimova
This work is licensed under a Creative Commons Attribution 4.0 International License.
The consolidation and conditions for the transfer of copyright (identification of authorship) is carried out in the License Agreement. In particular, the authors reserve the right to the authorship of their manuscript and transfer the first publication of this work to the journal under the terms of the Creative Commons CC BY license. At the same time, they have the right to conclude on their own additional agreements concerning the non-exclusive distribution of the work in the form in which it was published by this journal, but provided that the link to the first publication of the article in this journal is preserved.
A license agreement is a document in which the author warrants that he/she owns all copyright for the work (manuscript, article, etc.).
The authors, signing the License Agreement with PC TECHNOLOGY CENTER, have all rights to the further use of their work, provided that they link to our edition in which the work was published.
According to the terms of the License Agreement, the Publisher PC TECHNOLOGY CENTER does not take away your copyrights and receives permission from the authors to use and dissemination of the publication through the world's scientific resources (own electronic resources, scientometric databases, repositories, libraries, etc.).
In the absence of a signed License Agreement or in the absence of this agreement of identifiers allowing to identify the identity of the author, the editors have no right to work with the manuscript.
It is important to remember that there is another type of agreement between authors and publishers – when copyright is transferred from the authors to the publisher. In this case, the authors lose ownership of their work and may not use it in any way.