Preliminary Study of Methodology on the Impact of Different Teamwork Skill Levels on the Efficiency on the Software Development Workflow Based on Industry in Malaysia

  • Authors

    • Zairina Ibrahim
    • Md Gapar Md Johar
    • Normy Rafida Abdul Rahman
    2018-11-30
    https://doi.org/10.14419/ijet.v7i4.28.22640

  • The software development life cycle (SDLC) is the important element in software development. In fact, there are needs to upgrade the sequence of methodology in software development. The SDLC methodology is the highest level of abstraction and is defined as a collection of problem-solving methods governed by a set of principles and common philosophies in solving targeted problems for extended project timeline teamwork as well as a decrease of a high team collaboration and understanding in the software development. Thus, the SDLC is very crucial in order for them to ensure the quality of skills is placed accordingly in the workflow. This research contributes to the development of a new approach in system development workflow with the aim to properly manage system development projects. It started by providing some background data related to the previous mode of operation in the teamwork samples as shared by the stakeholders of the transformation projects and the new proposed Analysis System Development Framework (ASDF) method team members. Then, the key findings related to themes of 1) input for User Requirement Specification (URS) and 2) System Requirement Specification (SRS), 3) proses for module, 4) process for database, 5) process for User Acceptance Testing (UAT) 6) output for Final Acceptance Testing (FAT) and empowerment for the whole level based on ASDF method. This research contributes mainly to the findings, more than previous research has found, that significantly support the perception that a high quality of skills in a teamwork results in better performance of software development.

  • References

    1. [1] Agarwal, N., and Rathod, U., 2006. Defining success for software projects: An exploratory revelation. International Journal of Project agile transformation. Information and Software Technology 53(3). 276–290.

      [2] Ali, Munassar, N., M., and Govardhan, A., 2010. A Comparison Between Five Models of Software Engineering. IJCSI, Vol.7, Issue5. approach with agile practices, Empire Software Engineering 15:654– 693. Approaches School of Engineering and Information Technology Universiti Malaysia Sabah, Malaysia. between two new product development teams. Management Science, 38(3), 360-373.

      [3] Bacon, N., and Blyton, P. (2006). Union co - operation in a context of job insecurity:

      [4] Cockburn., A., and Highsmith, J., 2001. Agile software development: The people factor. Software Management, 34(11), 131-133.

      [5] Mulika. (2010). The Impact of Teamwork on Employee Performance in Strategic Management and the Performance Improvement Department of Abu Dhabi Police, UAE.

      [6] Pfaff, E., and P. Huddleston. (2003). Does it matter if I hate teamwork? What impacts student attitudes toward teamwork. Journal of Marketing Education25:37–45.

      [7] Froebel, P., and Marchington, M. (2005). Teamwork structures and worker perception: a cross na tional study in pharmaceuticals , International Journal of Human Resource Management, 16(2), 256 - 276.

      [8] Ingram, H. (2000). Lin king teamwork with performance. Journal of Team Performance Management, 2( 4 ), 5 - 10.

      [9] Washer P. Designing a system for observation of teaching. Quality Assurance in Education. 2006 Jul 1;14(3):243-50.

      [10] Conti, B., and Kleiner, B. (2003). How to incr ease teamwork in organizations. Journal of Quality, 5( 1 ), 26 - 29.

      [11] Langfred, C. W. (2000). The paradox of selfâ€management: Individual and group autonomy in work groups. Journal of Organizational Behavior, 21(5), 563-585.

      [12] Hoegl, M., & Gemuenden, H. G. (2001). Teamwork quality and the success of innovative projects: A theoretical concept and empirical evidence. Organization science, 12(4), 435-449.

      [13] Salas E, Sims DE, Burke CS. Is there a “big five†in teamwork?. Small group research. 2005 Oct;36(5):555-99.

      [14] Dickinson, T.L., and McIntyre, R.M. 1997. "A Conceptual Framework of Teamwork Measurement," in Team Performance Assessment and Measurement: Theory, Methods, and Applications,M.T. Brannick, E. Salas and C. Prince (eds.). NJ: Psychology Press, pp. 19–43.

      [15] Kraut, R.E., Streeter, L.A.: Coordination in software development. Commun. ACM 38(3), 69–81 (1995)

      [16] Diefenbach GJ, Reitman D, Williamson DA. Trichotillomania: a challenge to research and practice. Clinical Psychology Review. 2000 Apr 1;20(3):289-309.

      [17] Dingsoyr, T., and Lindsjorn, Y., 2013. Team Performance in a agile development teams: findings from 18 focus groups. Agile Process in Software Engineering and Extreme Programming, 14th International Conference, XP 2013, Vienna, Austria, June 3-7. Proceedings, 40-60, doi: 10.1007/978-3-642-38314-4-4.

      [18] Dyba, T., & Dingsoyr, T. (2008). Empiric.al studies of agile software development: A systematic review. Information and software technology, 50(9), 833-859.

      [19] Stray, V. G., Moe, N. B., & Dingsøyr, T. (2011, May). Challenges to teamwork: a multiple case study of two agile teams. In International Conference on Agile Software Development (pp. 146-161). Springer, Berlin, Heidelberg.

      [20] Rodd, H., Wray, A., Wilson, N. H., & Hosey, M. T. (2006). Treatment planning for the developing dentition. Quintessence.

      [21] Liang, T. P., Wu, J. C. H., Jiang, J. J., & Klein, G. (2012). The impact of value diversity on information system development projects. International Journal of Project Management, 30(6), 731-739.

      [22] Henderson, J. C., & Lee, S. (1992). Managing I/S design teams: a control theories perspective. Management science, 38(6), 757-777.

      [23] The Standish Group (2009). Chaos Summary Report: The 10 laws of CHAOS. Technical Report. Boston, MA: The Standish Group International.

      [24] Faraj, S., & Sproull, L. (2000). Coordinating expertise in software development teams. Management Science, 46(12), 1554-1568.

      [25] Khalaf, S. J., & Al-Jedaiah, M.N. (2008). Software Quality and Assurance in Waterfall Model and XP A Comparatice Study. Iss 2, Vol 7.

      [26] Highsmith, J., (2002). Agile Software Development Ecosystems. The Agile Software Development Series, ed. Boston, MA: Addison-Wesley.

      [27] Wateridge, J. (1995). IT Projects: A Basis for Success. International Journal of Project Management, 13(3), 169-172.

      [28] Alie, R.E., Beam, H., & Carey, T.A. (1998). The use of teams in an undergraduate management program. Journal of Management Education, 22(6), 707-19.

      [29] Hartenian, L. S. (2003). Team member acquisition of team knowledge, skills, and abilities. Team Performance Management: An International Journal, 9(1/2), 23-30.

      [30] Jones, A., Richard, B., Paul, D., Sloane, K., and Peter, F., 2007. Effectiveness of teambuilding in organization. Journal of Management, 5(3), 35-37.

      [31] Yu Beng Leau, Wooi Khong Loo, Wai Yip Tham & Soo Fun Tan. (2012). Software Development Life Cycle Agile vs Traditional Approaches School of Engineering and Information Technology University Malaysia Sabah, Malaysia.

      [32] Deepshikha, J., (2010). Analysis of Software Quality Models for Organizations University of Jammu Department of Computer Science & IT.

      [33] Linda, R., & Norman, S. J., (2000). The Scrum Software Development Process for Small Teams. AG Communication Systems.

  • Downloads

  • How to Cite

    Ibrahim, Z., Johar, M. G. M., & Rahman, N. R. A. (2018). Preliminary Study of Methodology on the Impact of Different Teamwork Skill Levels on the Efficiency on the Software Development Workflow Based on Industry in Malaysia. International Journal of Engineering & Technology, 7(4.28), 510-514. https://doi.org/10.14419/ijet.v7i4.28.22640