Article

October 27, 2026

Agile practices in the process of developing technical-commercial proposals aiming to increase performance

Lucas Campos; Gilberto Marassi de Loiola Leite

DOI: 10.22167/2675-6528-202601094

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

Summary

The study analyzed the process of developing technical-commercial proposals in an engineering and environmental services company, inserted in a context of high complexity and competitiveness, where the predominant management model was predictive and sequential, presenting limitations in flexibility and adaptation to changes. The objective was to analyze and incorporate practices and tools from agile methodologies, such as Scrum, Minimum Viable Product (MVP), and Kanban, to complement the traditional model and increase process performance, configuring a hybrid management arrangement. The research was characterized as applied, qualitative, and descriptive, developed from the structured analysis of the current process and professional experience, with a research-action design. The method was based on the adaptation of the Scrum framework, the application of the MVP concept for preliminary deliveries at the “budget” level, and the use of the Kanban method, supported by a CRM, for visualization and workflow management. As results, a potential for improvement was observed in deadline predictability, reduction of rework, anticipation of value delivery to the client, increased process transparency, and higher commercial assertiveness. The incorporation of the MVP, for example, reduced the time for developing preliminary proposals from 20 to 3 days. It was concluded that the structured adoption of agile practices represents a viable and effective alternative for organizations seeking greater competitiveness, flexibility, and alignment with market demands, strengthening organizational performance.

Keywords: Project management; Kanban; Hybrid model; MVP; Scrum.

1. Introduction

The engineering and environmental services sector faces a growing demand for complex and customized solutions, driven by regulatory requirements, pressure for operational efficiency, water resource costs, and the need for rigorous performance and sustainability standards. The business environment has become more competitive, with rapid access to information and diverse technological alternatives, raising customer expectations for agility, transparency, and assertiveness. These transformations reflect a context of increasing complexity and uncertainty, in which traditional management models often require adaptation to maintain adequate performance levels (Kozak-Holland, 2011; PMI, 2021a).

In this dynamic scenario, the development of technical-commercial proposals is crucial for evaluating opportunities and converting them into contracts. In large companies, especially multinationals in complex environmental ventures, proposal structuring involves multiple areas and formal governance stages. Although the predictive and sequential model offers benefits such as standardization and managerial control, it imposes significant limitations. These include difficulty in incorporating intermediate *feedbacks*, rigidity in adapting to scope changes, and a propensity for rework and wasted effort due to incomplete information or late validations. The linearity of this model can prolong the decision cycle and increase the risk of misalignment with the client (PMI, 2017; PMI, 2021a).

Given the shortcomings of predictive models in high-uncertainty environments, the search for complementary approaches that promote greater adaptability and reduce risks has gained prominence. Agile methodologies, initially consolidated in *software* development, emerge as a promising alternative. Based on the Agile Manifesto (Beck et al., 2001), these approaches prioritize the incremental delivery of value, continuous collaboration, and the ability to respond quickly to changes, over rigid plans. The agile mindset, by emphasizing flexibility and continuous learning, aligns with the demands of a market that requires faster and more personalized solutions (PMI, 2021a).

The incorporation of agile practices, such as the Scrum *framework*, the *Minimum Viable Product* (MVP), and the Kanban method, offers a robust framework to complement traditional models. Scrum structures work into one-to-four-week *sprints*, allowing for frequent deliveries and continuous validation (Schwaber and Sutherland, 2020), promoting transparency and alignment. Its iterative logic aligns with Nonaka and Takeuchi’s (1986; 1995) knowledge creation theory. The MVP, adapted for technical-commercial proposals, materializes in preliminary “budget” deliveries, validating premises and feasibility in initial phases with lower cost and effort, reducing risks of rework and resource waste (Standish Group, 2020). Kanban, focused on visualizing and managing workflow, contributes to identifying bottlenecks and balancing team capacity (Anderson, 2010), optimizing cycle time and increasing predictability, often supported by CRM systems.

