Article

October 27, 2026

Application of the Scrum method in the development of tooling for new products in the aeronautical sector.

Luiz Fernando Gianoni; Desiree Baldin Damame

DOI: 10.22167/2675-6528-202601131

Article prepared by the ResumeAI tool, an artificial intelligence solution developed by the Pecege Institute focused on synthesis and writing.

Summary

The development of new products in the aeronautical sector is characterized by high complexity, regulatory rigor, and tight deadlines, making schedule management a critical factor for project success. The study aimed to analyze the application of the Scrum methodology as a tool for reducing tooling development cycles in a company in the aeronautical sector. A case study method was adopted, allowing an in-depth analysis of the new product development process in its real organizational environment. The approach involved the practical application of Scrum in the phases of requirements definition, preliminary design, and tooling supplier prospecting and selection, with systematic schedule monitoring through Sprints and “framework” events. The results indicated a potential reduction of 38% in the development cycle, enabling initial product planning. However, during project execution, significant changes in requirements necessitated the inclusion of an additional “sprint”, resulting in an effective reduction of 23% in the total cycle. Despite the difference between the projected and actual gain, the results demonstrated that Scrum contributed significantly to cycle reduction, increased flexibility, and improved adaptability to changes, even in an environment of high uncertainty. It was concluded that the Scrum methodology constitutes a viable and effective alternative for managing complex industrial projects, especially when there is a need to reconcile deadline reduction, control, and adaptability.

Keywords: Adaptability; Complexity; Project management; Agile management; Cycle reduction.

1. Introduction

The global industrial scenario is marked by intense competitiveness, driven by the continuous pursuit of innovation and efficiency. The aeronautical sector, in particular, stands out as one of the most demanding and strategic, characterized by substantial investments, rapid technological advancements, and unprecedented regulatory rigor. The ability to develop new products agilely and effectively is a crucial competitive advantage for companies in this segment. Innovation and strategic thinking are fundamental for identifying new opportunities and generating lasting competitive advantages (Carvalho and Rabechini Jr., 2018). The modern industrial environment demands dynamic adaptive capabilities from organizations to respond to market pressures and constant transformations, making the optimization of decision-making processes and the efficient allocation of resources essential for sustainability.

Due to this dynamism and complexity, project management emerges as a central discipline to guide change processes and ensure the efficient application of resources. The Project Management Institute (PMI, 2021) emphasizes that project management is vital for the achievement of strategic objectives, promoting consistent value delivery and alignment with business goals. In environments characterized by uncertainties, rapid changes, and high complexity, the adoption of flexible and adaptive management approaches becomes imperative. Unlike merely complicated projects, which can be managed by detailed planning and rigorous control, complex projects, such as those found in aeronautical development, exhibit emergent behaviors, significant interdependencies, and limited predictability of outcomes (Ottino, 2004). Ottino (2004) argues that complex systems cannot be understood solely by the isolated analysis of their parts, demanding management models that prioritize continuous adaptation, learning, and incremental experimentation.

In this scenario of high complexity and need for adaptability, agile methodologies gain prominence, and Scrum stands out as one of the most widely adopted frameworks for project management. The PMI (2017) describes Scrum as an agile approach based on empirical principles, which favors short iterations, constant collaboration, and continuous adaptability. It is particularly indicated for situations where requirements evolve progressively, a common characteristic in the development of tooling for the aeronautical sector, where specifications can be refined and altered throughout the cycle. Schwaber and Sutherland (2020) define Scrum as a lightweight tool that empowers teams and organizations to generate value continuously, through adaptive solutions to complex problems. Its pillars – transparency, inspection, and adaptation – are crucial for dealing with the uncertainty inherent in complex engineering projects, allowing teams to respond quickly to changes and optimize the development process. The Scrum framework, with its fixed work cycles (sprints) and regular events, promotes a constant pace of development, greater predictability, and the continuous application of empiricism, impacting the reduction of development cycles and organizational efficiency. In the context of aeronautical tooling development, which involves high conception and manufacturing cycles and broad interaction between engineering and supply chains, Scrum’s ability to efficiently absorb and integrate requirement changes is a significant differentiator.

Despite the recognition of agile approaches, the practical application of Scrum in highly regulated and complex industrial contexts, such as the development of aeronautical tooling, still lacks empirical studies demonstrating its specific benefits and challenges. The technical complexity of the tooling, the criticality of deadlines for the economic viability of projects, and compliance with rigorous standards make schedule management a determining factor for success. Research on the effectiveness of Scrum in this environment is fundamental to optimizing development processes, mitigating risks, and increasing responsiveness to change. Given this scenario, this study is justified by the need to explore management alternatives that reconcile deadline reduction with control and adaptability in complex industrial projects. Thus, the work aimed to analyze the application of the Scrum methodology as a tool for reducing development cycles of tooling in a company in the aeronautical sector.

