International Conference on Software Quality

Software Quality. The Future of Systems- and Software Development pp 17-36 | Cite as

How Scrum Tools May Change Your Agile Software Development Approach

Conference paper
Part of the Lecture Notes in Business Information Processing book series (LNBIP, volume 238)


A major problem for distributed Scrum teams is proper communication between the involved parties to ensure the quality of the final product. This is especially true for coordination issues such as sharing requirements, time schedules, to-dos and code artefacts. Hence, ScrumMasters complain frequently about software tools not suiting their daily needs when supporting agile teamwork, finally leading to the fact of not using a Scrum tool at all. In this paper we describe the extensive interviews held with selected ScrumMasters in which they explained their current tools and the existing gap to their real needs. Within this context, they were able to define the features and aspects they really need. After collecting those requirements for their daily work, we extracted the most wanted ingredients, prioritised them and finally forged them into an Open Source tool called Scrumpy, helping us to present a first solution, which focuses on the agile philosophy of Scrum and the elements needed most by ScrumMasters. Features of Scrumpy include, for example, web-based access to the task board with real-time updates, advanced dashboard visualisation techniques and a sophisticated chat system, which enables effortless communication for distributed teams. Although we already have first anecdotal feedback from users, we plan to improve the tool in a next step by adding more commodity features, perform additional mobile usability tests and systematically evaluate Scrumpy with a large number of end users.


Scrum tools Scrum Agile software development   Distributed Scrum Scrum task board 


  1. 1.
    The Standish Group International. CHAOS MANIFESTO 2013 - Think Big, Act Small (2013).
  2. 2.
    Azizyan, G., Magarian, M.K., Kajko-Mattson, M.: Survey of agile tool usage and needs. In: Agile Conference 2011, AGILE 2011, pp. 29–38. IEEE Computer Society, August 2011. doi: 10.1109/AGILE.2011.30. ISBN: 978-0-7695-4370-3
  3. 3.
    Heller, R., Laurito, A., Johnson, K., Martin, M., Fitzpatrick, R., Sundin, K.: Global teams: trends, challenges and solutions. In: Cornell Center for Advanced Human Resource Studies. Partner Meeting, CAHRS 2010, May 2010.
  4. 4.
    Damian, D., Lassenius, C., Paasivaara, M., Borici, A., Schroter, A.: Teaching a globally distributed project course using scrum practices. In: Proceedings of 2nd Workshop on Collaborative Teaching of Globally Distributed Software Development, CTGDSD 2012, pp. 30–34. IEEE Computer Society (2012). doi: 10.1109/CTGDSD.2012.6226947. ISBN: 978-1-4673-1818-1
  5. 5.
    Moe, N.B., Dingsoyr, T., Dybå, T.: Overcoming barriers to self-management in software teams. IEEE Softw. 26(6), 20–26 (2009). doi: 10.1109/MS.2009.182 CrossRefGoogle Scholar
  6. 6.
    Scissors, L., Shami, N.S., Ishihara, T., Rohall, S., Saito, S.: Realtime collaborative editing behavior in USA and Japanese distributed teams. In: Proceedings of the SIGCHI Conference on Human Factors in Computing Systems, CHI 2011, Vancouver, BC, Canada, pp. 1119–1128. ACM (2011). doi: 10.1145/1978942.1979109. ISBN: 978-1-4503-0228-9
  7. 7.
    Rayhan, S.H., Haque, N.: Incremental adoption of scrum for successful delivery of an IT project in a remote setup. In: Melnik, G., Kruchten, P., Poppendieck, M. (eds.) Agile 2008 Conference, AGILE 2008, pp. 351–355. IEEE Computer Society, August 2008. doi: 10.1109/Agile.2008.98
  8. 8.
    Sarkan, H., Ahmad, T., Bakar, A.: Using JIRA and redmine in requirement development for agile methodology. In: 2011 5th Malaysian Conference Software Engineering (MySEC), pp. 408–413, December 2011. doi: 10.1109/MySEC.2011.6140707
  9. 9.
    Perry, T.: Drifting toward invisibility: the transition to the electronic task board. In: Agile, AGILE 2008, Conference, pp. 496–500, August 2008. doi: 10.1109/Agile.2008.62
  10. 10.
    Berczuk, S.: Back to basics: the role of agile principles in success with an distributed scrum team. In: Agile Conference (AGILE), pp. 382–388, August 2007. doi: 10.1109/AGILE.2007.17
  11. 11.
    Segers, J.: Analysis of a paper-and software-based scrum task board. M.A. thesis. Universiteit Twente, September 2012.
  12. 12.
    Uy, E., Rosendahl, R.: Migrating from SharePoint to a better scrum tool. In: Melnik, G., Kruchten, P., Poppendieck, M. (eds.) Agile 2008 Conference, AGILE 2008, pp. 506–512. IEEE Computer Society, August 2008. doi: 10.1109/Agile.2008.69. ISBN: 978-0-7695-3321-6
  13. 13.
    Seaman, C.: Qualitative methods in empirical studies of software engineering. IEEE Trans. Softw. Eng. 25(4), 557–572 (1999). doi: 10.1109/32.799955. ISSN: 0098-5589CrossRefGoogle Scholar
  14. 14.
    Beck, K., Martin, R.C., Schwaber, K., Sutherland, J., Fowler, M.: Principles behind the agile manifesto (2001). Accessed 12 January 2001
  15. 15.
    Møller, L.S., Nyboe, F.B., Jørgensen, T.B., Broe, J.J.: A scrum tool for improving project management. In: Flirting with the Future, Prototyped Visions by the Next Generation, Proceedings of the 5th Student Interaction Design Research Conference (SIDeR 2009), pp. 30–32 (2009)Google Scholar
  16. 16.
    Bente, G., Ruggenberg, S., Kramer, N.C., Eschenburg, F.: Avatar-mediated networking: increasing social presence and interpersonal trust in net-based collaborations. Hum. Commun. Res. 34(2), 287–318 (2008). doi: 10.1111/j.1468-2958.2008.00322.x CrossRefGoogle Scholar
  17. 17.
    Eckhart, M.: Scrumpy on GitHub, May 2015.
  18. 18.
    Eckhart, M., da Silva, E.V.: Scrumpy – An Agile Project Management Tool Designed to Skyrocket Your Team’s Productivity, May 2015.
  19. 19.
    Eckhart, M.: Product description of Scrumpy on KMU-goes-mobile, May 2015.

Copyright information

© Springer International Publishing Switzerland 2016

Authors and Affiliations

  1. 1.Internet Technologies and ApplicationsFH JoanneumKapfenbergAustria

Personalised recommendations