Luis G. Martínez, Juan R. Castro, Guillermo Licea, Antonio Rodríguez-Díaz, Carlos F. Alvarez


Nowadays organizations work to improve their software development process, with a purpose to reduce costs, improve quality and increase planning reliability. That is why decision making pertaining to role assignment in software engineering developing projects is one of the most important factors that affect the software development process in organizations. We should not only consider individual’s abilities and capabilities for better team performance but also consider knowing their personality traits to carry out the most suitable role in an effective working team. Through compilation of studies with RAMSET (Role Assignment Methodology for Software Engineering Teams) methodology some personalities and typologies have been identified to perform certain type of roles, thus helping us build a better, cohesive and less conflictive team. Our methodology based on personality has revealed appropriate and adequate personality patterns for assignment of best advisable performing roles in software development, according not only to capabilities of people and role demands but also taking into consideration personality traits, thus showing that knowing software engineer’s personality can improve software development process.


  1. Bernstein, A., Radosevich, D. J., Clesca, C. F., Lynn, J., (2008) Personality predictors of teamwork behaviors and decision-making style. Review of Business Research.
  2. Biffl, S., Halling, M. (2003) Investigating the Defect Detection Effectiveness and Cost Benefit of Nominal Inspection, In IEEE Transactions on SE (Vol. 29 no. 5, pp. 385-397).
  3. Calitz, A. P., Watson, M. B., Gideon, D. (1997) Identification and Selection of Successful Future IT Personnel in a Changing Technological and Business Environment. In ACM SIGCPR 97, San Francisco.
  4. Capretz, L. F. (2003) Personality types in software engineering Int. J. Human-Computer Studies, 58, 207-214, Elsevier Science Ltd.
  5. Costa Jr, P. R., McCrae, R. R. (1992) Revised NEO Personality Inventory (NEO-PI-R) and NEO FiveFactor Inventory (NEO-FFI) manual. Odessa, FL. Psychological Assessment Resources.
  6. DeMarco, T., Lister, T. (1999) Peopleware: Productive Projects and Teams 2nd edition. New York: Dorset House Publishing Co.
  7. Dubinsky, Y., Hazzan, O. (2006) Using a Roles Scheme to Derive Software Project Metrics, Journal of Systems Architecture 52(11), 693-699.
  8. Goldberg, L. R. (1993) The structure of phenotypic personality traits. American Psychologist, 48, 26-34.
  9. Goldstein, David K. (1988) An Updated Measure of Supervisor-rated Job Performance for Programmer/Analysts. In SIGCPR'88, ACM Digital Library.
  10. Gorla, N., Lam, Y. W., (2004) Who Should Work With Whom? Building Effective Software Project Teams, Communications of the ACM, (Vol. 47 No. 6, pp. 79- 82).
  11. Griffiths, R. (1988) Graphology: early recollections and the tree test. The Author West Vancouver British Columbia.
  12. Guinan, P. J., Cooprider, J. G., Faraj, S., (1998) Enabling Software Development Team Performance During Requirements Definition: A Behavioral Versus Technical Approach, Information Systems Research, 9(2), 101-125.
  13. Koch, K., (1986) El test del árbol: el dibujo del árbol como medio psicodiagnóstico auxiliar. Kapelusz, Buenos Aires
  14. Leaetta, M. H., Frederick, L. O. (2000). Personnel Selection: looking toward the future-remembering the past. Annual Reviews Psychology , 51, 631-664.
  15. Pittenger, D. J., (1993) The Utility of the Myers-Briggs Type Indicator. Review of Educational Research 63(4), 467-488.
  16. Rodríguez, J., (2004). Formación de grupos de desarrollo de software. Ediciones Yoltéotl.
  17. Rothstein, M., Goffin, G. R. D. (2006). The use of personality measures in personnel selection: What does current research support? Human Resource Management Review, 16(2), 155-180.
  18. Smith, D. C., Bwecher, M., Burns-Howell, J., Kyriakides, J., (2001) Creating High performance IS Teams, In SAICSIT, Pretoria South Africa.
  19. Soley, L., Smith, A. L. (2008). Projective Techniques for Social Science and Business Research. Milwaukee: The Southshore Press.
  20. Teague, J., (2002) Women in Computing: What brings them to it, what keeps them in it? in SIGCSE (Vol. 34 no. 2, pp. 147-158).
  21. Tomayko, J. E. (1996) Teaching a Project-Intensive Introduction to Software Engineering, SEI Carnegie Mellon University Tech. Rep., Pittsburgh Pennsylvania.
  22. Tupes, E. C., Christal, R. E., (1992) Recurrent Personality Factors Based on Trait Ratings. Journal of Personality, 60, 225-251.

Paper Citation

in Harvard Style

Martínez L., Castro J., Licea G., Rodríguez-Díaz A. and Alvarez C. (2011). KNOWING SOFTWARE ENGINEER’S PERSONALITY TO IMPROVE SOFTWARE DEVELOPMENT . In Proceedings of the 6th International Conference on Software and Database Technologies - Volume 2: ICSOFT, ISBN 978-989-8425-77-5, pages 99-104. DOI: 10.5220/0003446300990104

in Bibtex Style

author={Luis G. Martínez and Juan R. Castro and Guillermo Licea and Antonio Rodríguez-Díaz and Carlos F. Alvarez},
booktitle={Proceedings of the 6th International Conference on Software and Database Technologies - Volume 2: ICSOFT,},

in EndNote Style

JO - Proceedings of the 6th International Conference on Software and Database Technologies - Volume 2: ICSOFT,
SN - 978-989-8425-77-5
AU - Martínez L.
AU - Castro J.
AU - Licea G.
AU - Rodríguez-Díaz A.
AU - Alvarez C.
PY - 2011
SP - 99
EP - 104
DO - 10.5220/0003446300990104