Considering the growing complexity and competitiveness of the engineering and environmental services sector, and the inherent limitations of predictive management models in the proposal development process, it becomes imperative to explore approaches that promote greater flexibility, adaptability, and efficiency. The adoption of a hybrid arrangement, which integrates the strengths of traditional management with the agility and responsiveness of agile methodologies, presents itself as a promising strategy to optimize organizational performance. Thus, this study aims to analyze the technical-commercial proposal development process in an engineering and environmental services company and incorporate practices and tools from agile methodologies, such as Scrum, Minimum Viable Product (MVP), and Kanban, to complement the traditional model and, thus, increase process performance, configuring a hybrid management arrangement.

2. Material and Methods

This study was characterized as an applied research, with a qualitative approach and descriptive nature, as outlined in the original term paper. The applied research sought to generate knowledge for the resolution of a practical problem in the organizational environment. The qualitative approach allowed for an in-depth understanding of the proposal development process, while the descriptive nature aimed to detail the characteristics of the phenomenon studied. Additionally, the design was framed as action research, involving the direct participation of the researcher in the analyzed context, acting simultaneously in the analysis and in the proposition of improvements (Maschk, 2022).

The research was conducted in a large-sized company, operating in the engineering and environmental services sector, with operations in Latin America. This organization specializes in solutions for water collection, treatment, and distribution, as well as wastewater treatment and the production of reuse water. The study’s focus was on the commercial and proposals department, responsible for structuring complex technical-commercial solutions. The unit of analysis consisted of the process of developing technical-commercial proposals, seeking to optimize their performance in an environment of high technical and regulatory complexity.

There was no formally defined population or sample, as the study was configured as a single case, focused on the analysis and intervention in a specific department of the company. The basis for data collection and identification of improvement opportunities was the systematic observation of the current process, complemented by the author’s professional experience in the organizational context. This approach allowed for deep immersion in the work dynamics and the challenges faced by the team in preparing technical-commercial proposals.

The data collection procedures began with a structured analysis of the technical-commercial proposal elaboration process already established in the department. This stage involved the systematic observation of routines, workflows, and interactions between the commercial and engineering teams. The author’s professional experience was fundamental for the critical analysis of the existing flow, allowing for the identification of strengths, limitations, and opportunities for improvement, according to the perspectives of practical application of project management in real contexts (Maschk, 2022).

Starting from the understanding of the traditional process, the study proceeded to define a proposed scenario, based on the agile mindset. For this purpose, practices and tools associated with the Scrum *framework*, the *Minimum Viable Product* (MVP) concept, and the Kanban method were considered. These methodologies were selected for their potential to complement the existing predictive model, aiming to improve flexibility, adaptability, and efficiency in the development of technical-commercial proposals, without the intention of fully replacing it.

The incorporation of the Scrum *framework* occurred in an adapted way, organizing the work into short, iterative cycles, called *sprints*, lasting between one and four weeks. Each *sprint* was planned through the *Sprint Planning* ceremony, where the team defined the *Product Backlog* items to be executed. During execution, daily *Daily Meetings* of approximately 15 minutes were held for alignment and impediment identification. At the end, *Sprint Review* and *Sprint Retrospective* allowed for the validation of deliverables and continuous process improvement (Schwaber and Sutherland, 2020).

The Scrum roles were adapted to the existing organizational structure to facilitate transition and integration. The Sales Executive took on the role of *Product Owner*, being responsible for representing client interests and prioritizing the *backlog*. The Proposals Manager played the role of *Scrum Master*, acting as a facilitator, removing impediments, and promoting collaboration. The Proposals and Process Engineers were designated as developers, responsible for the technical elaboration of solutions and the delivery of *sprints*. This adaptation aimed for clarity of responsibilities and team engagement.

