Advertisement

A Study of the Scrum Master’s Role

  • John Noll
  • Mohammad Abdur Razzak
  • Julian M. Bass
  • Sarah Beecham
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 10611)

Abstract

Scrum is an increasingly common approach to software development adopted by organizations around the world. However, as organizations transition from traditional plan-driven development to agile development with Scrum, the question arises as to which Scrum role (Product Owner, Scrum Master, or Scrum Team Member) corresponds to a Project Manager, or conversely which Scrum role should the Project Managers adopt?

In an attempt to answer this question, we adopted a mixed-method research approach comprising a systematic literature review and a case study of a commercial software development team. Our research has identified activities that comprise the Scrum Master role, and which additional roles are actually performed by Scrum Masters in practice.

We found ten activities that are performed by Scrum Masters. In addition, we found that Scrum Masters also perform other roles, most importantly as Project Managers. This latter situation results in tension and conflict of interest that could have a negative impact on the performance of the team as a whole.

These results point to the need to re-assess the role of Project Managers in organizations that adopt Scrum as a development approach. We hypothesize that it might be better for Project Managers to become Product Owners, as aspects of this latter role are more consistent with the traditional responsibilities of a Project Manager .

Keywords

Agile software development Scrum Scrum Master role Empirical software engineering 

Notes

Acknowledgments

We thank the members of TeamA and members of the Project Management Team for their generous and thoughtful collaboration on this study, and PracMed, for allowing us to study their software development efforts. This work was supported, in part, by Science Foundation Ireland grants 10/CE/I1855 and 13/RC/2094 to Lero - the Irish Software Research Centre (www.lero.ie).