2. Material and Methods

The methodological design adopted for this study was the case study, a strategy recognized for its ability to investigate contemporary phenomena in their real contexts. This approach is particularly suitable when the boundary between the analyzed phenomenon and the context in which it is embedded is not clearly established (Yin, 2015). The case study allowed for an in-depth analysis of processes and decisions in a complex organizational environment, fostering an understanding of the relationships and practices developed. Such a method is valued for its flexibility in using various data collection techniques, such as documentary analysis and direct observation, contributing to a comprehensive view of the research object (Gil, 2008; Lakatos and Marconi, 2010).

The research was conducted in a large company in the aeronautical sector, located in the municipality of São José dos Campos, in the state of São Paulo. This organization specializes in the manufacturing and assembly of aeronautical components, an industrial environment characterized by high complexity and regulatory rigor. The study’s focus was on the tooling development process for new products, which represents a critical path to project success. The unit of analysis consisted of the practical application of the Scrum methodology within this specific process, seeking to understand its impacts on reducing development cycles. The study period was not explicitly delimited in the original methodology, but the application occurred in a real product development context.

The study directly involved several functional areas of the company, considered essential and interdependent in the new product development process. The product engineering, tooling manufacturing engineering, indirect procurement, and production planning teams actively participated. Continuous interaction between these departments was crucial for coordinating activities, making decisions, and meeting established deadlines. Additionally, the researcher’s direct participation as a project manager provided a practical and in-depth understanding of organizational dynamics and the challenges inherent in product development within the aeronautical industrial environment, enriching the study’s perspective.

For data collection, documentary analysis and direct observation techniques were employed, as recommended for case studies (Lakatos and Marconi, 2010). Documentary analysis included the review of technical specifications, project plans, and schedule records. Direct observation was carried out through the researcher’s active participation in work routines and Scrum events. Furthermore, structured meetings were fundamental instruments, encompassing product definition meetings, sprint planning, daily progress monitoring meetings, and sprint review sessions, allowing for requirements gathering, concept validation, and progress monitoring.

The methodological design of this study was anchored in the phases and principles presented in the Scrum Guide (Schwaber and Sutherland, 2020). Although the Scrum methodology is inherently flexible, all the steps proposed by the framework were fully complied with during the development of the case study. The application of Scrum was considered adequate for the development of tools, especially due to the uncertainty and the emergent nature of the final requirements in complex projects. Scrum, with its pillars of transparency, inspection, and adaptation, proved to be an effective empirical model for dealing with dynamic and highly complex environments, promoting short work cycles and continuous adaptation.

The first stage of applying Scrum consisted of defining the product and elaborating the “Product Backlog”. Meetings were held with the product engineering and production engineering areas, with the participation of the “Product Owner”. This role was crucial for representing the project client, prioritizing the “Product Backlog” and focusing on the presentation of the new product. During these meetings, the main requirements were identified and the list of tooling necessary for manufacturing was structured. The project deliverables were defined and organized into a prioritized list of requirements, serving as the basis for subsequent development stages.

The “Sprint” planning stage was conducted in collaboration with the senior engineers from the tooling manufacturing engineering department. A “sprint” represents a fixed-duration work cycle, typically between one and four weeks, during which the team develops a potentially shippable product increment. For this case study, four sprints were previously established, each lasting ten business days. The planning considered predecessor activities and the prioritization of “Product Backlog” items, aiming for value delivery and the maintenance of a constant development pace, according to Scrum principles (Schwaber and Sutherland, 2020).

The execution of the sprints was divided into four distinct cycles, each with specific objectives. Sprint 01 focused on defining the technical requirements for the development of the tooling, preparing the technical documentation, and validating these requirements with the “Product Owner”. In Sprint 02, the preliminary development of the tooling project concepts was carried out, followed by validation with the “Product Owner” and the initiation of the supplier selection process by the indirect procurement department. Sprint 03 involved the evaluation of supplier proposals, the updating of tooling projects to accommodate the evolution of the product structure and new requirements presented. Finally, Sprint 04 was dedicated to the final validation of the tooling project with the “Product Owner”, verification of requirement fulfillment, and authorization for the commencement of tooling manufacturing.