The concept of *Minimum Viable Product* (MVP) was central to reducing risks and rework. In the context of technical-commercial proposals, the MVP materialized in the elaboration of “budget” level proposals in the initial phases of the process. These preliminary deliverables, with low cost and controlled effort, contained process assumptions, initial Capex and Opex estimates, and a macro scope. The objective was to quickly validate the proposal’s adherence to customer expectations and project conditions, anticipating *feedbacks* and directing more intensive efforts only to opportunities with greater potential (Nonaka and Takeuchi, 1995).

For workflow management and visualization, the Kanban method was used, supported by the *Customer Relationship Management* (CRM) *software* Pipedrive®. This tool allowed for the visual representation of commercial opportunities in configurable *pipelines*, where each proposal was organized into stages, from lead identification to final delivery. The adoption of Kanban, even with conceptually defined *work in progress* (WIP) limits, contributed to process transparency, bottleneck identification, and team workload balancing (Anderson, 2010).

The data analysis was predominantly qualitative, based on systematic observations and critical analysis of the process after the incorporation of agile practices. The impacts on deadline predictability, rework reduction, early delivery of value to the client, improved communication, and increased conversion rate of commercial opportunities were evaluated. Although some indicators such as cycle time and rework incidence were monitored, the measurement was carried out qualitatively, focusing on the perception of improvements and adherence to the proposed hybrid model.

The methodological limitations of the study included the predominance of a qualitative analysis, based on observations arising from the application of practices over a still limited period. This characteristic limited the robust quantitative measurement of the gains obtained. Additionally, the implementation of agile practices occurred in a way adapted to the company’s specific organizational constraints, which may have influenced the scope and generalization of the observed results. No specific formal ethical procedures were identified for conducting this research in the original TCC.

3. Results and Discussion

The results of the intervention conducted are presented from the qualitative analysis of the process after the incorporation of agile practices, complemented by references and *benchmarks* consolidated in the literature on agile methodologies. Considering the adaptation of these practices to the process of elaborating technical-commercial proposals, potential for relevant gains in efficiency, predictability, proposal quality, and commercial assertiveness is observed.

The introduction of an agile mindset into the proposal process showed positive impacts, especially in the ability to adapt to changes in scope and assumptions during the development of opportunities. This was not merely a procedural adjustment, but a fundamental cultural transformation, requiring the overcoming of initial resistance to new ways of working in an environment historically accustomed to rigid and sequential processes. The initial phase demanded considerable effort to demonstrate the tangible benefits of agility, such as faster feedback cycles and an improved ability to respond to client needs. The flexibility to adapt to evolving requirements, a central characteristic of agile methodologies, proved crucial in the engineering and environmental services sector, where project specifications frequently change due to regulatory updates, technological advancements, or specific client modifications. This adaptability directly contrasts with the rigidity of the previous model, which often resulted in bottlenecks and costly rework when changes were introduced late in the project cycle.

These findings are consistent with the fundamental principles of the Agile Manifesto (Beck et al., 2001), which prioritizes “responding to change over following a plan.” The study’s findings align with publications from the Project Management Institute (PMI, 2021a), which consistently report higher success rates for projects employing agile or hybrid approaches compared to purely predictive models. PMI (2021b) emphasizes that agility fosters an environment where teams can quickly adjust course, minimizing the impact of unforeseen challenges. In the context of proposal development, this translates into a reduced risk of developing solutions that become obsolete or misaligned with client expectations before they are even submitted. The traditional model, as described by Kozak-Holland (2011), often struggles to incorporate intermediate feedback, leading to a “big-bang” approach where significant problems are discovered only at later, more costly stages. The agile mindset, by promoting continuous adaptation, effectively mitigates this inherent risk.

