{'fraction_non_alphanumeric': 0.022641509433962263, 'fraction_numerical': 0.0022641509433962265, 'mean_word_length': 5.254716981132075, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 1, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Is There an Optimal Sprint Length on Agile Software Development Projects?

: Agile software development is adopted by the industry as a way to develop applications while also remaining ﬂexible to quickly respond and adapt. At its core, agile relies heavily upon time-constrained iterations, usually named “sprints”, which should provide the development team to deliver a functional version of a software product. This study aims at understanding what is the impact of different sprint lengths in agile software teams. In order to achieve it, we have conducted a ﬁeld study at a mobile software development course for eight months. The course was organized on three stages, where at each stage ten projects were simultaneously conducted. Data collection was based on project outcome including daily logs and deliverables generated by the teams. Each stage had a different sprint length (1-week, 2-week, or 3-week iterations). Our results indicate that there are differences in some aspects, including project evaluation and weekly impediments. These differences were statistically analyzed regarding the impacts of different sprint lengths in agile teams. Further, we have also observed some correlation between weekly impediments and project evaluation, providing indications of a possible impact on overall projects outcome.