The Impact of Agile Development Practices on Project Outcomes

Dipendra Ghimire, Stuart Charters

Software · 2022 · 33 citations · 14 references

DOIFull text

Open access

Concepts

TL;DR

Agile software development methods were introduced to reduce problems of traditional approaches, with common practices such as Scrum, Extreme Programming, Kanban, stand‑ups, user stories, burndown charts, pair programming, and epics emphasizing collaboration and self‑organization. The study aims to determine how the combination of Agile practices influences team communication, project requirements, and priorities. Data were collected from participants in Agile teams and analyzed to assess the impact of practice combinations on communication, requirements, and priorities. The analysis revealed that adopting more Agile practices correlates with improved communication, clearer requirements, and better prioritization, leading to better project outcomes.

Abstract

Agile software development methods were introduced to minimize problems faced using traditional software development approaches. There are several Agile approaches used in developing software projects, these include Scrum, Extreme programming and Kanban. An Agile approach focuses on collaboration between customers and developers and encourages development teams to be self-organizing. To achieve this there are different Agile practices teams choose to use in their projects. Some teams only use one practice whilst others use a combination of practices. The most common practices used are stand-ups, user stories, Burndown chart/Burnup chart, pair programming, Epic and User stories. This paper reports on the analysis of the data collected from people involved in Agile software development teams and identifies that the combination of practices in Agile software development have an impact on the communication in the team, project requirements and project priorities, with more practices being adopted correlating with better project outcomes.

References

14