During the execution of each “sprint”, daily meetings were held to track progress and identify potential impediments. These meetings, known as Daily Scrum, were limited to fifteen minutes and were structured around three main questions. Participants responded about what they had done since the last meeting to contribute to the “sprint” goal, what they intended to do until the next meeting for the same purpose, and whether there were any impediments or blockers hindering the work or the advancement of the “sprint”. This format promoted transparency, alignment, and rapid problem identification.

At the end of each ten-business-day “sprint”, a review meeting was held to evaluate the performance of the work cycle. This event included an analysis of the progress of activities, a check of undelivered items, and the identification of necessary corrective actions. Simultaneously, requirements were refined together with the “Product Owner”, ensuring alignment with potential changes and priorities. Additionally, a “sprint” retrospective was conducted, focusing on continuous improvement, team recognition, and the identification of enhancement actions for the subsequent “sprint”, contributing to the overall effectiveness of the adopted methodology.

The data treatment and analysis were carried out by systematically monitoring the development schedule, using the events and artifacts of the Scrum framework. The analysis involved comparing the development cycles observed during the application of Scrum with the standard cycles traditionally practiced by the organization, according to historical experience and product complexity. This comparison allowed for an evaluation of the methodology’s effectiveness in reducing deadlines and adapting to changes. The focus was on describing how Scrum influenced time management and the response to emerging requirements, without anticipating quantitative results.

To contextualize the need for the Scrum approach, standard tooling development cycles, based on the organization’s historical experience, were considered. These cycles represent the traditional initial planning for requirements definition activities, preliminary concept development, vendor proposal evaluation, and final project validation. Table 1, presented below, details the activities and their respective durations in business days, reflecting the usual schedule adopted before Scrum implementation. This information was fundamental in establishing a benchmark against the cycles proposed by the agile methodology.

Table 1. Initial planned cycles

Element

Activities

Duration

1

Definition of technical requirements for the development of tooling, elaboration of technical documentation and validation of requirements with the “product owner”.

20 days left

2

Development of preliminary concepts for tooling projects and validation of concepts with the “product owner”, to send to the indirect procurement area initiating the supplier selection process.

15 days left

3

Evaluate supplier proposals regarding the tooling development cycle, update tooling designs to meet the evolution of the product structure and new requirements presented by the “product owner”.

20 days left

4

Validate the final tooling project with the “product owner” and validate the fulfillment of requirements. Authorize the start of tooling manufacturing.

10 cr

Source: Original Term Paper

In contrast to the traditional model, the application of Scrum resulted in a new cycle planning for the same development activities of tooling. Table 2, which follows below, illustrates the cycles planned with the Scrum methodology, indicating the durations in working days for each sprint and the corresponding activities. This planning was developed based on agile principles, aiming to optimize development time and increase flexibility. The comparison between traditional cycles and cycles planned with Scrum was a central element for evaluating the methodology’s potential contribution to reducing project deadlines.

Table 2. Planned cycles

Element

Activities

Sprint

Duration

1

Definition of technical requirements for the development of tooling, elaboration of technical documentation and validation of requirements with the “product owner”.

1

10 cr

2

Development of preliminary concepts for tooling projects and validation of concepts with the “product owner”, to send to the indirect procurement area initiating the supplier selection process.

2

10 cr

3

Evaluate supplier proposals regarding the tooling development cycle, update tooling designs to meet the evolution of the product structure and new requirements presented by the “product owner”.

3

10 cr

4

Validate the final tooling project with the “product owner” and validate the fulfillment of requirements. Authorize the start of tooling manufacturing.

4

10 cr

Source: Original Term Paper

3. Results and Discussion

The application of the Scrum methodology in the context of developing tooling for new products in the aeronautical sector revealed a complex panorama of results, characterized by a combination of successes in optimizing cycles and challenges inherent to the dynamic and uncertain nature of high-complexity projects. Initially, a partial achievement of expected results was observed, with a notable reduction in the development cycle for the crucial phases of requirements definition, preliminary design, and tooling supplier prospecting and selection. However, the cycle effectively carried out diverged from the initial planning of the methodology, evidencing the need for an in-depth analysis of the interactions between Scrum’s agility and the contingencies of the aeronautical industrial environment.

