Papers
Topics
Authors
Recent
Gemini 2.5 Flash
Gemini 2.5 Flash
110 tokens/sec
GPT-4o
56 tokens/sec
Gemini 2.5 Pro Pro
44 tokens/sec
o3 Pro
6 tokens/sec
GPT-4.1 Pro
47 tokens/sec
DeepSeek R1 via Azure Pro
28 tokens/sec
2000 character limit reached

Use of Agile Practices in Start-ups (2402.09555v1)

Published 14 Feb 2024 in cs.SE

Abstract: Context Software start-ups have shown their ability to develop and launch innovative software products and services. Small, motivated teams and uncertain project scope makes start-ups good candidates for adopting Agile practices. Objective We explore how start-ups use Agile practices and what effects can be associated with the use of those practices. Method We use a case survey to analyze 84 start-up cases and 56 Agile practices. We apply statistical methods to test for statistically significant associations between the use of Agile practices, team, and product factors. Results Our results suggest that development of the backlog, use of version control, code refactoring, and development of user stories are the most frequently reported practices. We identify 22 associations between the use of Agile practices, team, and product factors. The use of Agile practices is associated with effects on source code and overall product quality. A team's positive or negative attitude towards best engineering practices is a significant indicator for either adoption or rejection of certain Agile practices. To explore the relationships in our findings, we set forth a number of propositions that can be investigated in future research. Conclusions We conclude that start-ups use Agile practices, however without following any specific methodology. We identify the opportunity for more fine-grained studies into the adoption and effects of individual Agile practices. Start-up practitioners could benefit from Agile practices in terms of better overall quality, tighter control over team performance, and resource utilization.

