Advertisement

Development of a Grooming Process for an Agile Software Team in the Automotive Domain

  • Francisca Ribeiro
  • André L. Ferreira
  • Anabela Tereso
  • Deborah Perrotta
Part of the Advances in Intelligent Systems and Computing book series (AISC, volume 745)

Abstract

At the current unpredictable technical evolution, the market is demanding an increasingly flexibility from companies to adapt to the pace of change in what customers want. The present research was developed in an automotive company, where software teams are pursuing Agile methodologies to coupe with these challenges. Teams use the Scrum framework, however, lack of efficient communication among team members results in poor performance of the product owner and the development team. In an attempt to solve this issue and according to the needs shared by the teams, this paper proposes a grooming process for a Scrum team. It provides a step-wise approach to work breakdown, from customer requirements elicitation to the development of ready work entities using the user story format. This paper describes how agile methods can support requirements engineering in a software project.

Keywords

Agile methodology Scrum Product backlog grooming 

Notes

Acknowledgements

This work is supported by: European Structural and Investment Funds in the FEDER component, through the Operational Competitiveness and Internationalization Programme (COMPETE 2020) [Project nº 002797; Funding Reference: POCI-01-0247-FEDER-002797].

References

  1. 1.
    Lawrence, K.: Developing leaders in a business. UNC Exec. Dev. 1–15 (2013)Google Scholar
  2. 2.
    Hundermark, P.: Do-Better-Scrum. agile42 - The Agile Coaching Company (2015)Google Scholar
  3. 3.
    Dean, B.J., Pessanha, B.G., Langfeldt, N., Pritchard, S., Stanger, J.: Agile Project Management with Scrum (2006)Google Scholar
  4. 4.
    Sverrisdottir, H.S., Ingason, H.T., Jonasson, H.I.: The role of the product owner in scrum-comparison between theory and practices. Procedia Soc. Behav. Sci. 119, 257–267 (2014)CrossRefGoogle Scholar
  5. 5.
    Susman, G.I., Evered, R.D.: An assessment of the scientific merits of action research. Adm. Sci. Q. 23, 582–603 (1978)CrossRefGoogle Scholar
  6. 6.
    Cohn, M.: Scum (2017). https://www.mountaingoatsoftware.com/agile/scrum. Accessed 19 Apr 2017
  7. 7.
    Mahnič, V., Hovelja, T.: On using planning poker for estimating user stories. J. Syst. Softw. 85, 2086–2095 (2012)CrossRefGoogle Scholar
  8. 8.
    Sutherland, J.: Scrum Handbook. Scrum Trining Intitute Press, Somerville (2010)Google Scholar
  9. 9.
    Tobergte, D.R., Curtis, S.: A guide to the scrum body of knowledge (2013)Google Scholar
  10. 10.
    Rubin, K.S.: Essential Scrum. Pearson Education Inc., London (2012)Google Scholar
  11. 11.
    Crisp, C., McKenna, D.: The Art of Scrum: How Scrum Masters Bind Dev Teams and Unleash Agility (2016)Google Scholar
  12. 12.
    Leffingwell, D.: Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise (2011)Google Scholar
  13. 13.
    O’Brien, R.: An Overview of the Methodological Approach of Action Research. University of Toronto, Toronto (1998)Google Scholar

Copyright information

© Springer International Publishing AG, part of Springer Nature 2018

Authors and Affiliations

  • Francisca Ribeiro
    • 1
    • 2
  • André L. Ferreira
    • 2
  • Anabela Tereso
    • 1
  • Deborah Perrotta
    • 1
    • 2
  1. 1.Production and Systems Department/Centre ALGORITMIUniversity of MinhoGuimarãesPortugal
  2. 2.Bosch Car Multimedia PortugalBragaPortugal

Personalised recommendations