The discrepancy between the planned cycle and the one actually carried out was mainly due to a significant modification in the requirements identified during Sprint 3. This alteration directly impacted the preliminary designs and required a new round of requirements validation, culminating in the need to include an additional sprint in the project schedule. This finding highlights the emergent nature of requirements in complex projects, a phenomenon widely discussed in the literature. Ottino (2004) argues that complex systems cannot be fully understood by analyzing their parts in isolation, as the global behavior emerges from the dynamic interactions between components. In the context of this study, the evolution of requirements was not a mere adjustment, but a reconfiguration that reverberated throughout the planning, demonstrating the interdependence of project elements. Scrum’s ability to absorb this change, even with the addition of a sprint, underscores its resilience in high-uncertainty environments, as advocated by Schwaber and Sutherland (2020), who define Scrum as a lightweight framework that helps teams and organizations generate continuous value through adaptive solutions for complex problems.

The relevance of the “Product Owner’s” active participation in “sprint” review meetings emerged as a critical factor for risk mitigation and maintaining project alignment. The continuous presence and engagement of the “Product Owner” are fundamental to prevent the project from evolving with outdated data or requirements, ensuring that decisions made reflect the most recent needs of the client and the market. This point corroborates the Project Management Institute’s (PMI, 2017) view on the importance of constant collaboration among those involved in agile approaches. In a sector like aeronautics, where safety and regulatory compliance are paramount, continuous validation of requirements by the “Product Owner” is not just a best practice, but an essential safeguard against costly rework and critical delays. The absence of an engaged “Product Owner” could have amplified the impact of the change in requirements in Sprint 3, potentially leading to an even greater deviation from the schedule and a significant increase in costs. The practical implication is that organizations must invest in the training and empowerment of the “Product Owner”, recognizing their central role in facilitating adaptation and ensuring value delivery.

To contextualize the effectiveness of the Scrum methodology, a comparison was made with the standard development cycles for tools traditionally practiced by the organization. Table 1, presented below, illustrates the usual timeline adopted before the implementation of Scrum, detailing the activities and their respective durations in business days.

Table 1. Initial planned cycles

Element

Activities

Duration

1

Definition of technical requirements for the development of tooling, elaboration of technical documentation and validation of requirements with the “product owner”.

20 days left

2

Development of preliminary concepts for tooling projects and validation of concepts with the “product owner”, to send to the indirect procurement area initiating the supplier selection process.

15 days left

3

Evaluate supplier proposals regarding the tooling development cycle, update tooling designs to meet the evolution of the product structure and new requirements presented by the “product owner”.

20 days left

4

Validate the final tooling project with the “product owner” and validate the fulfillment of requirements. Authorize the start of tooling manufacturing.

10 cr

Source: Original Term Paper

The analysis of Table 1 reveals that the traditional tool development model was characterized by considerable duration cycles for each phase, totaling a substantial time for project completion. For example, the technical requirements definition and documentation elaboration phase demanded 20 business days, a period that, in an environment of high competitiveness and rapid technological evolution, can become a significant bottleneck. This approach, although it may offer a sense of predictability in projects with stable requirements, becomes inefficient and risky in scenarios where uncertainty and the need for adaptation are high, as is the case with new product development in the aeronautical sector. The rigidity of traditional schedules, often based on sequential approaches like the waterfall model, makes it difficult to incorporate changes and can lead to substantial delays if requirements evolve after the initial planning phases, as pointed out by Carvalho and Rabechini Jr. (2018). The lack of continuous feedback mechanisms and the difficulty in adjusting the scope without impacting the entire schedule are inherent disadvantages of these models, which justifies the search for more flexible alternatives.

In contrast to the traditional model, the application of Scrum resulted in a new cycle planning for the same development activities of tooling, as detailed in Table 2.

Table 2. Planned cycles

Element

Activities

Sprint

Duration

1

Definition of technical requirements for the development of tooling, elaboration of technical documentation and validation of requirements with the “product owner”.

1

10 cr

2

Development of preliminary concepts for tooling projects and validation of concepts with the “product owner”, to send to the indirect procurement area initiating the supplier selection process.

2

10 cr

3

Evaluate supplier proposals regarding the tooling development cycle, update tooling designs to meet the evolution of the product structure and new requirements presented by the “product owner”.

3

10 cr

4

Validate the final tooling project with the “product owner” and validate the fulfillment of requirements. Authorize the start of tooling manufacturing.

4

10 cr

Source: Original Term Paper

