Preference in using Agile Development with Larger Team Size

Abstract

Agile software development includes a group of software development methodologies based on iterative development, where requirements and solutions evolve through collaboration between cross-functional self-organizing teams. Different software houses were visited in a developing country to determine the experiences faced by people working on a real world projects using Agile software development methodology following different variants in different team sizes to determine the preference of using Agile software development methodology in larger team sizes. Several people were surveyed out of which few responded with an opinion of not to use agile development in a team sizes exceeding 25 members. According to the experience of people the ideal team size was 5 to maximum 10. Because according to the survey increase in the number of individuals create issues of communication as it is not possible to keep everyone on the same track with larger teams especially in case of scrum meetings which usually held on daily basis, taking responsibilities as everyone becomes reluctant in taking responsibilities believing someone else will take it, sub teams because the more the number of individuals the more will be the sub teams which indirectly increases the dependency among the teams by breaking the tasks into much smaller chunks. The findings also suggest that customer feedback would increase if the team size is less than 25 which in turn says that the Quality of Software is increased. As this study had only focused on the software companies of a developing country it is recommended that further studies should be carried out by surveying the people of other different developed countries.

A contextualised model of the use of agile technique in South African software development team

“…In the lifecycle of a project, agile methodology encourages continuous iterations of development and testing of software during the software development phase (Zia 2018). With agile methodology, both software development and testing occur concurrently.…”

“…He alludes that, unlike traditional methodologies, agile is not document oriented and that instead of creating the functional specification, software developers rely on storyboards that are created. Zia (2018) asserts that with agile methodology there is no detailed requirements specification but only users' stories that are iteratively written during the software development process.…”

“…It prevents any losses. It is based on five principles, namely optimising value streams, creating value for the customer, eliminating waste, empowering people and continually improving (Zia 2018).…”

Analyzing time pressure for software economics

“…Furthermore, a challenge is associated with the degree of communication, as communication is important for collaboration among the team members for the knowledge exchange (Teasley et al , 2002). However, it consumes the productive time of the team members as well (Zia et al , 2018). Our efforts lie in exploring the solution where TP can be reduced, and TS formation and team communication are optimal.…”

“…Our study shows that TP exerted will increase the software completion time, size and effort. This implies that to ensure the project is on time, the employees have to be stress-free and need to have little boundaries of communication (Khan and Mahmood, 2015; Nan and Harter, 2009; Zia et al , 2018).…”