Advertisement

What Do Practitioners Vary in Using Scrum?

  • Philipp Diebold
  • Jan-Peter Ostberg
  • Stefan WagnerEmail author
  • Ulrich Zendler
Conference paper
Part of the Lecture Notes in Business Information Processing book series (LNBIP, volume 212)

Abstract

Background: Agile software development has become a popular way of developing software. Scrum is the most frequently used agile framework, but it is often reported to be adapted in practice. Objective: Thus, we aim to understand how Scrum is adapted in different contexts and what are the reasons for these changes. Method: Using a structured interview guideline, we interviewed ten German companies about their concrete usage of Scrum and analysed the results qualitatively. Results: All companies vary Scrum in some way. The least variations are in the Sprint length, events, team size and requirements engineering. Many users varied the roles, effort estimations and quality assurance. Conclusions: Many variations constitute a substantial deviation from Scrum as initially proposed. For some of these variations, there are good reasons. Sometimes, however, the variations are a result of a previous non-agile, hierarchical organisation.

Keywords

Agile processes Scrum variations Industrial case study 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Barabino, G., Grechi, D., Tigano, D., Corona, E., Concas, G.: Agile methodologies in web programming: a survey. In: Cantone, G., Marchesi, M. (eds.) XP 2014. LNBIP, vol. 179, pp. 234–241. Springer, Heidelberg (2014) Google Scholar
  2. 2.
    Callanan, M.: Ken schwaber on scrum (2010). http://blog.mattcallanan.net/2010/02/ken-schwaber-on-scrum.html
  3. 3.
    Diebold, P., Dahlem, M.: Agile practices in practice: a mapping study. In: Proc. 18th International Conference on Evaluation and Assessment in Software Engineering (EASE 2014). ACM (2014)Google Scholar
  4. 4.
    Diebold, P., Ostberg, J.-P., Wagner, S., Zendler, U.: Interview guidelines for “what do practitioners vary in using Scrum?”. doi: 10.5281/zenodo.12856
  5. 5.
    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) CrossRefGoogle Scholar
  6. 6.
    Fontana, R.M., Reinehr, S., Malucelli, A.: Maturing in agile: what is it about? In: Cantone, G., Marchesi, M. (eds.) XP 2014. LNBIP, vol. 179, pp. 94–109. Springer, Heidelberg (2014) Google Scholar
  7. 7.
    VersionOne Inc. 8th annual state of agile survey (2013). http://stateofagile.versionone.com/
  8. 8.
    Ionel, N.: Critical analysys of the Scrum project management methodology. Annals of the University of Oradea, Economic Science Series 17(4), 435–441 (2008)Google Scholar
  9. 9.
    Kniberg, H.: The unofficial Scrum checklist (2011). https://www.crisp.se/wp-content/uploads/2012/05/Scrum-checklist.pdf
  10. 10.
    Kniberg, H.: Scrum and XP from the trenches. Lulu.com (2007)Google Scholar
  11. 11.
    Kurapati, N., Manyam, V.S.C., Petersen, K.: Agile software development practice adoption survey. In: Wohlin, C. (ed.) XP 2012. LNBIP, vol. 111, pp. 16–30. Springer, Heidelberg (2012) CrossRefGoogle Scholar
  12. 12.
    Moe, N.B., Dingsøyr, S.: 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) CrossRefGoogle Scholar
  13. 13.
    Sutherland, J., Schwaber, K.: The Scrum guide: The definitive guide to Scrum: The rules of the game (2013). http://scrumguides.org

Copyright information

© Springer International Publishing Switzerland 2015

Authors and Affiliations

  • Philipp Diebold
    • 1
  • Jan-Peter Ostberg
    • 2
  • Stefan Wagner
    • 2
    Email author
  • Ulrich Zendler
    • 2
  1. 1.Fraunhofer Institute for Experimental Software Engineering IESEKaiserslauternGermany
  2. 2.University of StuttgartStuttgartGermany

Personalised recommendations