Table 2 demonstrates the restructuring of activities into fixed-duration sprints, each lasting 10 business days, highlighting a significant schedule compression for each phase. The definition of requirements, for example, which in the traditional model took 20 business days, was allocated to Sprint 1, with a duration of 10 business days, representing a 50% reduction for this specific activity. This optimization is a direct reflection of Scrum principles, which promote short work cycles, focus on delivering value increments, and continuous inspection and adaptation (Schwaber and Sutherland, 2020). The possibility of a 38% reduction in the total development cycle for tooling, as initially projected, was an expressive and decisive result for the company’s approval of the new product development plan. This potential gain would not only accelerate time-to-market but also free up resources more quickly for other projects, increasing the organization’s operational efficiency. The practical implication is that the adoption of Scrum allows companies in the aeronautical sector to respond more rapidly to market demands and maintain a competitive advantage, while simultaneously managing the inherent complexity of their products.

Despite the initial projected gain of 38%, the project execution revealed that the substantial scope modification during Sprint 3 required the inclusion of an additional sprint, resulting in an effective reduction of 23% in the total cycle. Although lower than the initially projected gain, this outcome remains highly relevant, especially considering the high level of uncertainty and complexity inherent in product development in the aeronautical sector. Oehmen et al. (2015) highlight that complex engineering projects are characterized by a high degree of uncertainty and significant interdependencies, requiring rapid responses and continuous adaptability. Scrum’s ability to absorb such a significant change in requirements and still deliver a 23% reduction in the total cycle, without compromising the overall project deadline objectives, demonstrates the robustness and flexibility of the methodology. In a traditional environment, a scope alteration of this magnitude would likely result in a much larger delay, with significant additional costs and a negative impact on team morale. Scrum, by allowing continuous adaptation, transforms a potential disaster into a manageable challenge, reinforcing the idea that agility is not just about speed, but also about resilience and responsiveness.

The flexibility and adaptability of Scrum were crucial in handling requirement changes. Scrum events, such as Daily Scrums, Sprint Reviews, and Sprint Retrospectives, played a fundamental role in this process. Daily Scrums, with their limited duration and focus on the three essential questions (what was done, what will be done, and what impediments exist), promoted transparency and allowed for rapid identification of problems and blockers, facilitating team coordination and alignment. Sprint Reviews, in turn, were essential for continuous requirement refinement with the “Product Owner”, ensuring that the product under development remained aligned with customer expectations and needs. This iterative process of inspection and adaptation is a central pillar of Scrum, as described by Schwaber and Sutherland (2020), and was vital for the team to proactively adjust the project’s course. Sprint Retrospectives, at the end of each cycle, allowed the team to reflect on what worked well and what could be improved, fostering a culture of continuous learning and enhancing the methodology’s effectiveness. The practical implication is that the implementation of these events should not be seen as a formality, but as an investment in the project’s health and adaptability, empowering teams to self-organize and solve problems efficiently.

Beyond cycle reduction and adaptability, the implementation of Scrum provided greater control over the schedule and better visibility of activity progress. In complex projects, lack of visibility can lead to unpleasant surprises and significant delays. Scrum, with its artifacts such as the Product Backlog and Sprint Backlog, and its regular events, offers a framework that promotes transparency at all stages of development. The team and stakeholders have a clear understanding of what is being worked on, what has been completed, and what still needs to be done. This enhanced visibility is one of the main benefits of agile methodology, as highlighted by the PMI (2021), which emphasizes the importance of flexible approaches in environments of uncertainty. The ability to monitor progress in short cycles allows management to identify deviations early and take corrective actions before problems worsen. This contrasts with traditional approaches, where control can be more reactive and progress information may be outdated. The practical implication is that Scrum not only accelerates development but also improves the quality of project management, enabling more informed and strategic decisions.

The results of this study also indicate that the application of Scrum marked the beginning of a shift in the project management approach adopted by the organization. By serving as a reference for future initiatives in new product development, the study contributed to the institutionalization of more systematic schedule control practices and the use of project management support tools. This transition from a more traditional approach to an agile methodology reflects a global trend in project management, driven by the need for greater agility and responsiveness to market changes (PMI, 2017). Organizational maturity in project management is a critical factor for long-term success, and the adoption of frameworks like Scrum can accelerate this process. Gil (2008) and Lakatos and Marconi (2010) emphasize that flexibility in using various data collection techniques and in-depth analysis of complex scenarios, characteristics of the case study, are essential for a comprehensive understanding of the research subject. By integrating Scrum, the company not only optimized a specific project but also set a precedent for enhancing its ability to manage future projects, promoting an integrated view of deadlines, resources, and activity execution.

