October 26, 2026
Risk analysis applied to predictive schedule optimization in the procurement phase of a project
Pedro Gabriel Camargo de Campos Montanari; Felipe Miranda de Souza Almeida
DOI: 10.22167/2675-6528-202601306
Article prepared by the ResumeAI tool, an artificial intelligence solution developed by the Pecege Institute focused on synthesis and writing.
Summary
The growing pressure for reduced deadlines in the automotive sector, driven by globalization and competitiveness, demanded greater efficiency in planning and time management in development schedules. This study analyzed the application of schedule compression techniques and risk analysis tools in the development of an automotive product, aiming to reduce the project deadline in the acquisition phase without compromising the quality of deliverables and technical requirements. To this end, a predictive macro schedule was developed, structured in work packages and interdependent activities. The Critical Path Method (CPM) was applied to identify the critical path. Subsequently, techniques such as *crashing* and *fast-tracking*, described in the PMBOK® Guide, were employed, associated with the analysis, classification, and acceptance of identified risks through a probability and impact matrix. The results indicated that the integration of these techniques allowed for the construction of more assertive and reliable schedules, reducing exposure to uncontrolled risks and increasing project predictability. The approach strengthened technical decision-making and ensured adherence to customer milestones, proving to be a strategic factor in complex industrial environments, resulting in a seven-month reduction in the total deadline. It was concluded that schedule compression, when conducted in a structured manner and aligned with risk management, constitutes a relevant tool for improving temporal performance and efficiency in project planning, in addition to strengthening project management governance and maturity.
Keywords: Critical Path Method; Product development; Project management; Predictability; Automotive sector.
1. Introduction
The automotive sector is a fundamental pillar of global industry, with significant impact on technological development and the economy. In Brazil, this segment represented eighteen percent of the industrial Gross Domestic Product in 2022 (Ferreira Filho, 2022), and the truck and bus industry is crucial for freight transport, accounting for 61.1% in Brazil in 2018 (Wolff and Caldas, 2018) and 63.6% in the United States in 2014 (United States Department of Transportation, 2017). This environment of great relevance is, however, marked by intense globalization and competitiveness, which impose continuous pressure for agility and efficiency. The demand for innovation and high quality in increasingly shorter product development cycles is a constant for manufacturers (Masoumi et al., 2019; Schneider and Tanaka, 2025). The ability to reduce the time to market for new vehicles is a critical factor for competitive advantage and rapid adaptation to market dynamics (Clark, 1989).
In this dynamic scenario, project management assumes a strategic role, especially in schedule optimization. The predictive, or traditional, approach, according to the Project Management Institute (PMI, 2017), prioritizes detailed planning before execution, with clear definition of scope, schedule, costs, and risks. The acquisition phase is particularly critical, as it involves supplier selection and the definition of deadlines that will guide the entire product lifecycle. An assertive schedule from this initial stage is fundamental for controlling and evaluating project efficiency (Bragadin, 2019). However, the complexity of automotive projects and time and resource constraints often lead to the development of less detailed schedules, which can compromise success. Reports from The Standish Group (2009) indicate that a considerable portion of projects do not meet deadlines or costs, highlighting the need for rigorous time management.
To face these challenges and ensure predictability, the implementation of practices such as cross-functional teams and concurrent engineering is crucial (Karlsson and Ahlström, 1996). Although effective in overlapping activities, they introduce inherent risks, such as rework and revalidation, which demand careful evaluation. Risk management thus becomes indispensable. Tools like Preliminary Risk Analysis (PRA) and Failure Mode and Effects Analysis (FMEA) are essential for identifying, assessing, and prioritizing risks, supporting mitigation decisions (Carvalho and Souza, 2023). Risk, intrinsically linked to uncertainty, refers to the probability of occurrence of events that affect project objectives (Keeling, 2014). Risk analysis, therefore, goes beyond probability calculations, encompassing the team’s perception of the severity of potential delays. For schedule optimization, the Critical Path Method (CPM) is used to identify the critical path, the sequence of activities that defines the minimum project duration. Once identified, compression techniques such as *crashing* (allocating additional resources) and *fast-tracking* (parallel execution of activities) can be applied to reduce the total timeframe (PMI, 2017). The integration of these techniques requires careful risk analysis to preserve quality and technical requirements.
The complexity of automotive development and the pressure for deadlines demand an integrated approach to schedule optimization and robust risk management. Schedule compression, without analysis of inherent risks, can compromise the project’s quality and technical feasibility. It is urgent to develop methodologies for structured and controlled schedule reduction in the sector. This study is justified by the pursuit of greater predictability and assertiveness in project planning, especially in the acquisition phase, where decisions impact the entire product lifecycle. Thus, the present work aims to analyze the application of schedule compression techniques and risk analysis tools in the development of an automotive product, aiming to reduce the project deadline in the acquisition phase, without compromising the quality of deliverables and technical requirements.
2. Material and Methods
This work was characterized as an exploratory research, according to the classification proposed by Gil (2002). The main objective of this approach was to provide greater familiarity with the problem under study, making it more explicit and facilitating the refinement of ideas, as well as the formulation of relevant hypotheses for the investigation. The exploratory nature was fundamental for a deep understanding of the context and challenges faced in the development of automotive products.
Regarding the approach, the research adopted a predominantly qualitative one, complemented by quantitative information. The qualitative approach sought to understand phenomena in their complexity, considering the specific context in which they occurred, allowing for a rich and detailed analysis. The quantitative elements, in turn, contributed to the measurement and objective analysis of specific variables, offering empirical support to qualitative observations and strengthening the study’s robustness (Gil, 2002).
The study was conducted in a multinational company of German origin, large-sized, with a global operation of approximately 139 years and about 70 years of presence in the Brazilian market. The organization has strategic production units located in the Southeast and South regions of Brazil, being recognized for the development and manufacturing of components for commercial vehicles, with a focus on trucks and buses. This complex and competitive industrial environment served as the setting for the investigation.
The central unit of analysis was a specific project for the development of a new automotive product, intended for heavy vehicles. This project represented a strategic initiative for the company, aiming to increase export volume, expand annual revenue, and strengthen competitiveness in the international market. The project’s complexity lay in the need to develop two new components, covering design, supplier homologation, and the implementation of new assembly devices.
The project schedule, defined in the acquisition phase, presented a significant challenge due to the highly competitive environment, where multiple suppliers vied for the nomination. This scenario imposed strict time and resource constraints, conditioning the planning strategy. The research focused on the analysis and optimization of this schedule, seeking to balance competitiveness and technical feasibility to meet client requirements without compromising quality.
The project team, composed of professionals from different areas involved in product development, acted as the main source of data and knowledge. These specialists actively participated in structuring the schedule and in the risk identification sessions. The diversity of their perspectives and experiences was crucial for the breadth and depth of the analyses performed, ensuring a multifunctional view of the project’s challenges and opportunities.
The project was structured into work packages, named “Work Packages” (WP), each containing a set of specific activities. This structuring aimed to organize planning, facilitate schedule control, and ensure compliance with technical and quality requirements. The activities were defined based on consolidated practices from the automotive industry, previous experiences in similar projects, and internal organizational guidelines, including the project management ruler.
The execution deadlines for each activity were established by specialists from the respective areas, using historical estimates from previous projects and internal organizational standards. Reference deadlines, assessed as optimal for each stage, were considered, assuming normal development conditions. The precedence relationships between activities, such as Finish-to-Start (FS) and Start-to-Start (SS), were defined according to the PMBOK® (PMI, 2017), including lag periods when necessary.
Based on these definitions of activities, deadlines, and precedence relationships, the initial macro project schedule was developed. This schedule was structured following the predictive approach to project management, serving as a starting point for subsequent optimization and risk analyses. The initial representation allowed for a comprehensive view of the automotive product development cycle, from conception to the start of mass production.
To identify the critical path and optimize the schedule, the Critical Path Method (CPM) was applied to the project activities. CPM is a fundamental technique for determining the minimum project duration and identifying critical activities, which are those without float and whose delay directly impacts the project’s final deadline. The application of the method allowed for the visualization of the activity network and its interdependencies.
The determination of the earliest start and finish dates (ES and EF) and latest start and finish dates (LS and LF) was performed for each activity, allowing the calculation of total float in months. Activities with zero total float were identified as part of the critical path, indicating that any delay in their execution would result in an equivalent delay in the project as a whole. This analysis was crucial for directing optimization efforts.
For schedule optimization, techniques of compression and parallel execution of activities were evaluated, according to the recommendations of the PMBOK® (PMI, 2017). Schedule compression, or *crashing*, involved the analysis of critical activities and the possibility of allocating additional resources to reduce their duration, prioritizing the project over other organizational demands, considering the potential impacts on costs and risks.
Additionally, the parallel execution technique, or *fast-tracking*, was evaluated. This technique involves checking the feasibility of overlapping activities originally planned sequentially. This approach aimed to reduce the total project duration, although it implied a greater exposure to risks of rework and revalidation. The application of these techniques was careful, considering the interdependencies, associated risks, and technical constraints of the project.
The identification of risks inherent in schedule compression strategies was a fundamental step. Initially, a brainstorming session was held with the project team, composed of professionals from various areas. This technique, widely used in project management, facilitated the collective generation of ideas and the exchange of experiences, allowing for the identification of a comprehensive set of potential risks associated with schedule optimization.
Complementarily, lessons learned from previous projects, which were recorded in a corporate database of the company, were analyzed. The objective was to identify recurring risks and situations previously experienced by the organization in similar projects. This approach allowed for a historical and contextualized view of the challenges, enriching the risk identification process and providing valuable *insights* for subsequent analysis.
After identification, the risks were submitted to a classification process using a probability and impact matrix, with the participation of the project team. This technique, recommended by the PMBOK® (PMI, 2017), allowed for the evaluation of each risk regarding its probability of occurrence and its potential impact on the project. The probability and impact classifications included categories such as very low, low, medium, high, and very high.
The probability and impact matrix used a color scale to facilitate the visual prioritization of risks. White regions indicated low priority, yellow represented medium priority, and red corresponded to high priority, demanding greater attention and definition of mitigation actions. This structured classification was essential for prioritizing risks and supporting response decisions, ensuring proactive management.
The classified risks were presented to the company’s management, along with the proposed mitigation actions. The decision on whether to accept or not accept the risks was based on previously defined criteria, considering the level of exposure, the organization’s mitigation capacity, and the potential impact on project deadlines and objectives. This step ensured that the compression strategies were evaluated in a structured manner and aligned with the study’s objectives.
The detailed analysis of risk acceptance, which underpinned the decision-making process, is presented below. This table summarizes the identified risks, the analysis of their acceptance, and the final decision, highlighting the criteria used for each choice. Understanding these elements was crucial for developing an optimized, leaner, and technically feasible schedule during the project acquisition phase.
Table 1. Risk analysis and acceptance for schedule optimization
|
Risk list |
Risk Acceptance Analysis |
Risk Acceptance |
|
1 Risk of resource allocation without return, should the project not be named |
Average probability and average impact. The cost of resource allocation is not high and the probability of project nomination is considered high. |
Accepted Risk |
|
2 Risk of insufficient time for revalidation (of design) |
Low probability and very high impact. Although the design is similar to previously validated solutions, lessons learned from previous projects indicate the possibility of needing revalidation. |
Unaccepted risk |
|
3 Risk of rework due to design changes after testing |
Average probability and low impact. Reworks are expected in this project phase and can be mitigated through the allocation of dedicated resources, if necessary. |
Accepted Risk |
|
4 Risk of rework in case of design changes |
Average probability and low impact. The occurrence of rework is considered acceptable at this stage, provided that exclusive resources are available for immediate action. |
Accepted Risk |
|
5 Risk of exclusion of supplier with longer lead time and potentially more competitive price |
Low probability and medium impact. Lessons learned indicate that suppliers with longer lead times tend to present lower price competitiveness, while other suppliers meet the expected deadlines and costs. |
Accepted Risk |
|
6 Risk of no time margin for rework in PPAP documentation |
Average probability and average impact. Previous projects indicate that rework in PPAP is recurrent, but with adequate reaction time, provided there is dedication of exclusive resources. |
Accepted Risk |
|
7 Risk of insufficient time for (process) revalidation |
Low probability and very high impact. Although the design is similar to previously validated solutions, lessons learned from previous projects indicate the possibility of needing revalidation, which may impact the product launch. |
Unaccepted risk |
Source: Original research results
After defining the risk response strategies, a new master schedule was developed, incorporating adjustments to critical activities and the parallel execution of steps that were previously sequential. This reformulation was not limited to a mechanical reduction of deadlines, but reflected a structured decision, based on the integrated analysis of schedule, risk, and technical feasibility. The objective was to maintain alignment with the project’s strategic objectives, ensuring the quality of deliverables.
3. Results and Discussion
The initial structuring of the project, outlined through the division into Work Packages (WPs) and specific activities, as detailed in Table 7 of the original material, represented a fundamental pillar for the application of schedule optimization and risk analysis methodologies. The approach of decomposing the work into 5 WPs, subdivided into a total of 23 activities, not only facilitated planning organization but also allowed for essential granularity for project control and monitoring. This practice is in line with the guidelines of the Project Management Institute (PMI, 2017), which emphasizes the importance of a well-defined Project Breakdown Structure (WBS) to manage complexity and ensure that all deliverables are considered. The clarity in defining each activity, from product design to final maritime transport, such as “Define product design, perform simulations, and create a bill of materials” (WP 1.1) or “Execute PPAP of components” (WP 2A.6 and 2B.6), is crucial to avoid ambiguities and rework, elements that can significantly compromise the project’s schedule and budget.
The relevance of this structuring transcends mere organization, directly impacting the project team’s ability to visualize the complete scope and interdependencies. By detailing each step, the study allowed specialists from each area, from product engineering to logistics, to contribute more precise estimates and identify potential bottlenecks. This multifunctional collaboration, as suggested by Karlsson and Ahlström (1996), is vital in complex product development projects, such as those in the automotive industry, where the integration of different knowledge and perspectives can accelerate the process and improve quality. The subdivision into activities also serves as a basis for resource allocation and responsibility definition, critical elements for efficient project execution. The absence of a robust WBS (Work Breakdown Structure), on the other hand, could lead to reactive management, with decisions based on intuition rather than concrete data, increasing the probability of schedule and cost deviations, as pointed out by studies from The Standish Group (2009) on project failures.
The definition of execution deadlines for each of the 23 activities, expressed in months, and the establishment of precedence relationships, as presented in Table 8 of the original material, were crucial steps for building the initial macro schedule. The assignment of deadlines by specialists from the respective areas, based on historical estimates and the organization’s internal standards, reflects a pragmatic and well-founded approach, seeking the greatest possible accuracy in a highly competitive environment. The use of precedence relationships such as Finish to Start (FS), Start to Start (SS), Finish to Finish (FF), and Start to Finish (SF), along with the inclusion of lags when necessary, strictly aligns with the best practices for schedule management described in the PMBOK® (PMI, 2017). These definitions are the backbone for any critical path analysis and schedule optimization.
The accuracy in estimating deadlines is a constant challenge in product development projects, especially in the automotive industry, where innovation and technical complexity are high. The reliance on historical data and professional expertise, while valuable, can introduce a degree of uncertainty, as discussed by Keeling (2014), who relates risk to the absence of complete information. However, the adopted methodology, by involving multiple specialists and considering internal references, minimizes this uncertainty as much as possible in the acquisition phase. Precedence relationships, in turn, are vital for modeling project logic, ensuring that activities are executed in the correct sequence and that dependencies are clearly understood. For example, the activity “Name supplier” (2a.2 and 2b.2) precedes “Monitor tooling construction” (2a.3 and 2b.3), an unquestionable logic for the development flow. The correct identification of these relationships is what allows the effective application of techniques such as the Critical Path Method (CPM), which will be discussed next, and is a prerequisite for any attempt at schedule compression.
The application of the Critical Path Method (CPM) methodology to the project activities proved to be an indispensable analytical tool for identifying critical activities and, consequently, for optimizing the schedule. As detailed in Table 2, determining the earliest (ESi) and latest (ESt) start and finish dates (ESi and ESt) for each activity allowed for the calculation of total float in months. Activities with zero total float were categorized as critical, indicating that any delay in their execution would directly impact the project’s final deadline. This approach is in full compliance with the PMBOK® (PMI, 2017), which defines the critical path as the sequence of activities that determines the minimum project duration, being fundamental for schedule control and the definition of optimization strategies. The analysis showed that the product development, supplier development, and process validation stages concentrated the majority of critical activities, highlighting their temporal sensitivity and, therefore, their greater exposure to the risk of delay.
Table 2. Application of the CPM methodology in each project activity
|
Activities |
Antecedent |
Term (months) |
Latency (months) |
CAI (Months) |
DCt (Months) |
DTi (Months) |
DTt (Months) |
Leave (Months) |
|
1.1 |
3 |
0 |
3 |
0 |
3 |
0 |
||
|
1.2 |
1.1 |
3 |
3 |
6 |
3 |
6 |
0 |
|
|
1.3 |
1.2 |
3 |
6 |
9 |
6 |
9 |
0 |
|
|
1.4 |
1.3 |
1 |
9 |
10 |
9 |
10 |
0 |
|
|
2a.1 |
1.1 |
7 |
+3 |
3 |
13 |
8 |
15 |
2 |
|
2a.2 |
2a.1 |
3 |
13 |
16 |
15 |
18 |
2 |
|
|
2a.3 |
2a.2 |
5 |
16 |
21 |
18 |
23 |
2 |
|
|
2a.4 |
2a.3 |
1 |
21 |
22 |
23 |
24 |
2 |
|
|
2a.5 |
2a.4 |
2 |
22 |
24 |
24 |
26 |
2 |
|
|
2a.6 |
2a.5 |
3 |
24 |
27 |
26 |
29 |
2 |
|
|
2b.1 |
1.1 |
7 |
+3 |
3 |
13 |
6 |
13 |
0 |
|
2b.2 |
2b.1 |
3 |
13 |
16 |
13 |
16 |
0 |
|
|
2b.3 |
2b.2 |
5 |
16 |
21 |
16 |
21 |
0 |
|
|
2b.4 |
2b.3 |
3 |
21 |
24 |
21 |
24 |
0 |
|
|
2b.5 |
2b.4 |
2 |
24 |
26 |
24 |
26 |
0 |
|
|
2b.6 |
2b.5 |
3 |
26 |
29 |
26 |
29 |
0 |
|
|
3.1 |
1.4 |
2 |
10 |
12 |
20 |
22 |
10 |
|
|
3.2 |
3.1 |
6 |
12 |
18 |
22 |
28 |
10 |
|
|
3.3 |
3.2 |
1 |
18 |
19 |
28 |
29 |
10 |
|
|
4.1 |
3.3; 2a.5; |
1 |
29 |
30 |
29 |
30 |
0 |
|
|
4.2 |
4.1 |
3 |
30 |
33 |
30 |
33 |
0 |
|
|
5.1 |
4.2 |
1 |
33 |
34 |
33 |
34 |
0 |
|
|
5.2 |
5.1 |
2 |
34 |
36 |
34 |
36 |
0 |
Source: Original research results
The critical path visualization, as illustrated in Figure 1, provided a clear understanding of the interdependencies and the sequence of activities that govern the total project duration. This network diagram is a powerful tool that allows project managers and their teams to visually identify where optimization efforts should be concentrated. Project management literature, such as Keeling (2014), reinforces that identifying the critical path is the first step for any schedule compression initiative, as interventions in non-critical activities, in isolation, do not result in a reduction of the total deadline. In the context of this study, clarity in identifying the critical path allowed attention to be directed towards the activities with the greatest impact, such as “Define product design” (1.1), “Manufacture prototype” (1.2), “Execute design validation tests” (1.3), “Freeze and release design” (1.4), and the activities related to supplier development (2b.1 to 2b.6), as well as the process validation steps (4.1 and 4.2). Concentrating efforts on these critical activities is an efficient strategy to optimize the schedule without wasting resources on activities with float.
Source: Original research results
For schedule optimization, schedule compression (*crashing*) and parallel execution (*fast-tracking*) techniques were evaluated and applied, according to the recommendations of the PMBOK® (PMI, 2017). The *crashing* technique involved analyzing critical activities and the possibility of allocating additional resources to reduce their duration, prioritizing the project over other organizational demands, always considering the potential impacts on costs and risks. For example, the activity “Define product design” (1.1) had its studies advanced, a compression strategy that, although it involves the risk of allocating resources without return if the project is not named, was considered viable. The *fast-tracking* technique, in turn, consisted of verifying the feasibility of overlapping activities originally planned sequentially, such as reducing latency after design freeze for the supplier pre-naming activities (2a.1 and 2b.1). This approach aimed to reduce the total project deadline, although it implied greater exposure to risks of rework and revalidation. Table 3 details the specific strategies adopted for each activity.
Table 3. Strategy for reducing activity lead times
|
Activity |
Original term (months) |
Brainstorm for deadline reduction |
Risk |
Time after reduction (months) |
Strategy |
|
1.1 |
3 |
Anticipate design studies during the acquisition phase |
1- Risk of resource allocation without return, should the project not be named |
2 |
Crashing |
|
1.2 |
3 |
There is no possibility of deadline extension |
|||
|
1.3 |
3 |
Consider performing design validation tests without anticipating rework due to test failures |
2- Risk of insufficient time for revalidation |
2 |
Crashing |
|
1.4 |
1 |
There is no possibility of deadline extension |
|||
|
2a.1 |
7 (3 months latency) |
Reduce latency after freezing design from 3 to 1 month |
3- Risk of rework due to design changes after testing |
7 (1 month latency) |
Fast tracking |
|
2b.1 |
|||||
|
2a.2 |
3 |
Anticipate supplier nomination phase activities during the pre-nomination phase |
4- Risk of rework in case of design changes |
2 |
Fast tracking |
|
2b.2 |
|||||
|
2a.3 |
5 |
Adopt a 4-month deadline for tooling manufacturing, disregarding the supplier with the longest lead time |
5- Risk of exclusion of supplier with longer lead time and potentially more competitive price |
4 |
Crashing |
|
2b.3 |
|||||
|
2a.4 |
1 |
There is no possibility of deadline extension |
|||
|
2b.4 |
3 |
There is no possibility of deadline extension |
|||
|
2a.5 |
2 |
There is no possibility of deadline extension |
|||
|
2b.5 |
2 |
There is no possibility of deadline extension |
|||
|
2a.6 |
3 |
Start the PPAP process in parallel with the production of the D samples, finishing in the following month |
6- Risk of no margin for rework in PPAP documentation |
Fast tracking |
|
|
2b.6 |
|||||
|
4.1 |
1 |
There is no possibility of deadline extension |
|||
|
4.2 |
3 |
Consider execution of process validation tests without provision for rework due to test failures |
7- Risk of insufficient time for revalidation |
2 |
Crashing |
Source: Original research results
The judicious application of these techniques, considering the interdependencies between activities, the associated risks, and the technical constraints of the project, is a crucial point. The literature, such as Clark (1989), emphasizes that agility in product launches is a critical factor for competitive advantage in the automotive industry. However, this agility cannot come at the expense of quality or technical feasibility. The decision to compress the schedule for activities such as “Consider execution of design validation tests without rework provision” (1.3) or “Adopt a 4-month deadline for tooling fabrication, disregarding the supplier with the longest lead time” (2a.3 and 2b.3) was made after careful analysis of the inherent risks. Schedule compression, when poorly managed, can lead to increased costs, reduced quality, and a higher probability of project failures. The integrated approach of optimization and risk analysis, therefore, sought a balance between the need for agility and the maintenance of product quality and technical robustness, as advocated by Schneider and Tanaka (2025) in their lean design principles.
The identification and classification of risks inherent to schedule compression strategies were fundamental steps to ensure the robustness of the planning. Initially, a brainstorming session with the project’s multidisciplinary team allowed for collective idea generation and experience sharing, resulting in the identification of a comprehensive set of potential risks. Complementarily, the analysis of lessons learned from previous projects, recorded in a corporate database, provided valuable insights into recurring risks and situations previously experienced by the organization. This combination of approaches, as suggested by Carvalho and Souza (2023), enriched the identification process, ensuring a holistic view of the challenges. After identification, the risks were subjected to a classification process using a probability and impact matrix, with the participation of the project team, a technique recommended by the PMBOK® (PMI, 2017). Each risk was assessed for its probability of occurrence (very low, low, medium, high, and very high) and its potential impact on the project (very low, low, medium, high, and very high).
The probability and impact matrix, as illustrated in Figure 2, used a color scale (white for low priority, yellow for medium, and red for high) to facilitate visual risk prioritization. This tool is crucial for qualitative risk analysis, allowing the team and management to quickly understand which risks demand greater attention and definition of mitigation actions. In the context of this study, the classification obtained showed that two risks were in the high criticality range (red quadrant) and the others in the moderate criticality range (orange quadrant). High-priority risks included “Risk of rework due to design changes after testing” (Risk 3) and “Risk of insufficient time for revalidation (of process)” (Risk 7), both with the potential for significant impact on the project’s schedule and quality. The use of the matrix therefore allowed not only for the prioritization of identified risks but also for the substantiation of decision-making regarding the acceptance, mitigation, or rejection of the proposed compression alternatives, ensuring a greater balance between schedule reduction and risk exposure control.
Source: Original research results
The discussion on risk acceptance, although Table 1 detailing it was presented in the Material and Methods section, is an integral component of the results and discussion, as it reflects the strategic decisions made. The project team, in conjunction with company management, evaluated each classified risk, considering the proposed mitigation actions, the level of residual exposure, and the organization’s capacity to absorb the associated impacts. The decision to accept risks such as “Risk of resource allocation without return, should the project not be named” (Risk 1) or “Risk of rework due to design changes after testing” (Risk 3) was based on the assessment that the cost of mitigation would be low or that the probability of occurrence was medium with low impact, and that the organization had adequate response capacity. On the other hand, risks such as “Risk of insufficient time for revalidation (of design)” (Risk 2) and “Risk of insufficient time for revalidation (of process)” (Risk 7) were considered unacceptable due to their low probability but very high impact, indicating that the organization was unwilling to assume the risk of compromising product quality or launch.
This structured approach to risk acceptance, as advocated by PMI (2017), is a strategic decision-making process that requires a balance between the potential benefit of schedule compression and exposure to adverse events. Risk acceptance does not mean ignoring risks, but rather recognizing that the cost or effort to mitigate them may outweigh the potential benefit, or that the level of exposure is within the organization’s tolerance limits. Clarity in these decision criteria, discussed and approved by management, is fundamental for project governance and for aligning expectations among stakeholders. Risk analysis, therefore, is not an isolated exercise, but an integral part of the schedule optimization process, ensuring that schedule reductions are sustainable and do not compromise the project’s strategic objectives, such as increasing export volume and strengthening competitiveness in the international market.
After defining the risk response strategies and accepting the residual risks, a new macro schedule was developed, incorporating adjustments to critical activities and the parallel execution of steps that were previously sequential. This optimized schedule, although Figure 6 presenting it is not included again here, materializes the managerial decisions made throughout the evaluation process, demonstrating the feasibility of reducing the timeline without compromising the technical requirements and the quality of the planned deliverables. The reformulation of the schedule was not limited to a mechanical reduction of deadlines, but reflected a structured decision, based on the integrated analysis of timeline, risk, and technical feasibility, seeking to maintain alignment with the project’s strategic objectives. The internal approval of this optimized schedule by the company’s management, as synthesized in Table 1 (already discussed) and visualized in Figure 6, represented the validation of the adopted schedule compression strategy, indicating that the residual risk level was considered compatible with the organization’s objectives and execution capacity.
The optimized schedule, once internally approved, was forwarded to the client along with the quotation, a strategic step in the project acquisition phase. This action not only reinforced the competitiveness of the proposal presented but also demonstrated the company’s ability to respond to market demands with agility and robust planning. In an automotive sector characterized by intense time pressure and the need for rapid launches, as pointed out by Masoumi et al. (2019), the ability to present a lean and technically viable schedule is a significant competitive advantage. The integration of risk management with schedule optimization allowed the company not only to promise shorter deadlines but to do so with a clear understanding of the risks involved and the strategies to mitigate them, increasing predictability and confidence in the project’s success.
Finally, the comparison between the initial macro schedule and the optimized schedule, presented in Figure 3, strongly evidences the effectiveness of the adopted methodology. The analysis revealed a total reduction of 7 months in the project timeline, a significant gain achieved mainly through the compression of activities belonging to the critical path and the parallel execution of activities previously sequenced linearly. This timeline reduction is a direct result of the combined application of *crashing* and *fast-tracking* techniques, supported by a structured risk analysis. It is observed that the changes were concentrated, above all, in the product development and supplier stages, which were identified as the most critical in the CPM analysis. The preservation of client milestones and the start of production (SOP) in the optimized schedule demonstrates the technical feasibility of the proposed optimization and the commitment to delivering value to the client.
Source: Original research results
The 7-month reduction in the total project timeline is a remarkable achievement, especially in a complex industrial environment like the automotive sector, where each month of anticipation can represent millions in revenue and a crucial competitive advantage. Clark (1989) already highlighted the importance of reducing vehicle launch time as a critical factor for ensuring competitive advantage, allowing companies to respond more agilely to market changes. The ability to shorten the product development cycle, without compromising quality or technical feasibility, is an indicator of project management maturity and a strategic factor for increasing competitiveness in complex industrial environments, such as the one studied. The effectiveness of risk analysis will be continuously evaluated during the project execution phase, through systematic monitoring of the schedule by the project manager, focusing on meeting established deadlines and maintaining the quality of deliverables. This study, therefore, not only demonstrates the feasibility of schedule compression with risk management, but also offers a practical model for other organizations seeking to optimize their product development processes in a scenario of increasing demand for agility and efficiency.
4. Conclusion
It is concluded that the objective was achieved, demonstrating the effectiveness of applying schedule compression techniques and risk analysis tools in the development of an automotive product. The study managed to reduce the project deadline by seven months in the acquisition phase, without compromising the quality of deliverables and technical requirements. The integration of the Critical Path Method (CPM) with *crashing* and *fast-tracking* techniques, combined with a qualitative risk analysis, proved to be a robust approach to optimize the schedule. This methodology not only accelerated the product launch time but also strengthened decision-making, promoting greater transparency and alignment among teams, which is crucial for competitiveness in the automotive sector.
However, it is important to consider the limitations of this study, which focused on a single case and the project acquisition phase. Risk analysis was predominantly qualitative, and the duration estimates for the CPM were optimistic, without in-depth probabilistic analysis due to time constraints. For future studies, it is suggested to conduct longitudinal monitoring to validate the effectiveness of schedule compression and risk mitigation strategies during the complete project execution. It is also recommended to apply quantitative risk analyses and replicate the methodology in multiple projects or in different contexts of the automotive industry, in order to generalize the results and deepen the understanding of schedule and risk management.
Bibliographic References
Bragadin, 2019 [Referência completa não encontrada no documento original]
Carvalho, Ismael Almeida; Souza, Mauro Cezar Aparício de. 2023. Análise de riscos em projetos de engenharia de produção: metodologias e ferramentas. Revista Ibero-Americana de Humanidades, Ciências e Educação – REASE, São Paulo, v. 9, n. 11, p. 2443–2458, nov. 2023. DOI: 10.51891/rease.v9i11.12641.
Clark, Kim; Fujimoto, Takahiro. 1989. Reducing the time to market: the case of the world auto industry. Design Management Journal, v. 1, n. 1, Fall 1989. Design Management Institute.
Ferreira Filho, Valter Silva. 2022. O governo como indutor da indústria automotiva: proposições para uma política industrial automotiva brasileira baseada na substituição de frota. 2022. Tese (Doutorado em Engenharia Mecânica – Projetos, Gestão e Otimização) – Faculdade de Engenharia de Guaratinguetá, Universidade Estadual Paulista “Júlio de Mesquita Filho”, Guaratinguetá, 2022.
Gil, Antonio Carlos. 2002. Como elaborar projetos de pesquisa. 4. ed. São Paulo: Atlas.
Karlsson, Christer; Ahlström, Pär. 1996. The difficult path to lean product development. Journal of Product Innovation Management, v. 13, n. 4, p. 283–295.
Keelig, Ralph. 2014. Gestão de projetos: uma abordagem global. 3. ed. São Paulo: Saraiva.
Masoumi, S. M.; Kazemi, N.; Abdul-Rashid, S. H. 2019. Sustainable supply chain management in the automotive industry: a process-oriented review. Sustainability, Basel, v. 11, n. 14.
Project Management Institute. 2017. Um guia do conhecimento em gerenciamento de projetos (Guia PMBOK®). 6. ed. Newtown Square, PA: Project Management Institute.
Schneider, Martin; Tanaka, Sophia. 2025. Lean design principles for accelerating product development cycles in automotive manufacturing. [Artigo técnico].
The Standish Group International. 2009. CHAOS summary 2009 report. Boston: The Standish Group International. Disponível em: https://www.standishgroup.com. Acesso em: 25 set. 2025
United States Department of Transportation. 2017. Beyond traffic 2045: trends and choices. Washington, D.C.: U.S. Department of Transportation. Disponível em: https://www.transportation.gov/BeyondTraffic. Acesso em: 30 set. 2025
Wolff, Mariana Gonçalves de Carvalho; Caldas, Marco Antonio Farah. 2018. A model for the evaluation of Brazilian road transport: a sustainable perspective. Journal of Advanced Transportation, v. 2018, Article ID 5274789, p. 1–12. DOI: 10.1155/2018/5274789.
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