The practical implications of reducing rework, a direct consequence of incremental validation, represent a significant gain in efficiency. Previously, changes in advanced stages often required extensive revisions across multiple departments, consuming valuable technical and financial resources. With the agile mindset, decisions are validated incrementally, allowing for early course corrections. This not only saves time and money but also reduces frustration for technical and commercial teams. Furthermore, the enhanced collaboration between technical and commercial areas, fostered by this mindset, is a critical practical outcome. In the traditional model, these departments often operated in silos, resulting in communication breakdowns and misalignments between technical and commercial feasibility. The agile approach, by promoting continuous interaction and shared understanding of customer needs, ensures that proposals are not only technically sound but also strategically aligned with market demands. This improvement in communication and alignment directly contributes to increased team productivity and a more cohesive organizational effort, elevating the company’s competitive advantage in a demanding market. The cultural shift to embrace change and continuous learning, rather than resisting them, positions the company to better navigate future uncertainties and capitalize on emerging opportunities.

The adaptation of the Scrum *framework* to the proposal process resulted in greater predictability of deadlines and better control of activity progress. The implementation of the “Product Vision” provided a clear and shared understanding of the proposal’s final objective, ensuring that all team efforts were directed towards a common purpose. This collaboratively developed vision helped prevent *scope creep* and ensured that the final proposal remained aligned with both client expectations and organizational strategy. The “Product Backlog”, a prioritized list of functionalities and tasks, brought unprecedented transparency to the workload and allowed for strategic sequencing of activities based on value and urgency. This contrasts sharply with the previous, often unstructured, approach where tasks could be initiated without a clear understanding of their priority or contribution to the overall value of the proposal. Dividing the work into short, iterative *sprints* (typically 1 to 4 weeks) transformed the long, sequential process into manageable cycles, each culminating in tangible deliverables. This iterative nature allowed for continuous progress monitoring and frequent adjustment opportunities.

Schwaber and Sutherland (2020) emphasize that Scrum’s iterative cycles and defined roles are designed to maximize predictability and control in complex adaptive problems. The findings of this study align with this principle, demonstrating that decomposing proposal development into *sprints* allowed for more accurate prediction of completion times and better resource management. The “Sprint Review” and “Sprint Retrospective” ceremonies, as described by Schwaber and Sutherland (2020), were instrumental in fostering continuous improvement. These regular *feedbacks*, both internal and external, enabled the team to identify and address issues early, preventing them from escalating. This proactive problem-solving mechanism represents a significant departure from the traditional model, where problems often remained unresolved until the final stages, resulting in costly rework and delays. The PMI (2021a) highlights that adaptive approaches, such as Scrum, are particularly effective in environments characterized by high uncertainty, as they allow for continuous learning and adjustment. The observed reduction in the average proposal development time, along with an improvement in quality, directly supports the literature suggesting that Agile Methods can increase both efficiency and effectiveness. Nonaka and Takeuchi (1995) discuss the importance of knowledge creation through iterative processes, which is precisely what Scrum facilitates by encouraging continuous learning and adaptation within the team.

The practical advantages of incorporating Scrum were manifold. The increased predictability of deadlines allowed the commercial team to provide more realistic expectations to clients, fostering trust and professionalism. Enhanced control over activity progress meant potential bottlenecks could be identified and addressed proactively, preventing delays. For instance, if a specific technical analysis was taking longer than anticipated, the team could reprioritize other tasks or allocate additional resources to ensure *sprint* goals were met. Frequent reviews, both internal and with stakeholders, ensured the proposal was continuously refined, reducing the likelihood of major inconsistencies or misalignments being discovered in the final stages. This not only improved the quality of the final submission but also reduced the emotional and financial cost associated with last-minute changes. The “Product Vision” served as a constant compass, ensuring that even amidst iterative development, overarching strategic objectives were not lost. This structured yet flexible approach empowered the team to deliver higher-quality proposals more consistently and efficiently, reinforcing the company’s reputation for reliability and innovation. The shift from a “big-bang” delivery to incremental value delivery also meant that clients could see progress earlier, fostering a more collaborative relationship and allowing their input to be integrated throughout the process, rather than just at the beginning and end.

Source: Adapted from Schwaber and Sutherland (2020)

Figure 1. Scrum framework flowchart