One of the most significant points of this work is the demonstration that the Scrum methodology can coexist with the technical and regulatory demands of the aeronautical sector. Traditionally, highly regulated industries, such as aeronautics, tend to favor more rigid and sequential project management approaches, due to the need for extensive documentation, traceability, and compliance with rigorous standards. However, this study has proven that Scrum, when properly applied, can offer the necessary flexibility to deal with complexity and uncertainty, without compromising adherence to these critical requirements. Sprint review events, for example, can be structured to include the necessary regulatory validations and approvals, ensuring that each product increment is compliant. The transparency inherent in Scrum, with its visible artifacts and regular meetings, facilitates communication and progress documentation, which is vital for audits and compliance. This opens new perspectives for the adoption of Agile Methods in other industrial sectors with similar characteristics, challenging the perception that agility is incompatible with regulatory rigor. The ability to reconcile deadline reduction with control and adaptability is a crucial competitive differentiator, allowing the company not only to innovate faster but also to do so safely and in compliance.

In summary, the results obtained in this case study confirm that the application of the Scrum methodology in the development of tools for new products in the aeronautical sector is a viable and effective alternative for managing complex industrial projects. Although the actual cycle reduction gain was 23%, lower than the initially projected 38% due to requirement changes, Scrum’s ability to absorb these changes and still deliver a positive outcome is a testament to its robustness. The methodology contributed significantly to the reduction of development cycles, increased flexibility, and improved adaptability to changes, even in an environment of high uncertainty. Greater visibility of progress, enhanced control over the schedule, and the promotion of a culture of continuous improvement are additional benefits that reinforce the method’s suitability for dynamic and complex environments. This work demonstrates that, with a structured application and continuous stakeholder engagement, especially from the “Product Owner”, Scrum can be a powerful tool to drive efficiency, competitiveness, and responsiveness to market demands in high-tech and strictly regulated industries.

4. Conclusion

It is concluded that the objective was achieved by analyzing the application of the Scrum methodology as a tool for reducing the development cycles of tooling in a company in the aeronautical sector. The study demonstrated that Scrum is a viable and effective alternative for managing complex industrial projects, contributing significantly to the reduction of development cycles. Although the projected reduction was 38%, the execution resulted in a real gain of 23%, which is still an expressive and relevant result for the sector. The methodology provided greater flexibility, adaptability to changes, and improved schedule control and visibility, crucial elements in an environment of high uncertainty and regulatory rigor.

The main limitation observed lies in the emergent nature of requirements in complex projects. A substantial change in scope during Sprint 3 required the inclusion of an additional sprint, impacting the initially planned cycle gain. This event highlights the difficulty of predicting all needs in dynamic environments, even with Scrum’s agility. For future studies, it is suggested to deepen the analysis of the causes that lead to frequent requirement revisions, seeking strategies to mitigate their impact. Additionally, it is recommended to investigate the feasibility of extending the adoption of agile methodologies to all areas involved in product development, aiming for an even more integrated and efficient management of activities.

Bibliographic References

CARVALHO, Marly Monteiro de; RABECHINI JR., Roque. Fundamentos em gestão de projetos: construindo competências para gerenciar projetos. 5. ed. São Paulo: Atlas, 2018.

GIL, Antônio Carlos. Métodos e técnicas de pesquisa social. 6. ed. São Paulo: Atlas, 2008.

LAKATOS, Eva Maria; MARCONI, Marina de Andrade. Fundamentos de metodologia científica. 7. ed. São Paulo: Atlas, 2010.

OEHMEN, Josef et al. The complexity of risk management in engineering projects. International Journal of Project Management, v. 33, n. 4, p. 909-923, 2015.

OTTINO, Julio M. Engineering complex systems. Nature, v. 427, n. 6973, p. 399-399, 2004. DOI: 10.1038/427399a.

PROJECT MANAGEMENT INSTITUTE. A guide to the project management body of knowledge (PMBOK® Guide). 7. ed. Newtown Square, PA: Project Management Institute, 2021.

PROJECT MANAGEMENT INSTITUTE. Agile Practice Guide. Newtown Square, PA: Project Management Institute, 2017.

SCHWABER, Ken; SUTHERLAND, Jeff. The Scrum Guide: The definitive guide to Scrum – the rules of the game. 2020. Disponível em: <https://scrumguides.org/>. Acesso em: 17 abr. 2026.

YIN, Robert K. Estudo de caso: planejamento e métodos. 5. ed. Porto Alegre: Bookman, 2015.

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

You may also like

November 17, 2026

Detection and Diagnosis of Diseases in Corn and Rice in Mozambique with Deep Learning

