Abstract
The aim of this paper is to analyse the Agile methods implementation capability within software projects as a more viable alternative to the waterfall model and determine the key factors that guarantee the continuous delivery of software to market at the right and agreed quality level. Two Agile implementation methods were considered: Scrum and Kanban, which were evaluated based on factors like predictability, practicability and complexity. The conclusions show the selected methodologies advantages and disadvantages, and project key attributes can be used to choose the suitable methodology for a project. Regarding the Agile implementation methods, the most straightforward and predictable one was proven to be Scrum. This framework supports frequent delivery of software products that can address complex problems and adapt to the rapid market changes.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callMore From: IOP Conference Series: Materials Science and Engineering
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