References

  1. 1.
    Schwaber, K.: SCRUM development process. In: Sutherland, J., Casanave, C., Miller, J., Patel, P., Hollowell, G. (eds.) Business Object Design and Implementation, OOPSLA 1995 Workshop Proceedings, pp. 117–134. Springer, London (1995)Google Scholar
  2. 2.
    Schwaber, K., Beedle, M.: Agile software Development with Scrum, vol. 1. Prentice Hall Upper Saddle River, NJ (2002)MATHGoogle Scholar
  3. 3.
    VERSIONONE.COM: 11th annual state of agile™ survey. Technical report, VersionOne, Inc. (2017)Google Scholar
  4. 4.
    Schwaber, K.: Agile Project Management with Scrum. Microsoft press, WA (2004)MATHGoogle Scholar
  5. 5.
    Cohn, M., Schwaber, K.: The need for agile project management. Agile Times, vol. 1, January 2003Google Scholar
  6. 6.
    Bass, J.M.: Scrum master activities: process tailoring in large enterprise projects. In: 2014 IEEE 9th International Conference on Global Software Engineering (ICGSE), pp. 6–15. IEEE (2014)Google Scholar
  7. 7.
    Schwaber, K., Sutherland, J.: The Scrum guide-the definitive guide to Scrum: The rules of the game (2016). http://www.scrum.org/storage/scrumguides/Scrum%20Guide
  8. 8.
    Gupta, R.K., Reddy, P.M.: Adapting agile in a globally distributed software development. In: 2016 49th Hawaii International Conference on System Sciences (HICSS), pp. 5360–5367, January 2016Google Scholar
  9. 9.
    ISO/IEC/IEEE: Systems and software engineering - developing user documentation in an agile environment. Technical report, International Standards Organization, March 2012Google Scholar
  10. 10.
    Tengshe, A., Noble, S.: Establishing the agile PMO: managing variability across projects and portfolios. In: Agile 2007 (AGILE 2007), pp. 188–193, August 2007Google Scholar
  11. 11.
    Paasivaara, M., Lassenius, C.: Scaling Scrum in a large distributed project. In: 2011 International Symposium on Empirical Software Engineering and Measurement, pp. 363–367, September 2011Google Scholar
  12. 12.
    Paasivaara, M., Lassenius, C.: Scaling Scrum in a large globally distributed organization: a case study. In: 2016 IEEE 11th International Conference on Global Software Engineering (ICGSE), pp. 74–83, August 2016Google Scholar
  13. 13.
    Stray, V.G., Lindsjorn, Y., Sjoberg, D.I.: Obstacles to efficient daily meetings in agile development projects: a case study. In: 2013 ACM/IEEE International Symposium on Empirical Software Engineering and Measurement, pp. 95–102. IEEE (2013)Google Scholar
  14. 14.
    Moe, N.B., Dingsyr, T., Dyb, T.: Understanding self-organizing teams in agile software development. In: 19th Australian Conference on Software Engineering (ASWEC 2008), pp. 76–85, March 2008Google Scholar
  15. 15.
    Shastri, Y., Hoda, R., Amor, R.: Does the project manager still exist in agile software development projects? In: 2016 23rd Asia-Pacific Software Engineering Conference (APSEC), pp. 57–64, December 2016Google Scholar
  16. 16.
    Berczuk, S., Lv, Y.: We’re all in this together. IEEE Softw. 27(6), 12–15 (2010)CrossRefGoogle Scholar
  17. 17.
    Sutherland, J.V., Schwaber, K.: Business object design and implementation: OOPSLA 1995 workshop proceedings. The University of Michigan. Technical report (1995). ISBN 3-540-76096-2Google Scholar
  18. 18.
    Creswell, J.W.: Research Design: Qualitative, Quantitative, and Mixed Methods Approaches, 4th edn. SAGE Publications Inc., Thousand Oaks, California (2013)Google Scholar
  19. 19.
    Kitchenham, B., Charters, S.: Guidelines for performing systematic literature reviews in software engineering, v. 2.3. Technical report EBSE-2007-01, Software Engineering Group, School of Computer Science and Mathematics, Keele University (2007)Google Scholar
  20. 20.
    Beecham, S., Noll, J., Razzak, M.A.: Lean global project interview protocol (2017). http://www.lero.ie/sites/default/files/Lero_TR_2017_02_Beecham_Noll_Razzak-Lean%20Global%20Project%20Interview%20Protocol.pdf
  21. 21.
    Braun, V., Clarke, V.: Using thematic analysis in psychology. Qual. Res. Psychol. 3(2), 77–101 (2006)CrossRefGoogle Scholar
  22. 22.
    Andriyani, Y., Hoda, R., Amor, R.: Reflection in agile retrospectives. In: Baumeister, H., Lichter, H., Riebisch, M. (eds.) XP 2017. LNBIP, vol. 283, pp. 3–19. Springer, Cham (2017). doi: 10.1007/978-3-319-57633-6_1CrossRefGoogle Scholar
  23. 23.
    Baumgart, R., Hummel, M., Holten, R.: Personality traits of Scrum roles in agile software development teams-a qualitative analysis. In: ECIS (2015)Google Scholar
  24. 24.
    Costa, N., Santos, N., Ferreira, N., Machado, R.J.: Delivering user stories for implementing logical software architectures by multiple Scrum teams. In: Murgante, B., et al. (eds.) ICCSA 2014. LNCS, vol. 8581, pp. 747–762. Springer, Cham (2014). doi: 10.1007/978-3-319-09150-1_55CrossRefGoogle Scholar
  25. 25.
    Dorairaj, S., Noble, J., Malik, P.: Understanding team dynamics in distributed agile software development. In: Wohlin, C. (ed.) XP 2012. LNBIP, vol. 111, pp. 47–61. Springer, Heidelberg (2012). doi: 10.1007/978-3-642-30350-0_4CrossRefGoogle Scholar
  26. 26.
    Alzoubi, Y.I., Gill, A.Q., Al-Ani, A.: Empirical studies of geographically distributed agile development communication challenges: a systematic review. Inf. Manag. 53(1), 22–37 (2016)CrossRefGoogle Scholar
  27. 27.
    Maranzato, R.P., Neubert, M., Herculano, P.: Moving back to Scrum and scaling to Scrum of Scrums in less than one year. In: Proceedings of the ACM International Conference Companion on Object Oriented Programming Systems Languages and Applications Companion, pp. 125–130. ACM (2011)Google Scholar
  28. 28.
    Bless, M.: Distributed meetings in distributed teams. In: Sillitti, A., Martin, A., Wang, X., Whitworth, E. (eds.) XP 2010. LNBIP, vol. 48, pp. 251–260. Springer, Heidelberg (2010). doi: 10.1007/978-3-642-13054-0_27CrossRefGoogle Scholar
  29. 29.
    Cajander, Å., Larusdottir, M., Gulliksen, J.: Existing but not explicit - the user perspective in Scrum projects in practice. In: Kotzé, P., Marsden, G., Lindgaard, G., Wesson, J., Winckler, M. (eds.) INTERACT 2013. LNCS, vol. 8119, pp. 762–779. Springer, Heidelberg (2013). doi: 10.1007/978-3-642-40477-1_52CrossRefGoogle Scholar
  30. 30.
    Gulliksen Stray, V., Moe, N.B., Dingsøyr, T.: Challenges to teamwork: a multiple case study of two agile teams. In: Sillitti, A., Hazzan, O., Bache, E., Albaladejo, X. (eds.) XP 2011. LNBIP, vol. 77, pp. 146–161. Springer, Heidelberg (2011). doi: 10.1007/978-3-642-20677-1_11CrossRefGoogle Scholar
  31. 31.
    Drury, M., Conboy, K., Power, K.: Obstacles to decision making in agile software development teams. J. Syst. Softw. 85(6), 1239–1254 (2012)CrossRefGoogle Scholar
  32. 32.
    Heikkilä, V.T., Paasivaara, M., Rautiainen, K., Lassenius, C., Toivola, T., Järvinen, J.: Operational release planning in large-scale Scrum with multiple stakeholders-a longitudinal case study at f-secure corporation. Inf. Softw. Technol. 57, 116–140 (2015)CrossRefGoogle Scholar
  33. 33.
    Vlietland, J., van Vliet, H.: Towards a governance framework for chains of Scrum teams. Inf. Softw. Technol. 57, 52–65 (2015)CrossRefGoogle Scholar
  34. 34.
    Chamberlain, S., Sharp, H., Maiden, N.: Towards a framework for integrating agile development and user-centred design. In: Abrahamsson, P., Marchesi, M., Succi, G. (eds.) XP 2006. LNCS, vol. 4044, pp. 143–153. Springer, Heidelberg (2006). doi: 10.1007/11774129_15CrossRefGoogle Scholar
  35. 35.
    Stray, V., Fægri, T.E., Moe, N.B.: Exploring norms in agile software teams. In: Abrahamsson, P., Jedlitschka, A., Nguyen Duc, A., Felderer, M., Amasaki, S., Mikkonen, T. (eds.) PROFES 2016. LNCS, vol. 10027, pp. 458–467. Springer, Cham (2016). doi: 10.1007/978-3-319-49094-6_31CrossRefGoogle Scholar
  36. 36.
    Daneva, M., Van Der Veen, E., Amrit, C., Ghaisas, S., Sikkel, K., Kumar, R., Ajmeri, N., Ramteerthkar, U., Wieringa, R.: Agile requirements prioritization in large-scale outsourced system projects: an empirical study. J. Syst, Softw. 86(5), 1333–1353 (2013)CrossRefGoogle Scholar
  37. 37.
    Alaa, G., Samir, Z.: A multi-faceted roadmap of requirements traceability types adoption in Scrum: an empirical study. In: 2014 9th International Conference on Informatics and Systems (INFOS), p. SW-1. IEEE (2014)Google Scholar
  38. 38.
    Baskerville, R., Pries-Heje, J., Madsen, S.: Post-agility: what follows a decade of agility? Inf. Softw. Technol. 53(5), 543–555 (2011)CrossRefGoogle Scholar
  39. 39.
    Caballero, E., Calvo-Manzano, J.A., San Feliu, T.: Introducing scrum in a very small enterprise: a productivity and quality analysis. In: O‘Connor, R.V., Pries-Heje, J., Messnarz, R. (eds.) EuroSPI 2011. CCIS, vol. 172, pp. 215–224. Springer, Heidelberg (2011). doi: 10.1007/978-3-642-22206-1_19CrossRefGoogle Scholar
  40. 40.
    Santos, R., Flentge, F., Begin, M.-E., Navarro, V.: Agile technical management of industrial contracts: scrum development of ground segment software at the european space agency. In: Sillitti, A., Hazzan, O., Bache, E., Albaladejo, X. (eds.) XP 2011. LNBIP, vol. 77, pp. 290–305. Springer, Heidelberg (2011). doi: 10.1007/978-3-642-20677-1_21CrossRefGoogle Scholar
  41. 41.
    Bass, J.M.: How product owner teams scale agile methods to large distributed enterprises. Empirical Softw. Eng. 20(6), 1525–1557 (2015)CrossRefGoogle Scholar
  42. 42.
    Gren, L., Torkar, R., Feldt, R.: Group development and group maturity when building agile teams: a qualitative and quantitative investigation at eight large companies. J. Syst. Softw. 124, 104–119 (2017)CrossRefGoogle Scholar
  43. 43.
    Hoda, R., Murugesan, L.K.: Multi-level agile project management challenges: a self-organizing team perspective. J. Syst. Softw. 117, 245–257 (2016)CrossRefGoogle Scholar
  44. 44.
    Tuomikoski, J., Tervonen, I.: Absorbing software testing into the Scrum method. In: Bomarius, F., Oivo, M., Jaring, P., Abrahamsson, P. (eds.) PROFES 2009. LNBIP, vol. 32, pp. 199–215. Springer, Heidelberg (2009). doi: 10.1007/978-3-642-02152-7_16CrossRefGoogle Scholar
  45. 45.
    Stray, V., Sjøberg, D.I., Dybå, T.: The daily stand-up meeting: a grounded theory study. J. Syst. Softw. 114, 101–124 (2016)CrossRefGoogle Scholar
  46. 46.
    Moe, N.B., Dingsøyr, T.: Scrum and team effectiveness: theory and practice. In: Abrahamsson, P., Baskerville, R., Conboy, K., Fitzgerald, B., Morgan, L., Wang, X. (eds.) XP 2008. LNBIP, vol. 9, pp. 11–20. Springer, Heidelberg (2008). doi: 10.1007/978-3-540-68255-4_2CrossRefGoogle Scholar
  47. 47.
    Díaz, J., Pérez, J., Garbajosa, J.: Agile product-line architecting in practice: a case study in smart grids. Inf. Softw. Technol. 56(7), 727–748 (2014)CrossRefGoogle Scholar
  48. 48.
    Sekitoleko, N., Evbota, F., Knauss, E., Sandberg, A., Chaudron, M., Olsson, H.H.: Technical dependency challenges in large-scale agile software development. In: Cantone, G., Marchesi, M. (eds.) XP 2014. LNBIP, vol. 179, pp. 46–61. Springer, Cham (2014). doi: 10.1007/978-3-319-06862-6_4CrossRefGoogle Scholar
  49. 49.
    Diebold, P., Ostberg, J.-P., Wagner, S., Zendler, U.: What do practitioners vary in using Scrum? In: Lassenius, C., Dingsøyr, T., Paasivaara, M. (eds.) XP 2015. LNBIP, vol. 212, pp. 40–51. Springer, Cham (2015). doi: 10.1007/978-3-319-18612-2_4CrossRefGoogle Scholar
  50. 50.
    Garbajosa, J., Yagüe, A., Gonzalez, E.: Communication in agile global software development: an exploratory study. In: Meersman, R., Panetto, H., Mishra, A., Valencia-García, R., Soares, A.L., Ciuciu, I., Ferri, F., Weichhart, G., Moser, T., Bezzi, M., Chan, H. (eds.) OTM 2014. LNCS, vol. 8842, pp. 408–417. Springer, Heidelberg (2014). doi: 10.1007/978-3-662-45550-0_41CrossRefGoogle Scholar
  51. 51.
    Li, J., Moe, N.B., Dybå, T.: Transition from a plan-driven process to Scrum: a longitudinal case study on software quality. In: Proceedings of the 2010 ACM-IEEE international symposium on empirical software engineering and measurement, p. 13. ACM (2010)Google Scholar
  52. 52.
    Galster, M., Angelov, S., Meesters, M., Diebold, P.: A multiple case study on the architect’s role in Scrum. In: Abrahamsson, P., Jedlitschka, A., Nguyen Duc, A., Felderer, M., Amasaki, S., Mikkonen, T. (eds.) PROFES 2016. LNCS, vol. 10027, pp. 432–447. Springer, Cham (2016). doi: 10.1007/978-3-319-49094-6_29CrossRefGoogle Scholar
  53. 53.
    Alahyari, H., Svensson, R.B., Gorschek, T.: A study of value in agile software development organizations. J. Syst. Softw. 125, 271–288 (2017)CrossRefGoogle Scholar
  54. 54.
    Vlaanderen, K., van Stijn, P., Brinkkemper, S., van de Weerd, I.: Growing into agility: process implementation paths for Scrum. In: Dieste, O., Jedlitschka, A., Juristo, N. (eds.) PROFES 2012. LNCS, vol. 7343, pp. 116–130. Springer, Heidelberg (2012). doi: 10.1007/978-3-642-31063-8_10CrossRefGoogle Scholar
  55. 55.
    Leffingwell, D.: Scaling software agility: Best practices for large enterprises. Addison Wesley, Boston (2007)Google Scholar

Copyright information

© Springer International Publishing AG 2017

Authors and Affiliations

  • John Noll
    • 1
  • Mohammad Abdur Razzak
    • 2
  • Julian M. Bass
    • 3
  • Sarah Beecham
    • 2
  1. 1.University of East LondonLondonUK
  2. 2.Lero, The Irish Software Research CentreUniversity of LimerickLimerickIreland
  3. 3.University of SalfordSalfordUK

Personalised recommendations