The explicit definition of the adapted Scrum roles (“Product Owner”, “Scrum Master”, and development team) contributed to the reduction of organizational ambiguities and responsibility conflicts. The formal adaptation of Scrum roles within the existing organizational structure provided much-needed clarity regarding responsibilities, which represented a significant improvement compared to previous, often ambiguous, role definitions. The Sales Executive, by assuming the role of “Product Owner”, became the definitive voice for customer needs and business value, ensuring that the proposal development was always aligned with market demands and strategic objectives. This central authority for prioritization eliminated previous conflicts arising from competing demands and unclear direction. The Proposal Manager, as “Scrum Master”, acted as a facilitator and impediment remover, protecting the agile process and fostering a collaborative environment. This role was crucial in ensuring that the team could focus on its work without being overwhelmed by organizational obstacles or procedural complexities. The Proposal and Process Engineers, who formed the “Development Team”, obtained a clear mandate for technical execution and delivery, fostering a sense of ownership and responsibility for their contributions.

The importance of role and responsibility clarity is a recurring theme in project management literature. PMI (2021a) explicitly states that a lack of role clarity is one of the main factors contributing to project failures, especially in complex environments. By clearly delineating who is responsible for what, the adapted Scrum *framework* minimized the potential for misunderstandings and conflicts that frequently arise in multidisciplinary teams. Nonaka and Takeuchi (1995) highlight that effective knowledge creation and innovation depend on well-defined roles within a collaborative structure, allowing individuals to specialize while contributing to a shared goal. The observed increase in decision-making fluidity can be directly attributed to this clarity. With a dedicated “Product Owner” making prioritization decisions and a “Scrum Master” removing impediments, the team could make quick, informed decisions without extensive bureaucratic delays. This contrasts with traditional hierarchical structures, where decisions often require multiple layers of approval, slowing down the process.

The practical impact of this role clarity was profound. It significantly reduced organizational ambiguities, which previously led to wasted time and effort as team members sought clarification or awaited decisions. For instance, the clear mandate of the “Product Owner” meant that questions about customer scope or priorities could be addressed swiftly, preventing the development team from working on features that might later be deemed unnecessary. The “Scrum Master’s” role in removing impediments directly contributed to increased team productivity by ensuring a smoother workflow. If a technical resource was unavailable or specific information was missing, the “Scrum Master” would proactively address these issues, allowing the development team to maintain focus. Furthermore, increased team member engagement was a notable outcome. When individuals understand their specific contribution and how it fits into the bigger picture, their motivation and commitment tend to rise. This enhanced engagement, coupled with improved communication channels, fostered a more dynamic and productive work environment. The tailored roles, therefore, not only streamlined the proposal development process but also cultivated a stronger sense of teamwork and collective responsibility, which are vital for sustained organizational performance in a competitive market.

Source: Original survey data

Figure 2. Incorporation of roles in the process according to Scrum

The incorporation of the “Minimum Viable Product” (MVP) concept proved to be one of the most relevant elements of the intervention carried out, especially regarding the reduction of technical and commercial risks and the increase in process efficiency. The integration of the MVP concept into the proposal development process revealed itself as a transformative element, fundamentally altering how opportunities were sought and evaluated. Instead of allocating significant resources to develop a comprehensive proposal from the outset, the company could now generate a “budget” level proposal in a remarkably short timeframe — approximately 3 days, a stark contrast to the 20 days typically required for a complete proposal in the traditional model. This expedited preliminary delivery, containing essential process assumptions, initial Capex and Opex estimates, and a macro scope, allowed for early validation with the client. The primary objective of this MVP was not to present a finalized solution, but rather to test key assumptions, gather initial *feedback*, and quickly verify the client’s genuine interest and the project’s overall viability. This approach effectively minimized the initial investment of time and resources in opportunities that might ultimately prove unfeasible or misaligned with client expectations.

