## 1 Introduction  
Agile methodologies emerged as a response to problems in traditional project management methods [1]. Originally introduced in the Manifesto for Agile Software Development in 2001, agile has set new standards for flexibility and adaptability in software development [2; 3]. Agile methodologies are a set of iterative and incremental approaches to software development and project management. They prioritize flexibility, collaboration, and customer feedback to deliver high-quality products efficiently. Mention methodologies emphasize adaptive planning, continuous improvement, and rapid delivery of working software. Agile methods are very popular because of their features in software development [4]. Key principles of agile methodologies include [5]:  
* Breaking the project into small iterations, allowing for frequent releases and feedback loops. * Involving stakeholders throughout the development process to ensure alignment with their needs and priorities. * Embracing change and adjusting plans based on feedback and evolving requirements. * Bringing together individuals with diverse skills and expertise to promote collaboration and problem-solving. * Reflecting on performance and processes to identify areas for enhancement and implementing changes incrementally. Scrum is the most popular agile development methodology [5; 6; 7; 8]. Scrum was developed to improve team collaboration and efficiency through structured processes and frequent evaluations [9].Meetings in the Scrum methodology facilitate communication in the execution of tasks [10]. A daily fifteen-minute Scrum meeting is held by the manager and members of the development team, during which the manager asks questions to be discussed: What has been completed? What things need to be done, and what problems do the team members have? A sprint planning meeting is a monthly meeting attended by the product owner, Scrum master, and the team to discuss what will be done for the next sprint. The project is divided into small tasks to complete the tasks in one sprint. A sprint review meeting is a monthly meeting held at the end of a sprint. It is a time-limited meeting where team members present the incremental working model that has been completed. A sprint retrospective meeting is held after the completion of each sprint. Team members take appropriate action for the future sprint anddetermine if everything is fine and if some improvement is needed [10; 11]. These are some types of meetings that are carried out, and there are more, depending on the company. Scrum benefits [12]:  
* Scrum supports teams to complete their products rapidly and coherently;
* Scrum guarantees efficient use of money and time;
* Big projects are divided into maintainable sprints;
* Developed products are coded and tested throughout the sprint analysis;
* Every task is done properly for rapid software development;
* The team members can achieve a clear idea with Scrum meetings;
* Get feedback from customers and stakeholders for better improvements;
* The self-effort of every team member is seen in every Scrum meeting. Scrum teams are the core of the Scrum framework [7; 13]. Meetings are conducted within the Scrum methodology. Meetings enable teams to coordinate, communicate, and adapt to rapidly changing project requirements and priorities. They are of great importance, and it is necessary to emphasize the problems in agile teams. Problems in agile teams include lack of focus, poor member engagement, technology issues, lack of transparency, conflicts, communication challenges, and information overload. Problems significantly affect team efficiency and productivity, hindering collaboration and quality of work [14; 15]. In comparison to Scrum, the Kanban method is less detailed in its required practices and principles, making it a more flexible approach. While Scrum is known for its structured framework with specific roles and ceremonies, Kanban is less rigid and offers greater adaptability [16].