Abstract
Currently many organizations have adopted the development of software projects with agile methodologies, particularly Scrum, which has more than 20 years of development. In these methodologies, software is developed iteratively and delivered to the client in increments called releases. In the releases, the goal is to develop system functionality that quickly adds value to the client’s business. At the beginning of the project, one or more releases are planned. For solving the problem of replanning in the context of releases, a model is proposed considering the characteristics of agile development using Scrum. The results obtained show that the algorithm takes a little less than 7 min for solutions that propose replanning composed by 16 sprints, which is equivalent to 240 days of project. They show that applying a repair operator increases the hypervolume quality indicator in the resulting population.
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: International Conference on Computing Science, Communication and Security
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.