This finding aligns strongly with the principles of *lean startup* and agile development, where the MVP is a central strategy for learning and risk reduction (Nonaka and Takeuchi, 1995). By validating assumptions early, organizations can avoid the significant waste associated with building comprehensive solutions that, in the end, do not meet market needs or customer demands. The Standish Group’s *Chaos Report* (2020) consistently highlights that a substantial portion of project features are rarely or never used, underscoring the importance of incremental delivery and early validation to reduce such waste. The traditional, predictive model, in contrast, often encourages a “big-bang” approach, where a complete solution is developed before any substantial customer *feedback* is incorporated, leading to higher risks of rework and project cancellation. The MVP approach, as applied here, directly addresses this by creating a much earlier *feedback* loop in the process, allowing for iterative refinement and adaptation based on actual customer input. This not only reduces the risk of technical and commercial failures but also fosters a more collaborative relationship with the customer, who becomes an active participant in shaping the solution.

The practical implications of the MVP approach are far-reaching. Firstly, the drastic reduction in the time required for initial proposals (from 20 to 3 days) significantly increased the company’s commercial agility. Sales teams were able to respond to customer inquiries much more quickly, gaining a competitive advantage and demonstrating responsiveness. This speed allowed the company to engage with more opportunities, filtering out less viable ones early and concentrating intensive resources only on those with high conversion potential. Secondly, the early customer validation provided by the MVP was critical in improving the accuracy of Capex and Opex estimates. By presenting preliminary figures and receiving initial feedback, the team was able to refine its cost models and technical assumptions, reducing the likelihood of significant deviations between the initial proposal and the final project conditions. This proactive risk mitigation not only protected the company from potential financial losses but also built greater trust with clients, who appreciated the transparency and iterative refinement. Thirdly, the MVP concept facilitated a more strategic allocation of technical resources. Instead of highly skilled engineers spending weeks on detailed proposals for uncertain opportunities, their expertise could be focused on refining viable projects, maximizing their impact and reducing wasted effort. This strategic shift in resource allocation directly contributed to increased overall efficiency and a higher conversion rate of commercial opportunities, boosting the company’s bottom line and market position. The ability to quickly iterate on a budget proposal based on customer feedback also meant that the final, firm proposal was much more likely to be accepted, as it had already been de-risked and aligned with customer expectations.

The use of the Kanban method, supported by the Pipedrive® CRM, resulted in significant gains in transparency and workflow control. The implementation of the Kanban method, specifically through the Pipedrive® CRM *software*, promoted a profound transformation in the management and visualization of proposal workflows. Prior to this, the process, although structured, often lacked real-time visibility, making it challenging to determine the exact *status* of each proposal or identify where bottlenecks were occurring. The Pipedrive® system, with its configurable *pipelines*, provided a clear visual representation of each business opportunity, moving through distinct stages, from initial *lead* identification to final proposal delivery. This visual management system immediately enhanced transparency, allowing all stakeholders—from sales executives to engineering teams—to have a shared and up-to-date understanding of the entire proposal portfolio. This eliminated the need for constant *status* update meetings and reduced the time spent searching for information, freeing up valuable time for more productive tasks.

The observed benefits are highly consistent with the principles of Kanban, as articulated by Anderson (2010). Anderson emphasizes that workflow visualization, limiting work in progress (WIP), and flow management are critical for improving efficiency and predictability. Although the study applied WIP limits conceptually, rather than strictly, even this conceptual application contributed to better workload balancing and a reduction in chaotic and excessive resource allocation. The traditional model often suffered from a “push” system, where new work was initiated regardless of the team’s current capacity, leading to overload, multitasking, and ultimately, slower delivery. Kanban, in contrast, promotes a “pull” system, where work is pulled into the next stage only when capacity allows, ensuring a smoother and more sustainable flow. This shift directly contributed to the observed reduction in activity overlap and a more balanced distribution of tasks among team members. Centralizing information in Pipedrive® also aligns with best practices in Knowledge Management (Nonaka and Takeuchi, 1995), ensuring that all relevant data, customer interactions, and proposal iterations are stored in a single accessible location, reducing information loss and improving decision-making.

