October 26, 2026
Agile methodology applied to installation and commissioning of a project in the food industry
Micaela Camile Alves; Jonatas de Oliveira
DOI: 10.22167/2675-6528-202601226
Article prepared by the ResumeAI tool, an artificial intelligence solution developed by the Pecege Institute focused on synthesis and writing.
Summary
The food sector demanded more efficient industrial project management, especially in the installation and commissioning phases, due to operational complexity and the need for inter-team collaboration. The study aimed to examine the implementation of the agile Scrumban methodology and compare its performance with the traditional methodology proposed by the Project Management Institute. The research was conducted as a descriptive case study, with a mixed approach, in two industrial projects of a food company: Project A used the conventional methodology and Project B applied Scrumban. Data were collected through operational records, a structured questionnaire containing 16 Likert scale questions, and direct observation, analyzed by descriptive statistics and content analysis. The results indicated that the traditional methodology presented communication failures, low activity visibility, and prolonged execution times. In contrast, the use of Scrumban promoted greater transparency, better collaboration among teams, and a significant reduction in activity execution time, which decreased from 30.5 to 12 days. It was found that the adoption of agile methodologies favored operational efficiency and improved project management in dynamic industrial scenarios.
Keywords: Organizational agility; Operational efficiency; Project management; Kanban; Scrum.
1. Introduction
The food industry in Brazil has consolidated itself as one of the most relevant industrial sectors in the country, playing a crucial role in both domestic supply and exports. According to the Brazilian Food Industry Association (ABIA, 2025), the sector has shown continuous growth, driven by factors such as technological innovations, increasing international demand, and changes in consumer preferences. Given this dynamic scenario, food industry companies have directed significant efforts and resources to modernize their production processes, expand industrial capacity, and develop new projects.
In this context, project management has emerged as an essential strategic factor to ensure companies’ competitiveness, especially in industrial sectors that exhibit high operational complexity. Projects dedicated to the implementation and activation of new production lines, for example, require intense collaboration from various functional areas, including engineering, production, quality, maintenance, and safety. Such complexity demands a high degree of coordination and supervision of activities. Dynamic industrial environments, such as those in the food sector, require management methods capable of dealing with uncertainties, interdependencies between tasks, and the need for agile responses (Conforto et al., 2021).
Historically, project management has been conducted through traditional methodologies, widely disseminated by the Project Management Institute (PMI, 2021). These approaches prioritize extensive planning, rigorous scope definition, and sequential task execution. However, in environments requiring greater flexibility and constant adaptation, these methodologies reveal their limitations, potentially leading to delays, rework, and communication problems among teams (Serrador and Pinto, 2021; Marnewick and Marnewick, 2022). In the current industrial scenario, applying conventional approaches in the installation and commissioning phases of projects, characterized by constant changes, represents a significant challenge. Integration among teams, agility in decision-making, and the ability to adapt to unexpected situations are crucial elements for the effective resolution of activities, and the absence of these competencies can compromise operational effectiveness and project outcomes.
Faced with these restrictions, agile methodologies have gained prominence as more flexible and collaborative alternatives. Although originally developed for software development, these approaches have been progressively implemented in various sectors. They facilitate rapid feedback cycles, promote greater interaction between teams, and enhance the ability to adapt to changes, which is vital in volatile environments (Rigby et al., 2016).
Among the most recognized agile methodologies, Scrum stands out, based on iterative work cycles, and Kanban, which emphasizes visual workflow management. The combination of these two approaches gave rise to Scrumban, a hybrid methodology that integrates Scrum’s adaptability with Kanban’s effectiveness in organizing and supervising tasks (Alqudah and Razali, 2018). Hybrid methods, such as Scrumban, are capable of improving operational efficiency, promoting greater alignment between teams, and optimizing priority management in complex projects (Khan et al., 2023), offering a more effective response to the challenges of contemporary industrial project management.
Despite the growing recognition and adoption of agile methodologies, significant gaps still persist in the scientific literature regarding the implementation of these approaches in real industrial scenarios, particularly in the food sector. The inherent complexity of installation and commissioning projects, combined with the dynamics of the food market, reinforces the need for studies that evaluate the effectiveness of new management approaches. The lack of empirical evidence on the application of Scrumban in this specific segment justifies the relevance of investigating how this methodology can optimize project management, overcoming the limitations of traditional approaches and contributing to operational efficiency and organizational agility.
In this context, the present study aimed to examine the implementation of the agile Scrumban methodology in the installation and commissioning phases of an industrial project in a food industry company, contrasting its results with those obtained through the traditional approach, with an emphasis on operational effectiveness, activity duration, and team participation.
2. Material and Methods
This study was characterized as an applied research of a descriptive nature, with the objective of examining and comparing the effectiveness of project management methodologies in the industrial sector. A case study strategy was adopted, considered appropriate for the analysis of contemporary phenomena in their real contexts (Yin, 2015).
The methodological approach was mixed, integrating quantitative and qualitative information for a comprehensive data analysis (Creswell, 2021). The research was conducted in a consolidated food company, located in Curitiba, Paraná, with approximately 2500 employees. The institution’s identity was kept confidential.
The unit of analysis consisted of two distinct industrial projects within the same company. Project A used the conventional project management methodology, while Project B implemented the agile Scrumban methodology, allowing for a direct comparison.
The research population consisted of approximately 28 specialists who worked directly on the studied projects. Operators, engineers, maintenance technicians, and quality analysts were included, professionals essential for the execution and monitoring of activities.
Data collection employed three sources: operational project records, direct observation of activities, and a structured questionnaire. The questionnaire contained 16 closed-ended questions, using a five-point Likert scale, ranging from “strongly disagree” to “strongly agree”.
The instrument’s questions addressed communication, team alignment, activity visibility, operational efficiency, and participant engagement (Khan et al., 2023; Dikert et al., 2017). The questionnaire was administered online via Google Forms, ensuring anonymity and minimizing response distortions.
Project A, serving as the control group, was executed according to the classic project management methodology of the Project Management Institute (PMI, 2021). It was characterized by meticulous planning, upfront scope definition, rigorous schedule control, and sequential task execution.
Your scope involved the adaptation of an existing production line, considered of high complexity. The planned investment was between one million and one million five hundred thousand US dollars, with a scheduled duration of seven months. The team was multidisciplinary, with monitoring based on deadlines and operational notes.
In contrast, Project B was conducted with the agile methodology Scrumban, which integrates elements of Scrum and Kanban (Alqudah and Razali, 2018). This project focused on the creation of a new production line, using existing equipment from another factory, and was classified as medium complexity.
The investment planned for Project B was between two million and three million US dollars, covering the transfer and installation of equipment, training, and operational adjustments. The scheduled period for its completion was approximately five and a half months.
The implementation of Scrumban in Project B used a visual management board with three columns: “pending”, “in progress”, and “finished”. Tasks were represented by cards and classified by criticality level (low, medium, and high). Daily meetings were held to monitor the progress of activities. The Project B team was composed of specialists from the same areas as Project A.
For the data analysis, the numerical information was processed by descriptive statistics, including calculation of means, counts, and percentages, according to Gil (2019). The qualitative data were submitted to content analysis, following Bardin (2016), to understand the participants’ experiences and perceptions.
3. Results and Discussion
The analysis of the two industrial projects, one conducted by the traditional methodology (Project A) and another by the agile Scrumban approach (Project B), revealed substantial differences in activity management, operational efficiency, and team engagement. The results indicated that the conventional methodology, although structured, presented significant flaws in communication and visibility, culminating in prolonged execution times and rework. In contrast, the implementation of Scrumban proved to be more adaptable and effective, promoting greater transparency, collaboration, and a notable reduction in task duration, aligning with the needs of dynamic industrial environments.
Project A Evaluation – Conventional Approach
The evaluation of Project A, which followed the traditional methodology of the Project Management Institute (PMI, 2021), identified a total of 115 actions during the installation and commissioning phases. These activities were categorized by criticality, with 33 of high, 42 of low, and 40 of medium relevance. This distribution highlighted a scenario of intense operational demand, with a significant concentration of medium and high criticality tasks, which directly impacted production continuity. Such a context required more effective coordination and meticulous planning for its execution, characteristics that proved challenging in practice.
Regarding the duration of activities, Project A presented an average of 30.5 days per task. A large variation in this time was observed, with some activities being completed quickly, while others extended for more than 100 days. This fluctuation highlighted the difficulty in predicting the progress of the execution process and signaled restrictions in the planning and supervision of tasks. Predictability is a crucial performance parameter in projects, and its limitation increases the probability of delays, rework, and operational inefficiencies, as pointed out by Serrador and Pinto (2021).
The investigation of variation in execution times indicated the absence of a defined pattern in the conduction of activities, suggesting problems in prioritization and resource allocation. The inconsistency in execution impaired the overall efficiency of the project and hindered the fulfillment of established deadlines. Furthermore, the clarity of activities was restricted, with the tracking of actions occurring in a decentralized manner, based on personal notes and informal dialogues, which complicated the supervision of task progress and the detection of obstacles in the process.
The disconnect between teams from different disciplines, such as engineering, production, quality, and maintenance, represented one of the biggest obstacles in Project A. Collaboration between departments was limited by the absence of well-defined communication channels. Studies such as Khan et al. (2023) emphasize that communication deficiencies are a critical factor for the failure of industrial projects, potentially leading to considerable disharmony, errors, and schedule delays, a pattern clearly identified in this project.
The qualitative analysis, based on the questionnaires, revealed a unfavorable view of the participants regarding communication and coordination. Approximately 62% of respondents pointed out obstacles in defining priorities and in clarity about the progress of actions, evidencing deficiencies in information management. The operations team’s reluctance to implement changes in the production line was notable, linked to the absence of these operators’ participation in the planning phases, which is crucial for the success of projects in industrial contexts (Marnewick and Marnewick, 2022).
The lack of involvement from the operational team reduced collaboration and extended the time needed to resolve actions, revealing a limitation of the conventional method, which tends to focus planning on the initial phases. Activity management occurred reactively, with corrective measures applied only after problems arose, resulting in a total of 115 corrective interventions throughout the project. This reactive approach, combined with high deadline fluctuations and a lack of clarity, demonstrated the restrictions of the conventional methodology in a dynamic scenario, corroborating research indicating its inferior performance in complex contexts (Spundak, 2014).
Project B Evaluation – Scrumban Approach
The analysis of Project B, implemented with the agile Scrumban methodology, allowed for the evaluation of the effects of mixed project management practices in the installation and commissioning phases. This approach integrated elements of Scrum, such as reduced monitoring cycles and daily meetings, with the visual management system of Kanban, promoting greater adaptability and supervision of the workflow (Alqudah and Razali, 2018). Although the project faced an initial delay of two months due to fiscal documentation, a factor external to the methodology, the internal results were significantly positive.
In the time interval studied, only 18 actions were recorded, a considerably smaller amount compared to the 115 actions of Project A. These actions were categorized by criticality: 6 low, 7 medium, and 4 high. The decrease in the total number of tasks signaled an improvement in project performance, indicating that the Scrumban approach aided in identifying and solving problems in the early stages, preventing the accumulation of corrective actions throughout development. This proactivity is a significant differentiator in industrial environments.
The allocation of activities in Project B demonstrated a more adequate balance between criticality levels, resulting in less concentration of high-complexity tasks. This pattern indicated more effective control of the production process and improved administration of the necessary interventions during the commissioning phase. Regarding the execution deadline, the average was 12 days per activity, a substantial reduction compared to the 30.5 days of Project A, evidencing a notable advance in operational efficiency and greater predictability and stability in the process.
The reduction in execution time variability is crucial in industrial contexts, as it facilitates operational planning and increases confidence in meeting established deadlines. The implementation of visual management systems, such as the Kanban board with the columns “pending,” “in progress,” and “completed,” was fundamental for real-time supervision of task progress, contributing to the reduction of bottlenecks and the optimization of process flow (Lei et al., 2021). This transparency allowed all team members to access important project information, aiding in the identification of impediments and faster decision-making.
The structuring of tasks into a continuous flow enabled a more balanced distribution of the workload among team members, preventing overload in specific areas and promoting increased efficiency. An essential component of Scrumban was the daily meetings, or “dailies”, whose purpose was to synchronize tasks, identify obstacles, and establish corrective measures quickly, with daily updates to the activity board. These meetings resulted in remarkable progress in team interaction, fostering constant coordination between the different participating areas, unlike the reactive communication of Project A.
The practice of promoting regular meetings is fundamental to the success of agile methodologies, as it facilitates the early detection of difficulties and the agile application of solutions (Dikert et al., 2017). The qualitative evaluation of the questionnaires confirmed the advantages of Scrumban, with about 60% of respondents mentioning advances in communication, clarity in tasks, team alignment, and project involvement. A significant aspect was the increased involvement of the operational team, which began to actively engage in decisions, better understanding the context and relevance of tasks, an essential factor for the success of agile projects (Moe et al., 2010).
The enhancement in prioritizing tasks, organized by degree of importance, allowed the team to focus efforts on the most significant actions, ensuring that essential tasks were addressed more quickly. This prioritization positively impacted the reduction in task completion time and the increase in operational efficiency, in addition to enabling a more effective distribution of resources, preventing waste and rework. The evaluation of results also revealed a considerable decrease in the frequency of rework, which in Project A were common due to a lack of alignment and communication, but were reduced in Project B through constant monitoring and agile feedback, demonstrating Scrumban’s proactivity in anticipating obstacles.
Results Assessment
The comparison between Projects A and B showed significant differences in team management and performance. Project A’s traditional method faced obstacles that impacted communication, clarity, and task duration, while the agile Scrumban approach in Project B proved more adaptable and conducive to cooperation. The critical analysis of the results sought to integrate quantitative data and qualitative perceptions for a deep understanding of the effects of the applied management methodologies, focusing on operational efficiency, response time, and team involvement.
From a quantitative perspective, the most notable evidence was the considerable reduction in the average time for task completion, which decreased from 30.5 days in Project A to 12 days in Project B. This change represents a reduction of approximately 60.7% in the time required to complete activities, indicating a significant increase in operational efficiency. In addition to the decrease in the average, a drop in the variability of execution times was observed, which points to greater stability and predictability in the workflow, crucial aspects for the planning and delivery of industrial projects (Conforto et al., 2021).
Another significant practical result was the decrease in registered actions, which fell from 115 in Project A to 18 in Project B. Although this difference requires careful analysis, considering the variations in complexity between the projects, it suggests an evolution in organization and proactivity regarding problems. In Project B, greater transparency of activities and constant monitoring, facilitated by Scrumban, enabled early detection of deviations, preventing the accumulation of corrective actions and the consequent volume of rework.
A considerable advance was noted in the organization of tasks in Project B, especially those of high importance. In Project A, the lack of systematic monitoring methods hindered a clear perception of priorities, resulting in delays in the execution of essential actions. In contrast, the implementation of a visual framework and the categorization of actions by criticality level in Project B allowed the most significant activities to be addressed with greater agility. A clear example was the management of tasks that required machine shutdowns: in Project A, they were often delayed due to lack of coordination, while in Project B, they were planned and communicated in advance, resulting in punctual execution and shorter resolution times.
Regarding communication between teams, the qualitative information collected through questionnaires revealed considerable progress in Project B. Respondents highlighted a clearer understanding of activities, a better grasp of priorities, and easier interaction among the involved sectors. This evolution can be directly linked to the adoption of agile methodologies, such as regular review meetings and the use of visual tools. Constant communication and short feedback cycles are essential elements for the success of agile methodologies, enabling rapid issue detection and more effective decision-making (Dikert et al., 2017).
A relevant point highlighted by the results was the increased commitment of the teams, especially the team responsible for operations. In Project A, resistance was observed among the operators, related to the lack of involvement in decisions and the lack of clarity about activities. In Project B, greater engagement of these professionals was recorded, who became actively involved in tasks and gained a deeper understanding of the project objectives. The active participation of team members is one of the essential elements that favor the success of projects carried out through agile methodologies (Moe et al., 2010).
The joint evaluation of numerical and descriptive data indicated that the advances recorded in Project B were not limited to a single parameter, but reflected a series of connected factors. The reduction in execution time, the improvement in communication, the increased visibility of actions, and greater team involvement worked in synergy to enhance operational efficiency. From a theoretical perspective, these findings support research showing the effectiveness of agile methodologies in varied and complex contexts, as they increase organizational flexibility and improve project outcomes (Rigby et al., 2016; Serrador and Pinto, 2021).
It is essential to emphasize that the analysis of the results must consider the study’s limitations, the most significant being the variation in the complexity of the projects evaluated. Project A was categorized as high complexity, while Project B was considered medium complexity. Projects with higher complexity often exhibit greater variability and difficulties in their control, which can unfavorably impact performance indicators (Baccarini, 1996). However, the robustness of the results, especially the reduction in completion time and the qualitative improvements in communication and engagement, suggest that the benefits of Scrumban are not solely due to the lower complexity of Project B.
An important aspect to consider was the need for cultural adjustments by the teams for the implementation of agile methodologies, which may have influenced the results. The incorporation of practices such as regular meetings and the use of visual tools required a cultural transformation and an increase in discipline during task execution, an adaptation process common in agile implementations and linked to the improvement of organizational maturity (Dikert et al., 2017). Furthermore, the research was conducted in a single organizational environment, which restricts the generalization of the results, suggesting that future investigations could expand the analysis to diverse organizations and sectors, adding other performance parameters, such as costs, productivity, and quality.
In summary, the implementation of the Scrumban methodology in Project B demonstrated a remarkable positive impact on the efficiency of activity management in a dynamic industrial context. The decrease in average execution time from 30.5 to 12 days, the significant reduction in the number of corrective actions from 115 to 18, the improvement in communication, and the increase in team engagement indicate that the agile approach proved superior to the conventional methodology. These findings corroborate the literature that points to the relevance of more versatile and adaptable methodologies in constantly changing environments, where agility in response and integration between sectors are essential for project success.
4. Conclusion
The present study aimed to examine the implementation of the agile Scrumban methodology in the installation and commissioning phases of an industrial project in a food industry company, contrasting its results with the traditional approach. It was found that the conventional methodology, applied in Project A, presented communication failures, low visibility of activities, and prolonged execution times, with an average of 30.5 days per task and 115 corrective actions. In contrast, the adoption of Scrumban in Project B promoted greater transparency, improved team collaboration, and resulted in a significant reduction in the average activity execution time to 12 days, in addition to decreasing the number of corrective actions to 18. An increase in operational team engagement and a better definition of priorities were also observed, demonstrating the effectiveness of the agile approach in dynamic scenarios.
The main contribution of this work lies in the empirical demonstration that the Scrumban methodology offers a more effective solution for managing complex industrial projects, favoring operational efficiency and organizational agility compared to traditional methods. However, the study had limitations, such as the variation in the complexity of the evaluated projects, with Project A being of high complexity and Project B of medium complexity, and the research being conducted in a single organizational environment, which restricts the generalization of the results. For future investigations, it is suggested to expand the analysis to different sectors and institutions, as well as to include other performance parameters, such as costs, productivity, and quality, for a more comprehensive understanding of the benefits of Agile methodologies.
Bibliographic References
Alqudah, M.; Razali, R. 2018. An empirical study of Scrumban Formation based on the selection of Scrum and Kanban Practices. International Journal on Advanced Science Engineering Information Technology 8 (6): 2315-2322.
Associação Brasileira da Indústria de Alimentos [ABIA]. 2025. Balanço econômico da indústria de alimentos. Disponível em: <https://intranet.abia.org.br/vsn/temp/z2025221OnePage25web.pdf>. Acesso em: 23 jan. 2026.
Baccarini, D. 1996. The concept of project complexity – a review. International Journal of Project Management 14 (4): 201-204.
Bardin, L. 2016. Análise de conteúdo. Edições 70, São Paulo, SP, BR.
Conforto, E.C.; Amaral, D.C.; Silva, S.L. 2021. Agile project management in industrial environments. International Journal of Project Management 39 (2): 101-113.
Creswell, J.W. 2021. Projeto de pesquisa: métodos qualitativo, quantitativo e misto. 5. Atlas, São Paulo, São Paulo, Brasil.
Dikert, K.; Paasivaara, M.; Lassenius, C. 2017. Challenges and success factors for large-scale agile transformations: a systematic literature review. Information and Software Technology 87 (1): 87-108.
Gil, A.C. 2019. Métodos e técnicas de pesquisa social. 7ed. Atlas, São Paulo, SP, BR.
Khan, A.Z.; Skibniewski, M.; Cable, J.R. 2023. Challenges and limitations of communications in project stakeholder management and engagement. PM World Journal 12 (2).
Lei, H.; Geng, J.; Liu, W. 2021. Application of Kanban in production systems. Procedia CIRP 97 (1) 470-475.
Marnewick, C.; Marnewick, A. 2022. Digitalization of project management: opportunities in research and practice. Project Leadership and Society 3.
Moe, N.B.; Dingsoyr, T.; Dyba, T. 2010. A teamwork model for understanding agile teams. Information and Software Technology 52 (5): 480-491.
Project Management Institute [PMI]. 2021. A guide to the project management body of knowledge (PMBOK guide). 7ed. Newtown Square, PA, EUA.
Rigby, D.K.; Sutherland, J.; Takeuchi, H. 2016. Embracing agile. Harvard Business Review.
Serrador, P.; Pinto, J.K. 2021. Does agile work? A quantitative analysis of agile project success. International Journal of Project Management 33 (5): 1040-1051.
Spundak, M. 2014. Mixed agile/tradicional project management methodoly – reality or illusion? Procedia Social and Behavioral Sciences (119) 939-948.
Yin, R.K. 2015. Estudo de caso: planejamento e métodos. 5 ed. Porto Alegre. RS. BR.
Article originating from the Final Course Project of the Specialization in Project Management of the MBA USP/Esalq
To learn more about the course, click here and access the MBX Academy platform