Reforming Performance Appraisal for Agile Software Development Projects

 
 
 
  • Abstract
  • Keywords
  • References
  • PDF
  • Abstract


    Changes in software development methods should lead to changes in an organization’s performance appraisal system. Several organizations, however, have adopted Agile software development methods without reforming their performance appraisal. Performance appraisal should be aligned to Agile values, principles, and practices, which advocate interactions, collaborations, teamwork, and knowledge transfer. Through a Grounded Theory study involving 48 Agile practitioners and external specialists, we discovered two major changes to performance appraisal for Agile teams: integrating individual and team performance assessment criteria, and shifting from quantitative to qualitative measurement of performance. Our findings indicate that reforming performance appraisal tends to influence successful expertise coordination in Agile teams. This study can be a baseline in generating an Agile-compliant performance appraisal to assess Agile team members in a fair and consistent manner. This indirectly increases motivation amongst team members and tends to produce capable workforce to perform at a higher level.

     

     


  • Keywords


    Agile-compliant performance appraisal, Agile Software Development, Grounded Theory.

  • References


      [1] G.A. Allan, “A critique of using grounded theory as a research method,” Electronic Journal of Business Research Methods 2, 1, 2003, pp. 1-10.

      [2] L. Alnaji, and H. Salameh, “Performance-measurement framework to evaluate software engineers for agile software-development methodology,” European Journal of Business and Management 7(2), 2015, pp. 183–190.

      [3] R. Ahmad, and S. Bujang, “Issues and challenges in thepractice of performance appraisal activities in the 21st century,” International Journal of Education and Research 1, 4, 2013, pp. 7.

      [4] J.M. Corbin, A. Strauss, “Grounded theory research: Procedures, canons, and evaluative criteria,”. Qualitative sociology 13, 1,1990, pp. 3-21.

      [5] S. Coyle and K. Conboy, “People over process: key people challenges in agile development.” IEEE, 2010.

      [6] S. Faraj, and L. Sproull, “Coordinating expertise in software development teams. Management Science,” 2000, pp. 1554-1568.

      [7] S.Noori, S.H. Hosseini, and A. Baksha, “Human performance factors in the evaluation of virtual organizations,” International Journal of Business and Management 4 (2), 41, 2009.

      [8] M. Birks, and J. Mills, “Grounded theory: a practical guide,” Sage Publications Limited, 2011.

      [9] B. Boehm, and S.K. Mobasser, “System thinking: educating tshaped software engineers,” In 2015 IEEE/ACM 37th IEEE International Conference on Software Engineering, vol. 2, 2015, pp. 333–342.

      [10] G. Bowen, “Document analysis as a qualitative research method,” Qualitative research journal 9, 2 2009, pp. 27–40.

      [11] K. Charmaz, “Constructing grounded theory: A practical guide through qualitative analysis,” Sage Publications Limited, 2006.

      [12] S. Coyle, and K. Conboy, “People over process: key people challenges in agile development,” IEEE ,2010.

      [13] J.W.Creswell, “Qualitative inquiry and research design: Choosing among five approaches,” Sage, 2012.

      [14] S. Denning, “Why agile can be a game changer for managing continuous innovation in many industries,” Strategy & Leadership 41, 2, 2013, pp. 5–11

      [15] S. Dorairaj, J. Noble, and G. Allan, “Agile software Development with distributed teams: Senior management support,” In Global Software Engineering (ICGSE), 2013 IEEE 8th International Conference on 2013, IEEE, pp. 197–205.

      [16] B.G. Glaser, “Emergence vs forcing: Basics of grounded theory analysis,” Sociology Press, 1992.

      [17] B.G. Glaser and A.L. Strauss, “The discovery of grounded theory: Strategies for qualitative research.,” Aldine de Gruyter, 1967.

      [18] R.Hoda, J. Noble, and S. Marshall, “Developing a grounded theory to explain the practices of self-organizing agile teams,” Empirical Software Engineering 17, 6, 2012, pp. 609–639.

      [19] B. Jackling, and C. Sullivan, “Financial planners in australia: an evaluation of gaps in technical and behavioral skills.,” Financial Services Review 16, 3, 2007, pp. 211.

      [20] M. Keith, M., Goul, H., Demikran, J., Nichols, and M.C. Mitchell, “Contextualizing knowledge management readiness to support change management strategies,” In Proceedings of the 39th Annual Hawaii International Conference on System Sciences (HICSS’06), vol. 7, IEEE, 2006, pp. 152a–152a.

      [21] J. Kirk, and M.L. Miller., “Reliability and validity in qualitative research,” Sage, 1986.

      [22] S. M. Kolb, “Grounded theory and the constant comparative method: valid research strategies for educators,” Journal of Emerging Trends in Educational Research and Policy Studies 3, 1 2012, pp. 83–86.

      [23] C. Kutay, and A. Aurum, “Knowledge transformation for education in software engineering,” International Journal of Mobile Learning and Organisation 1, 1 2006, pp. 58–80.

      [24] M.A. Lapham, “Dod agile adoption: Necessary considerations, concerns, and changes,” Tech. rep., DTIC Document, 2012.

      [25] S. Nerur, R., Mahapatra, and G. Mangalaraj, “Challenges of migrating to agile methodologies,” Communications of the ACM 48, 5, 2005, pp. 72–78.

      [26] T. Chow, and D. Cao, “A survey study of critical success factors in agile software projects,” Journal of Systems and Software 81, 6, 2008, pp. 961-971.

      [27] G. Lohan, K. Conboy, and M. Lang, “Beyond budgeting and agile software development: a conceptual framework for the performance management of agile software development teams,” In ICIS, 2010, pp. 162.

      [28] K.W. Parry, “Grounded theory and social process: A new direction for leadership research,” The Leadership Quarterly 9, 1, 1998, pp. 85–105.

      [29] R. Shakir, “Soft skills at the malaysian institutes of higher learning,” Asia Pacific Education Review 10, 3, 2009, pp. 309–315.

      [30] R.Shahkarmani, S. Mantha, and V. Babu, “Perforrmance assessment of ASD team using FPL football rules as reference,” In India Conference, 2011 Annual IEEE, 2011, IEEE, pp. 1–4.

      [31] J.F.Tripp, and C.K. Riemenschneider, “Toward an understanding of job satisfaction on agile teams: Agile development as work redesign,” In System Sciences (HICSS), 2014 47th Hawaii International Conference on, 2014, IEEE, pp. 3993–4002.

      [32] V. Vinekar, C.W. Slinkman, and S.Nerur, “Can agile and traditional systems development approaches coexist? an ambidextrous view,” Information systems management 23, 3, 2006, pp. 31–42.

      [33] M. Waterman, J. Noble and G. Allan, “How much up-front? A grounded theory of agile architecture,” In Software Engineering (ICSE), 2015 IEEE/ACM 37th IEEE International Conference, 2015, vol. 1, IEEE, pp. 347–357.

      [34] M.Rejab, J. Noble and G. Allan, “Distributing expertise in agile software development projects,” In Agile Conference (AGILE), 2014, IEEE, pp. 33–36.

      [35] M.Rejab, J. Noble, and G. Allan, “Locating expertise in agile software development projects,” In Agile Processes in Software Engineering and Extreme Programming. Springer, 2014, pp. 260–268.

      [36] Rejab, M. M., J. Noble, & S. Marshall, “Coordinating expertise outside agile teams,” In International Conference on Agile Software Development, Springer, Cham, 2015, pp. 141-153.

      [37] M.M. Rejab, “Expertise Coordination for Agile Software Development Projects:” A Thesis Submitted to the Victoria University of Wellington in Fulfilment of the Requirements for the Degree of Doctor of Philosophy in Software Engineering (Doctoral dissertation, Victoria University of Wellington), 2017.


 

View

Download

Article ID: 22056
 
DOI: 10.14419/ijet.v7i4.19.22056




Copyright © 2012-2015 Science Publishing Corporation Inc. All rights reserved.