Source: Original survey data

Figure 3. Pipedrive® CRM tool

From a practical standpoint, the Kanban-based system provided invaluable support for managerial control and continuous improvement. Managers could quickly identify proposals that were stalled at a particular stage, indicating a potential bottleneck or an issue requiring intervention. This proactive identification allowed for timely adjustments, such as resource reallocation, issue escalation, or task reprioritization. For instance, if a specific engineering review step consistently showed a backlog, it signaled the need to investigate the underlying cause, perhaps a lack of resources, a complex technical challenge, or an inefficient process step. The ability to track key indicators like cycle time (the time it takes for a proposal to move from start to finish) and the incidence of rework, even if qualitatively, provided objective data for process analysis and improvement. This data-driven approach fostered a culture of continuous improvement, where the team regularly reviewed its workflow, identified areas for enhancement, and implemented incremental adjustments. The transparency offered by the visual Kanban board also empowered team members, giving them a clearer understanding of their individual contributions to the overall flow and enabling them to self-organize more effectively. Ultimately, the Kanban system, supported by Pipedrive®, transformed the proposals department into a more agile, responsive, and data-informed operation, capable of delivering proposals with greater efficiency and control, thereby strengthening the company’s market position.

The review of the proposal development flowchart, with the selective incorporation of agile practices, resulted in the configuration of a more flexible and responsive hybrid model, without compromising the formal governance mechanisms. The culmination of the agile intervention was the revised proposal development flowchart, which effectively integrated agile practices into the existing traditional *framework*, creating a robust hybrid model. This adaptation did not aim to replace the established and governed process, but rather to enhance it with flexibility and responsiveness. A key structural change was the segregation of the “Feasibility Score” stage from the “Form A” stage. In the traditional model, the “Feasibility Score” involved a comprehensive review by a large multidisciplinary team, consuming significant resources even for low-viability opportunities. The new flowchart allowed for a preliminary and agile assessment of *leads* by the “Product Owner” and “Scrum Master” before engaging the full technical team. This strategic change significantly reduced the unnecessary mobilization of technical resources for opportunities with a low probability of proceeding, optimizing resource allocation and accelerating the initial screening process.

This hybrid approach aligns with contemporary project management trends that advocate for combining the strengths of predictive and adaptive methodologies (PMI, 2021a). While traditional models excel in governance, standardization, and control, they often lack the agility required in dynamic environments. Conversely, purely agile models can sometimes struggle with the formal controls and extensive documentation demanded in highly regulated sectors like engineering. The proposed hybrid model, therefore, represents a pragmatic solution, leveraging the best of both worlds. The distinction between “budget” and “firm” proposals, a direct outcome of the MVP concept, is an excellent example of this integration. It allows for early, low-cost validation (budget proposal) before committing to a full, detailed development (firm proposal). This layered approach to proposal development is a practical application of risk management principles, where investment is scaled according to the level of certainty and client commitment, as advocated by Nonaka and Takeuchi (1995) in their discussions on iterative product development. Continuous monitoring via Pipedrive® (Kanban) further reinforces this hybrid nature, providing real-time visibility and control over agile *sprints* and traditional sequential steps.

Source: Original survey data

Figure 4. Proposal development flowchart