Mozambican agriculture depends on corn and rice, fundamental crops for food security, but their productivity is strongly affected by phytosanitary diseases, whose early and accurate identification remains a challenge in resource-limited contexts. The study aimed to develop and compare Deep Learning-based models for the automatic detection and diagnosis of diseases in corn and rice leaves in Mozambique. Three approaches were used: a classic Convolutional Neural Network (CNN) developed from scratch, and two transfer learning models, ResNet50 and MobileNetV2. The dataset consisted of images from public databases and collected in the field, which underwent cleaning, balancing, and artificial augmentation steps. The models were trained and evaluated with standard performance metrics, including accuracy, precision, recall, F1-score, Log Loss, and Cohen’s Kappa. The classic CNN presented the best overall performance, with 94% precision, recall, and F1-score, and 93% accuracy and Cohen’s Kappa. MobileNetV2 achieved 91% F1-score and 90% accuracy, standing out for its lower Log Loss (0.30) and training time (6h32min59s). ResNet50 reached 80% F1-score and 79% accuracy. It was concluded that Deep Learning techniques have high potential to support phytopathological diagnosis in real agricultural contexts, contributing to faster and more accurate decisions in the management of corn and rice diseases.

Keywords: Deep learning; Rice; Plant diseases; Corn; Computer vision.

November 17, 2026

Artificial intelligence in accounting operational routines and financial efficiency

The incorporation of Artificial Intelligence (AI) and automation tools has reconfigured the routines of Brazilian accounting offices, impacting productivity, error mitigation, and financial efficiency. These impacts were analyzed in a small accounting firm, specialized in serving service providers in the medical field in São Caetano do Sul, São Paulo. The research adopted a qualitative approach, with a single case study design and incorporated units of analysis. Data were collected through a structured questionnaire, applied via Google Forms between January and February 2026, to five professionals in the operational structure of the firm in a census survey. The treatment followed content analysis with a priori and emergent categories. All respondents declared the use of automated tools or tools with AI resources. The perception of reduced execution time, decreased operational errors, rework, and better use of the team’s time converged in 80% of affirmative responses and 20% partial responses. The most benefited activities were bank reconciliation, import of fiscal documents, and tax assessment, with visible gains on typing errors, duplicate entries, and incorrect classification. Human intervention remained indispensable in tax planning, scenario analysis, and verification of ancillary obligations. The overall evaluation of AI’s contribution was predominantly favorable, with moderation linked to the complexity of fiscal regulations.

Keywords: Content analysis; Process automation; Accounting 4.0; Small business; Digital transformation.

November 17, 2026

Factors influencing schedule management in sewage treatment plant “retrofit” projects

Projects involving “retrofit” in Sewage Treatment Plants (STP) are characterized by high complexity, operational restrictions, and multiple technical interfaces. The study analyzed the perception of the professionals involved regarding the management and adherence to deadlines in “retrofit” projects for sewage treatment plants, considering technical, operational, and organizational factors. The research was characterized as an applied study, with a quali-quantitative approach, designed as a field survey. Data analysis was performed using descriptive statistics and qualitative categorization, employing SWOT, risk matrix (Probability x Impact), and 5W2H action plan tools. The results indicated a high perception of clarity (77.8%) and realism of deadlines (100% agreement), evidencing consistent initial planning. However, 77.7% of respondents pointed out that rework and scope changes directly impacted deadline adherence. The integration between engineering, manufacturing, and Production Planning and Control (PPC) showed an intermediate evaluation (77.7% partial/total agreement), indicating fragility in interfunctional coordination. The risk matrix highlighted as critical: scope changes, operational limitations of the STP, and technical complexity, all with a high level. As a central improvement, the standardization of scope change control, analysis, and approval was proposed, aiming to reduce rework and increase schedule predictability.

Keywords: Performance; Integration; Planning; Rework; Risk.

November 17, 2026

B2C Acquisition in diagnostic medicine: strategic partnerships with specialized medical offices

The diagnostic medicine sector in Brazil operates with high dependence on health plan providers, which limits the financial autonomy of service providers. This study proposed and analyzed a direct patient acquisition model (B2C) for a highly complex diagnostic medicine institution, structured through partnerships with Oncology and Cardiology practices and operationalized by a personalized customer service called concierge. The investigation adopted a mixed-methods approach in three phases: a field survey with a structured questionnaire applied to 87 patients, mapping of the operational flow using “Service Blueprint”, and analysis of the conversion rate from 312 medical referrals registered in the pilot project. The results indicated that trust in medical referral achieved 92.0% agreement, establishing itself as the main factor for adherence. The convenience of performing the exam on the same day reached 78.2%, and the willingness to pay directly was 55.2%, with polarization associated with the predominance of health plan users. The “Service Blueprint” identified three critical points in the transitions between stages of the patient journey. The overall conversion rate was 51.0%, with superior performance in Oncology (58.2%) compared to Cardiology (45.0%), and the greatest loss was concentrated in the acceptance and scheduling stage (28.3%). It was concluded that the model demonstrated possible operational viability and indications of patient acceptance, conditioned by price transparency and a reduction in the interval between consultation and approach by the concierge.