Definition Search Book Streamline Icon: https://streamlinehq.com
References (45)
  1. Alliance Agile. Agile glossary. https://www.agilealliance.org/agile101/agile-glossary/, 2018. [Online; accessed 20-April-2018].
  2. Alan Agresti. An introduction to categorical data analysis, volume 135. Wiley New York, 1996.
  3. Manifesto for agile software development. 2001.
  4. Steve Blank. Why the Lean Start Up Changes Everything. Harvard Business Review, 91(5):64, 2013.
  5. Software Development in Startup Companies: The Greenfield Startup Model. IEEE Transactions on Software Engineering, X(September):233, 2016.
  6. A survey study of critical success factors in agile software projects. Journal of Systems and Software, 81(6):961–971, jun 2008.
  7. J Cohan. Statistical power analysis for the behaviour sciences, 1988.
  8. Software test automation practices in agile development environment: An industry experience report. In 2012 7th International Workshop on Automation of Software Test (AST), pages 57–63. IEEE, 2012.
  9. Mark Crowne. Why software product startups fail and what to do about it. In Engineering Management Conference, pages 338–343, Cambridge, UK, 2002. IEEE.
  10. Wayne W Daniel. Spearman rank correlation coefficient. Applied nonparametric statistics, pages 358–365, 1990.
  11. Agile practices in practice: a mapping study. In Proceedings of the 18th International Conference on Evaluation and Assessment in Software Engineering, page 30. ACM, 2014.
  12. Empirical studies of agile software development: A systematic review. Information and software technology, 50(9-10):833–859, 2008.
  13. Key Challenges in Early-Stage Software Startups. In Agile Processes, in Software Engineering, and Extreme Programming, volume 212, pages 52–63, 2015.
  14. What Do We Know about Software Development in Startups? IEEE Software, 31(5):28–32, sep 2014.
  15. The evolution of requirements practices in software startups. In Proceedings of the 40th International Conference on Software Engineering, pages 823–833. ACM, 2018.
  16. The prospects of a quantitative measurement of agility: A validation study on an agile maturity model. Journal of Systems and Software, 107:38–49, 2015.
  17. Adery CA Hope. A simplified monte carlo significance test procedure. Journal of the Royal Statistical Society. Series B (Methodological), pages 582–598, 1968.
  18. Analyses of an agile methodology implementation. In Proceedings. 30th Euromicro Conference, 2004., pages 326–333. IEEE, 2004.
  19. Global software engineering and agile practices: a systematic review. Journal of software: Evolution and Process, 24(6):643–659, 2012.
  20. Effective implementation of agile practices-incoordination with lean kanban. International Journal on Computer Science and Engineering, 4(1):87, 2012.
  21. System metaphor in extreme programming: A semiotic approach. In 7th Internat. Workshop Organ. Semiotics. Citeseer, 2004.
  22. Software quality: the elusive target [special issues section]. IEEE software, 13(1):12–21, 1996.
  23. Eriks Klotins. Using the case survey method to explore engineering practices in software start-ups. In Proceedings of the 1st International Workshop on Software Engineering for Startups, pages 24–26. IEEE Press, 2017.
  24. A progression model of software engineering goals, challenges, and practices in start-ups. IEEE Transactions on Software Engineering, 2019.
  25. Software engineering antipatterns in start-ups. IEEE Software, 36(2):118–126, 2018.
  26. Software engineering in start-up companies: An analysis of 88 experience reports. Empirical Software Engineering, 24(1):68–102, 2019.
  27. R. Larsson. Case Survey Methodology: Quantitative Analysis of Patterns Across Case Studies. Academy of Management Journal, 36(6):1515–1546, 1993.
  28. Exploring extreme programming in context: an industrial case study. In Agile Development Conference, pages 32–41. IEEE, 2004.
  29. Forging high-quality user stories: towards a discipline for agile requirements. In 2015 IEEE 23rd international requirements engineering conference (RE), pages 126–135. IEEE, 2015.
  30. A taxonomy and an initial empirical study of bad smells in code. International Conference on Software Maintenance, 2003. ICSM 2003. Proceedings., (OCTOBER):381–384, 2003.
  31. Agile software development practices: evolution, principles, and criticisms. International Journal of Quality & Reliability Management, 29(9):972–980, 2012.
  32. A case study on the impact of refactoring on quality and productivity in an agile team. In IFIP Central and East European Conference on Software Engineering Techniques, pages 252–266. Springer, 2007.
  33. Contextualized relationship between knowledge sharing and performance in software development. Journal of Management Information Systems, 32(2):134–161, 2015.
  34. Do they really smell bad? a study on developers’ perception of bad code smells. In 2014 IEEE International Conference on Software Maintenance and Evolution, pages 101–110. IEEE, 2014.
  35. Are software startups applying agile practices? the state of the practice from a large survey. In International Conference on Agile Software Development, pages 167–183. Springer, Cham, 2017.
  36. Software development in startup companies: A systematic mapping study. Information and Software Technology, 56(10):1200–1218, oct 2014.
  37. Inc. PitchBook Data. European Middle Market Report 2H 2015. 2015.
  38. Inc. PitchBook Data. U.S. Middle market report Q4 2015. Technical report, 2015.
  39. The Scrum software development process for small teams. IEEE software, (August):26–32, 2000.
  40. Case study research in software engineering. John Wiley & Sons, Inc., mar 2012.
  41. Bran Selic. Agile documentation, anyone? IEEE software, 26(6), 2009.
  42. Prioritizing agile benefits and limitations in relation to practice usage. Software quality journal, 24(2):447–482, 2016.
  43. The Role of Process in a Software Start-up. IEEE Software, 17(4):33–39, 2000.
  44. An exploration of technical debt. Journal of Systems and Software, 86(6):1498–1516, jun 2013.
  45. Is a Rigorous Agile Methodology the Best Development Strategy for Small Scale Tech Startups? Technical report, University of Pennsylvania Department of Computer and Information Science, 2013.
User Edit Pencil Streamline Icon: https://streamlinehq.com
Authors (7)
  1. Eriks Klotins (18 papers)
  2. Michael Unterkalmsteiner (73 papers)
  3. Panagiota Chatzipetrou (7 papers)
  4. Tony Gorschek (38 papers)
  5. Rafael Prikladnicki (16 papers)
  6. Nirnaya Tripathi (3 papers)
  7. Leandro Bento Pompermaier (3 papers)

Summary

We haven't generated a summary for this paper yet.

X Twitter Logo Streamline Icon: https://streamlinehq.com