The practical advantages of this revised flowchart are substantial and multifaceted. The faster, more targeted “Feasibility Score” process means the sales team can qualify *leads* quickly, allowing them to pursue high-potential opportunities with greater speed and confidence. This early filtering mechanism prevents valuable technical resources from being allocated to speculative projects, enabling them to focus on proposals with a higher likelihood of conversion. The clear distinction between “budget” and “firm” proposals offers a structured path for client engagement, allowing for iterative refinement and validation at each stage. This not only reduces the risk of rework but also ensures that the final proposal is highly aligned with client expectations and project realities. Continuous monitoring facilitated by Pipedrive® provides managers with real-time *insights* into the entire proposal *pipeline*, enabling proactive decision-making and efficient resource allocation. For example, if a specific “firm” proposal is progressing slowly, the system can highlight the bottleneck, allowing the “Scrum Master” to intervene and resolve impediments. Overall, the consolidated results of this action research indicate a significant improvement in operational efficiency, a notable reduction in rework, the ability to anticipate critical decisions, increased deadline predictability, and a marked improvement in the perceived quality of proposals. This reinforces the company’s ability to compete effectively in a complex and rapidly evolving market, demonstrating that a well-designed hybrid model can deliver superior performance without sacrificing necessary governance and control. The new flowchart, therefore, serves as a blueprint for continuous process improvement, fostering a culture of adaptability and continuous value delivery.

Source: Original survey data

Figure 5. Flowchart for proposal development adapted to agile

4. Conclusion

It is concluded that the objective was achieved, as this study analyzed the process of developing technical-commercial proposals in an engineering and environmental services company and incorporated practices and tools from agile methodologies, such as Scrum, Minimum Viable Product (MVP), and Kanban, to complement the traditional model, configuring a hybrid management arrangement. The action research demonstrated that this approach resulted in significant gains in operational efficiency, greater deadline predictability, reduction of rework, early validation of assumptions with the client, and improvement in the perceived quality of the proposals. The adaptation of the Scrum *framework* organized the work into short cycles, the MVP allowed for early conceptual validations, and Kanban, supported by a digital tool, optimized the visualization and control of the flow, strengthening the integration between areas.

However, the study presents important limitations, such as the predominance of qualitative analysis and a restricted observation period, which prevents a more robust quantitative measurement of gains. Furthermore, the implementation of agile practices was adapted to organizational constraints, which may influence the scope of the results. For future studies, it is recommended to continue the application and maturation of practices, with the consolidation of quantitative performance indicators, such as average lead time, rework rate, and customer satisfaction. It is also suggested to expand the approach to other processes and comparative analyses in different business contexts, deepening the understanding of hybrid management models.

Bibliographic References

Anderson, D.J. 2010. Kanban: successful evolutionary change for your technology business. Blue Hole Press, Sequim, Washington, EUA.

Beck, K.; Beedle, M.; Bennekum, A.; Cockburn, A.; Cunningham, W.; Fowler, M; Grenning, J.; Highsmith, J.; Hunt, A.; Jeffries, R.; Kern, J.; Marick, B.; Martin, R.; Mellor, S.; Schwaber, K.; Sutherland, J.; Thomas, D. 2001. Manifesto for Agile Software Development. Disponível em: <http://agilemanifesto.org/>. Acesso em: 02 fev. 2026.

Kozak-Holland, M. 2011. History of project management. Multi-Media Publications, Oshawa, Ontario, Canadá.

Maschk, R. 2022. Gerenciamento de projetos: fundamentos. Senac, São Paulo, SP, Brasil.

Nonaka, I.; Takeuchi, H. 1986. The new new product development game. Harvard Business Review 64(1): 137-146.

Nonaka, I.; Takeuchi, H. 1995. The knowledge-creating company: how Japanese companies create the dynamics of innovation. Oxford University Press, New York, NY, EUA.

Project Management Institute [PMI]. 2017. A guide to the project management body of knowledge (PMBOK® Guide). 6ed. PMI, Newtown Square, PA, EUA.

Project Management Institute [PMI]. 2021a. A guide to the project management body of knowledge (PMBOK® Guide). 7ed. PMI, Newtown Square, PA, EUA.

Project Management Institute [PMI]. 2021b. Pulse of the profession® 2021. PMI, Newtown Square, PA, EUA.

Schwaber, K.; Sutherland, J. 2020. Guia do Scrum: o guia definitivo para o Scrum as regras do jogo. Disponível em: <https://www.scrumguides.org/>. Acesso em: 10 jan. 2026.

Standish Group. 2020. Chaos report 2020. Boston: Standish Group.

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.