Keywords: Direct payment; Patient journey; Supplementary health; Concierge service; Conversion rate.

November 17, 2026

The role of the school manager in promoting an inclusive culture: leadership and educational policies

The research analyzed the school manager’s performance in promoting an inclusive culture, considering the need to transform legal guidelines and pedagogical foundations into effective institutional practices. It was assumed that school inclusion requires planning, organization, and strategic leadership in the school’s daily operations. A qualitative approach of an applied nature was adopted, developed in three complementary stages: documentary analysis of Brazilian legislation on inclusive education, bibliographic review on school leadership and management, and data systematization using management tools such as SWOT analysis and the PDCA cycle. The results indicated that the school management’s performance directly influenced the consolidation of inclusive environments, especially in the organization of processes, continuous team training, and strengthening of a collaborative institutional culture respectful of diversity. Structural, pedagogical, and relational challenges that demanded planned interventions were also identified. Finally, a Practical Guide for School Managers was developed, with guidelines, protocols, and operational orientations for decision-making and the organization of inclusive processes. It was concluded that the construction of an inclusive culture depended on the management’s ability to articulate public policies, pedagogical practices, and institutional processes, consolidating inclusion as a permanent commitment in the school context.

Keywords: educational accessibility; educational equity; participatory management; strategic planning; institutional processes.

November 17, 2026

An AI artifact based on Design Thinking to support the elicitation of software requirements from user needs

The development of software oriented to user needs frequently faces challenges in requirements elicitation, stemming from ambiguities in natural language and communication failures. Given this, an intelligent artifact integrating Design Thinking and Artificial Intelligence was proposed and validated, focusing on the Empathy and Definition stages, to support the collection, interpretation, and structuring of user needs. The research, of an applied, qualitative, and exploratory nature, conducted a Proof of Concept in a controlled environment, employing hypothetical scenarios. The artifact operated through guided natural language interviews, organizing information into elements such as pain points, context, and impact, and generating traceable problem syntheses. The results indicated that the system organized unstructured reports, reduced ambiguities, and preserved the meaning of the original information in most cases. The ability to reorganize logically in complex scenarios was also observed, although with limitations in separating multiple problems and dependence on instructions. It was concluded that the artifact has potential as a support for requirements elicitation, improving the clarity and structuring of information, but requires supervision and contextual control.

Keywords: Design Thinking; Requirements Elicitation; Requirements Engineering; Artificial Intelligence; Natural Language Processing.

November 17, 2026

The Extinction of the Monophasic Tax System in the Pharmaceutical Industry in Light of the Tax Reform

The consumption Tax Reform, established by Constitutional Amendment No. 132/2023, introduced structural changes to the Brazilian tax system, with the replacement of the Social Integration Program (PIS) and the Social Security Financing Contribution (COFINS) by the Contribution on Goods and Services (CBS), in a dual Value Added Tax (VAT) model. The objective was to analyze the impacts of the extinction of the single-stage system on the pharmaceutical industry, in light of the new regulatory design and its economic and legal effects. A qualitative, exploratory research was conducted through a case study and documentary analysis of legislation and specialized doctrine. It was examined whether the end of the single-stage system would imply a relevant increase in the tax burden for the sector. The results indicated that, although the formal overcoming of the single-stage system has occurred, the material exemption of medicines has been preserved, mainly due to the application of reduced rates of 60% and, in certain cases, a zero rate of the Tax on Goods and Services (IBS) and CBS. The change in model may cause occasional variations in revenue collection, without characterizing a structural increase in the tax burden, tending towards neutrality over time. It was preliminarily concluded that the Tax Reform reorganized the taxation technique in the pharmaceutical industry, replacing a concentrated regime with more transparent exemption mechanisms. This approach proved compatible with the principles of neutrality, full non-cumulativeness, and fiscality, maintaining tax protection for essential medicines and aligning fiscal policy with the fundamental right to health.

Keywords: CBS; COFINS; IBS; Dual VAT; PIS.