Servicios
Descargas
Buscar
Idiomas
P. Completa
Entrepreneurial Orientation as support in solving the challenges of Agile Methods adoption: A case study in a Brazilian startup
Vanessa Blas Garcia; Cristina Dai Prá Martens; Renato Penha;
Vanessa Blas Garcia; Cristina Dai Prá Martens; Renato Penha; Mauro Luiz Martens
Entrepreneurial Orientation as support in solving the challenges of Agile Methods adoption: A case study in a Brazilian startup
A Orientação Empreendedora como apoio na solução dos desafios da adoção de Métodos Ágeis: Um estudo de caso em Startup brasileira
Orientación Emprendedora como apoyo en la resolución de los desafíos de la adopción de Métodos Ágiles: Un estudio de caso en una startup brasileña
REGEPE Entrepreneurship and Small Business Journal, vol. 12, no. 2, e2404, 2023
Associação Nacional de Estudos em Empreendedorismo e Gestão de Pequenas Empresas
resúmenes
secciones
referencias
imágenes

Abstract: Study objective: empirically evaluate how the dimensions of Entrepreneurial Orientation (EO) can help solve the challenges of Agile Method adoption (AM). Methodology/approach: single case study in a software startup. Key findings: confirmation of challenges in adopting AM across three dimensions (people, processes, and management and organization) in the studied startup, and identification of which dimensions of EO contribute most to solving these challenges. Relevance/originality: although EO and its dimensions are recognized by the interviewees as potential actions to solve the challenges of AM adoption, they are not encouraged when the team is allocated at the client's site due to cultural influence. This research is relevant as it aims to help understand these challenges and suggest ways to overcome them. Theoretical/methodological contributions: as an academic contribution, this study advances research on the adoption of AM and EO, as well as the relationship between these topics. Social/management contributions: understanding the inherent challenges in adopting and using AM and promoting actions that can assist in solving these challenges through the utilization of EO concepts.

Keywords: Agile methods, Entrepreneurial orientation, Startup.

Resumo: Objetivo do estudo: avaliar empiricamente como as dimensões da Orientação Empreendedora (OE) podem auxiliar na solução dos desafios da adoção de Métodos Ágeis (MA). Metodologia/abordagem: estudo de caso único em uma startup de software. Principais resultados: confirmação da existência de desafios para a adoção dos MA em três dimensões (pessoas, processos, e gestão e organização), na startup foco do estudo, e de quais dimensões da OE mais contribuem para a solução desses desafios. Relevância/originalidade: embora a OE e suas dimensões sejam reconhecidas pelos entrevistados como possíveis ações para solucionar os desafios para a adoção de MA, elas não são incentivadas quando o time é alocado no cliente, por influência cultural. A pesquisa é relevante, pois tem a finalidade de ajudar a compreender tais desafios e de sugerir formas para os resolver. Contribuições teórico/metodológicas: como contribuição acadêmica, este estudo avançou nas pesquisas sobre a adoção de MA e a OE, bem como acerca da relação entre os tópicos. Contribuições sociais/para a gestão: entendimento dos desafios inerentes à adoção e à utilização dos MA, e incentivo de ações capazes de auxiliar na solução desses desafios, a partir da utilização dos conceitos de OE.

Palavras-chave: Métodos ágeis, Orientação empreendedora, Startup.

Resumen: Objetivo del estudio: evaluar empíricamente cómo las dimensiones de la Orientación Emprendedora (OE) pueden ayudar a resolver los desafíos de la adopción de Métodos Ágiles (MA). Metodología/enfoque: estudio de caso único en una startup de software. Principales resultados: confirmación de la existencia de desafíos en la adopción de MA en tres dimensiones (personas, procesos y gestión y organización) en la startup objeto de estudio, y qué dimensiones de la OE contribuyen más a resolver estos desafíos. Relevancia/originalidad: aunque los entrevistados reconocen que la OE y sus dimensiones son posibles acciones para solucionar los desafíos de la adopción de MA, no se fomentan cuando el equipo es asignado al cliente debido a la influencia cultural. Esta investigación es relevante, ya que tiene como objetivo ayudar a comprender estos desafíos y sugerir formas de superarlos. Contribuciones teóricas/metodológicas: como contribución académica, este estudio avanza en la investigación sobre la adopción de MA y la OE, así como en la relación entre estos temas. Contribuciones sociales/para la gestión: comprensión de los desafíos inherentes a la adopción y utilización de MA, y fomento de acciones que puedan ayudar a resolver estos desafíos mediante el uso de los conceptos de la OE.

Palabras clave: Métodos ágiles, Orientación emprendedora, Startup.

Carátula del artículo

Artigos

Entrepreneurial Orientation as support in solving the challenges of Agile Methods adoption: A case study in a Brazilian startup

A Orientação Empreendedora como apoio na solução dos desafios da adoção de Métodos Ágeis: Um estudo de caso em Startup brasileira

Orientación Emprendedora como apoyo en la resolución de los desafíos de la adopción de Métodos Ágiles: Un estudio de caso en una startup brasileña

Vanessa Blas GarciaAUTHOR BIOGRAPHY
Universidade Nove de Julho (UNINOVE), Brasil
Cristina Dai Prá MartensAUTHOR BIOGRAPHY
Universidade Nove de Julho (UNINOVE), Brasil
Renato PenhaAUTHOR BIOGRAPHY
Universidade Nove de Julho (UNINOVE), Brasil
Mauro Luiz MartensAUTHOR BIOGRAPHY
Universidade Paulista (UNIP), Brasil
REGEPE Entrepreneurship and Small Business Journal, vol. 12, no. 2, e2404, 2023
Associação Nacional de Estudos em Empreendedorismo e Gestão de Pequenas Empresas

Received: 15 June 2022

Revised: 11 November 2022

Accepted: 23 January 2023

Published: 27 June 2023

Funding
Funding source: Support from Call Universal MCTIC/CNPq 2018 resources
Contract number: 433080/2018-3
Award recipient: Vanessa Mesquita Blas Garcia
INTRODUCTION

Agile Methods (AM) can be defined as a set of methods based on iterative and incremental development, which promotes adaptive planning, evolutionary construction, and delivery, while encouraging a quick and flexible response to change (Beck et al., 2001; Silva et al., 2020).

The movement that created the Agile Manifesto - the foundation for all AM frameworks - recognized the need for organizations to deal with volatile management environments (Beck et al., 2001).

Since then, AM has become popular among companies aiming to create high-quality products in less time (Serrador & Pinto, 2015) and stands out in project management because it requires more speed (Söderlund & Geraldi, 2012), a focus on open communication, and intense interaction and collaboration with customers (Li et al., 2011). Prioritization, simplified development processes, increased predictability, and accelerated product delivery are, therefore, some of the motivations for adopting AM (Beck et al., 2001).

Agile Methods (AM) reflect the organizational culture; therefore, while the opportunities and benefits of AM are appealing, organizations must exercise caution in their adoption or integration into existing practices, evaluating whether they are ready to deal with the provided agility (Nerur et al., 2005). Such agility requires support from top management due to the level of entrepreneurship and the risks involved in achieving flexibility, adaptability, and empowerment of the project team - factors necessary to meet the demands of AM's change requests (Sheffield & Lemétayer, 2013).

Challenges related to organizational cultural issues continue to be the primary impediment to the adoption and scaling of AM (Version One, 2020). These challenges are not inherent characteristics but rather barriers, primarily caused by their people-centric nature (Gandomani & Nafchi, 2016).

In the context of entrepreneurship, agility is associated with creativity, initiative, and the ability to set and achieve goals, helping to gain a competitive advantage (Ragin-Skorecka, 2016). At the organizational level, entrepreneurship conceptualized as Entrepreneurial Orientation (EO) can contribute to the adoption of AM (Garcia, Martens et al., 2021; Garcia et al., 2022; Kaufmann et al., 2020).

In this sense, EO can be understood as the mindset of key decision-makers within an organization, which can characterize it as a culture of entrepreneurial decision-making. Among the subjects studied in the fields of entrepreneurship and management, EO emerges as one of the most relevant and crucial topics in the organizational context (Frare et al., 2021).

According to Garcia, Martens et al. (2021), there is evidence in the literature that there are common characteristics between AM and EO, with EO favoring the incorporation of agile practices - the foundation of agile project management.

In the literature, the application of AM is primarily focused on small, medium, and large established companies, resulting in few studies involving software development startups (Souza et al., 2019).

According to Paternoster et al. (2014), the term startup still lacks a single, universally accepted definition within the scientific community, but it is not related to the size or age of the company. However, there is consensus regarding the encouragement of an environment for the development of new products and/or services (Noronha et al., 2022). This study adopts the concept that describes startups as evolving companies with development and processes focused on product and service innovation.

Software startups are characterized by various challenges, highly uncertain conditions, lack of resources, and operating in rapidly growing markets (Paternoster et al., 2014). Similar to AM, software startups aim for rapid product delivery to their customers (Kalyanasundaram, 2018). Therefore, AM holds value in providing startups with improved software development practices (Souza et al., 2019).

In recent years, startups have attracted increasing attention, both from entrepreneurs seeking to capture new business opportunities and from large companies aiming for rapid growth to become more agile (Silva et al., 2020).

Despite entrepreneurship being one of the central topics addressed in research on startups (Noronha et al., 2022), studies that focus on supporting the activities of these companies, particularly in providing guidance to professionals in decision-making to avoid choices that could lead to business failure, are still scarce (Paternoster et al., 2014).

There is a growing emergence of startups involved in software development, and limited studies have linked the failure of these businesses to product creation flaws, without investigating the factors that affect the selection or adoption of AM, as these ventures often lack the use of appropriate methodology (Mkpojiogu et al., 2019; Silva et al., 2020). In this regard, it is worth noting that, according to Silva et al. (2020), the majority of research on AM published recently is descriptive, with few case studies and rare empirical applications.

To empirically evaluate how dimensions of Entrepreneurial Orientation can assist in addressing the challenges of Agile Methods adoption, this study begins with the following question: How can the challenges of Agile Methods adoption be solved with the dimensions of Entrepreneurial Orientation?

To answer the research question and achieve the proposed objective, a single case study was conducted in a software startup. The study proposes that the dimensions of EO can assist in addressing the challenges of AM adoption.

LITERATURE REVIEW
Challenges of Agile Methods (AM)

The adoption of AM in an organization is a growing challenge, as agility, despite being a difficult concept to define, should be based on the values and principles stated in the Agile Manifesto (Gregory et al., 2016). Even when following such a manifesto, AM is not a one-size-fits-all approach, with differences mainly in team size, duration of each cycle, emphasis on activities, and feedback for change (Nerur et al., 2005).

There is a multitude of frameworks and agile practices to adopt or adapt, with some deserving special mention. Scrum, one of the main ones, is composed of feedback loops where development is done by a self-organizing team for incremental deliveries, initiated by planning and concluded with reviews (Schwaber & Sutherland, 2011).

ScrumBan, on the other hand, is a hybrid methodology (combining Scrum and Kanban) that allows teams to utilize waste elimination concepts from Kanban and adapt to the requirements and interests of stakeholders, similar to Scrum (Ladas, 2009).

Kanban is a part of the Toyota Production System's Just-In-Time (JIT) system from the 1950s, aiming to do only what is necessary, when necessary, and in the necessary quantity (Sugimori et al., 2007).

In Lean Startup, which aims to assist innovation-oriented entrepreneurs through the development and launch of new products in the market, the riskiest parts are identified, and a minimum viable product (MVP) is provided to be systematically tested, planning modifications for the next iteration (Ries, 2008; 2011).

Finally, there is Xtreme Programming (XP), a development methodology widely used in startups due to its reduced process costs and low documentation requirements (Paternoster et al., 2014).

Organizational cultures that are conducive to innovation can adopt AM more easily than those mediated by bureaucracy and formalization (Nerur et al., 2005). Just like in large companies, the process of adopting AM in startups depends on the organizational environment, given the necessary adaptation to integrate AM into existing processes (Mkpojiogu et al., 2019). To assist startups in the challenge of managing innovation and validating the business model, certain AM are more suitable, such as Lean Startup (Silva et al., 2020).

Startups require flexibility in the application of methodologies to accommodate frequent changes in the development environment. As a result, AM have been considered one of the most viable ways for these companies, as they embrace changes and employ a rapid, iterative, and incremental approach (Paternoster et al., 2014). Consequently, AM are becoming increasingly common in software startups due to their flexible, lightweight, and adaptive nature, with a strong focus on close collaboration with the customer throughout the development process (Bosch et al., 2013).

Regarding the contribution of AM to the success of organizations, the choice and adaptation of the appropriate methodology can be highlighted as support for management, mindset, alignment, training, and coaching (Dikert et al., 2016).

It is important to note that tools alone cannot make software development successful; therefore, it is necessary to train the human capital of the company to use them correctly (Nerur et al., 2005), as each individual (or role/function in the organization) has a specific impact on an agile project (Coram & Bohner, 2005).

Entrepreneurial Orientation (EO)

Understood as a general or enduring direction of entrepreneurial thinking, an inclination towards the interests of the firm (Covin & Lumpkin, 2011), and the application or practice of entrepreneurship in the organizational context (Garçon & Nassif, 2021; Martens et al., 2016), EO facilitates the discovery of new opportunities and the creation of competitive advantage (Carmona et al., 2020).

Considering that businesses with higher EO tend to be more successful than those with lower EO, authors affirm that this orientation can positively influence the performance of an organization (Covin & Lumpkin, 2011; Martens et al., 2018; Oblog et al., 2010; Rauch et al., 2009).

EO can be reflected in methods, practices, and management or decision-making styles, according to the entrepreneurial posture (Freitas et al., 2012). According to Lumpkin and Dess (1996), there are important factors to characterize and distinguish entrepreneurial processes, grouped into five dimensions of a firm's EO: autonomy, innovativeness, risk-taking, proactiveness, and competitive aggressiveness.

The "autonomy" dimension is characterized by the presence of a culture that promotes independent action and the pursuit of opportunities without social constraints (Freitas et al., 2012). Autonomous behavior has been the subject of research in small businesses, investigating leadership centralization and authority delegation (Martens & Freitas, 2008).

The "innovativeness" of an organization can be observed through the amount of financial resources invested in innovation activities and the level of human resources committed to them, the number of new products/services, and the frequency of change in product/service lines (Freitas et al., 2012).

Innovation is more common when there are strong market pressures (Martens & Freitas, 2008), which is an important characteristic for the use of AM in organizations. According to these authors, innovativeness manifests as an individual act to innovate (Martens & Freitas, 2008), but as employees engage at the team level, knowledge sharing can increase and enhance decision-making for new ideas and new knowledge (Covin et al., 2020).

"Risk-taking" can be considered a mediator between risk preferences and risk behavior as it affects the likelihood of a person behaving more or less riskily (Lumpkin & Dess, 1996). This dimension is associated with (a) the degree of risk reflected in various resource allocation decisions, denoting a criterion and/or a pattern for decision-making at the organizational level (Martens & Freitas, 2008), and (b) how willing the firm is to break away from what is tried and tested to venture into the unknown in pursuit of high returns, seizing market opportunities (Wiklund & Shepherd, 2005).

The dimension of "proactiveness" is related to the future perspective and the market leader's opportunity search, as it drives organizations to forecast and act in anticipation of future demand in order to seize opportunities (Rank et al., 2015).

For proactiveness to occur, the organization must allow and encourage employees to take action for value creation. Trust and commitment are no longer focused solely on the manager but rather on goals and objectives for improved performance (Covin et al., 2020). Management is crucial in this context, as an entrepreneurial manager seeks the organization's growth with vision and imagination to explore emerging opportunities (Martens & Freitas, 2008).

Lastly, "competitive aggressiveness" refers to a company's propensity to directly and intensely challenge its competitors to gain entry or ascend in the market (Lumpkin & Dess, 1996). Some evidence of competitive aggressiveness can be seen in managerial behavior by allocating resources to gain market positions more quickly than competitors (Martens & Freitas, 2008).

In the context of small businesses, performance improvement relies on an orientation toward innovation, the willingness to take risks, and the encouragement of employee proactivity (Wiklund & Shepherd, 2005).

Approximation between AM and the dimensions of the EO

The reviewed literature clearly identifies a significant relationship between the characteristics (values and principles) of AM and the dimensions of EO. Recent research has also provided evidence of a positive relationship (Garcia, Martens et al., 2021; Garcia et al., 2022; Garcia, Martens & Martens, 2021). Furthermore, companies with EO operate in contexts characterized by uncertainty and learning orientation (Covin & Wales, 2019), which are ideal for the use of MA.

Autonomy is positively related to the practices used in AM (Tripp et al., 2016), which encourage members of organizational teams to engage in activities that increase their level of autonomy (Tripp et al., 2016). In this regard, the way leaders facilitate team autonomy significantly impacts task completion (Maruping et al., 2009).

Several best practices associated with AM are linked to self-organization, shared leadership, and proactiveness (Salin, 2017). To overcome the challenges associated with implementing AM, active members need to have proactive profiles, future-focused attitudes, self-monitoring abilities, and enhanced self-awareness (Mustafa & Sönmezisik, 2020).

Proactive organizations monitor trends, identify future customer needs, and anticipate changes in demand or problems (Martens & Freitas, 2008). They exhibit flexibility, measured by a team's efforts to create something easily modifiable in case of changing requirements (Conboy, 2002). Thus, even if change is not actually initiated, measures can be taken to anticipate it, minimizing its negative impact, and maximizing the potential for benefiting from it (Conboy & Fitzgerald, 2004).

In general, companies that use AM empower people, have a results-oriented approach, exhibit entrepreneurial and innovative leadership, and embrace risk-taking (Strode et al., 2009). Regarding business risks, practices for risk management are recommended for the Product Owner (PO), while the development team is responsible for managing technical risks (Tavares et al., 2019). In the context of startups, similar to risk-taking, there is uncertainty and resource commitment in launching a new product (Linton, 2019).

AM are used in complex adaptive systems, where individuals interact to create innovative outcomes (Highsmith & Cockburn, 2001). This interaction, within an innovative and entrepreneurial organizational culture, is manifested through the pursuit of opportunities, entrepreneurial leadership, the creation of collaborative cross-functional teams, and informal communication flows (Ghezzi & Cavallo, 2020). Additionally, as AM involve adaptive systems, flexibility, and quick response to changes in requirements are necessary conditions to sustain and enhance competitive advantage (Siakas et al., 2005).

Considering the interconnection between the topics, a review was conducted to shape the research questions and emphasize points for the case study. The review helped conceptualize the research and build a theoretical framework to support its development (Yazan, 2015) (Table 1). The relationship between the presented concepts and the proposition of this study is depicted in Figure 1.

Table 1

Conceptual framework: EO dimensions and AM challenges


Table 1
Conceptual framework: EO dimensions and AM challenges
Note: Elaborated by the authors.

Note: Elaborated by the authors.

Figure 1

Modelo conceitual do estudo


Figure 1
Modelo conceitual do estudo
Note: Elaborated by the authors.

Note: Elaborated by the authors.

RESEARCH METHOD

This article employed an exploratory case study method (Yin, 2015) conducted in a software startup. A single case study can be used in the preliminary stages of developing a new theory when relevant variables are still being explored, especially when there are many situations where studying a particular aspect sheds light on valuable insights about a specific situation (Mariotto et al., 2014).

According to Miller (2011), the specificity of the context may limit generalization; however, as a positive aspect, it can generate more refined and empirically valid knowledge.

Therefore, following the proposal by Merriam (1998), this study went through the following stages: literature review, construction of a theoretical framework, identification of a problem to be investigated, formulation of research questions, and selection of the sample (intentional).

The company focused on in this study is a Brazilian software startup with over 15 years of operation and 80 employees. Its selection was based on several aspects that aligned with the research objective, namely, a company with a present entrepreneurial culture and challenges in understanding the adoption of AM in project management.

According to Yazan (2015), a case study should focus on a specific situation, event, program, or phenomenon. Most recent studies do not focus on startups because these companies typically do not adopt AM (Mkpojiogu et al., 2019). Therefore, this study, by encompassing the adoption of AM and entrepreneurship in startups, can contribute to the expansion of the literature on the subject.

To assess different perceptions, from project management operations to top management direction, interviews were conducted with professionals from three areas of the company: two professionals from each role established in the agile scrum framework (scrum master - SM, product owner - PO, and development team), two human resources analysts, and the two owner partners (Table 2).

Table 2

Characterization of respondents


Table 2
Characterization of respondents
Note: SM = Scrum master. PO = product owner. Note: Elaborated by the authors.

Note: SM = Scrum master. PO = product owner. Note: Elaborated by the authors.

In this research, data collection was conducted through semi-structured interviews, which were carried out in person at the location where the professionals work, either at the consultancy or at the client's site. This type of interview allows the researcher to follow a set of predefined questions in the context of an informal conversation, with the main advantage being the possibility of obtaining a better sample of the population of interest (Boni & Quaresma, 2005).

As a data collection tool in a case study, interviews should follow a script, considering the introduction of the interview, the interaction between the interviewer and the respondent, the recording, and the transcription process (Yazan, 2015).

To facilitate the flow of the interviews in this study, they were divided into three parts: (1) characterization of the interviewee; (2) presentation of the main challenges of AM and dimensions of EO; and (3) identification of the dimensions of the EO that the interviewees consider most important for addressing the challenges of AM in the company. The data were then subjected to content analysis (Bardin, 2004), a technique that considers the interviewer's perspective, the context, and the intended effects, aiming to derive interpretations from inferences.

All interviews were recorded with the permission of the interviewees, and the confidentiality of the obtained information was ensured. The "Dictate" tool in Microsoft Word was used for transcription, which listens to the recording and transcribes it into a document.

The analysis of the interviews was conducted by the researchers, based on the concepts presented for the challenges of AM and dimensions of EO. All transcriptions were analyzed in Microsoft Excel, with the separation and categorization of key excerpts that aligned with the concepts of AM challenges and EO dimensions, as found in the literature. These excerpts were organized in spreadsheets for the assessment of convergence of the collected information.

RESULTS ANALYSIS

The analysis of the results was divided into three parts, aiming to: (1) analyze the presence of AM challenges within the company, (2) examine the EO dimensions, and (3) explore the alignment of EO dimensions to understand their contribution to addressing AM challenges.

Agile methods (AM) challenges

In this section, the challenges of AM are presented within the selected dimensions for this study: people, processes, and management and organization.

People

The challenges of AM related to the "people" dimension (according to the Conceptual Framework - Table 1 and theoretical model - Figure 1) were pointed out by the interviewees working in agile teams of both project types (client-based and consultancy-based) and by the business owners. The HR analysts did not mention any challenges in this dimension, suggesting that leaders closer to project execution have a better understanding of the people-related challenges than these analysts.

"Competencies and skills" were identified as challenges by the PO and SM based at the client's site and one of the business owners, who believe that people, in general, lack maturity in terms of AM requirements.

The aspect of "collaboration" was mentioned as a challenge only by the SM based at the consultancy. According to this interviewee, despite being one of the principles of AM, the team members at the company still lack the appropriate profiles and do not work collaboratively with each other.

Finally, "communication" was considered a challenge by the developer based at the consultancy, but only when he was working at the client's site. The challenge ceased to exist after he relocated. Figure 2 presents some excerpts from the interviews that highlight the challenges related to people.

Figure 2

Analysis of the challenges dimension of AM: People


Figure 2
Analysis of the challenges dimension of AM: People
Note: Elaborated by the authors.

Note: Elaborated by the authors.

The items related to "openness to change" and "teamwork" were presented as positive aspects in the company. On the other hand, the items related to "teamwork," "customer relationship," "transparency," and "business knowledge" were not identified as major challenges by any of the interviewees.

In the comments, solutions were also suggested, such as behavioral training programs aimed at bridging the maturity gap for the proper adoption of AM. A starting point for implementing such training in the organization could be the study by Garcia, Martens, and Martens (2021), which lists the personal, interpersonal, and technical knowledge characteristics necessary to overcome the challenges of using and adopting AM by connecting with the dimensions of EO.

Among the employees, the behavior of not wanting to assume the roles required by agility was highlighted. Acquiring new skills and knowledge through engagement in something different from the usual can generate a commitment that was previously avoided. Empirically, when the organization promotes behaviors related to the "innovativeness" dimension, people tend to be more dedicated (Martens & Freitas, 2008). Therefore, a possible solution to this problem may lie within this dimension. People's openness to change aligns with practical elements in modifying product/service lines (Martens & Freitas, 2008).

Processes

The challenges of AM related to the "processes" dimension (Table 1) were identified by interviewees working in agile teams for both types of projects (client-based and consultancy-based) and one of the owners. Once again, none of the HR analysts identified this as an existing AM challenge in the company. This perception may have been influenced by the technical aspects that significantly impact the day-to-day work of project implementers.

"The need for understanding agile values and principles, not just practices" was mentioned by both POs from the teams, indicating a misalignment with both the client and the company itself regarding the requirements for proper AM adoption.

Both POs from the teams, the SM, and the developer working at the client site, mentioned the importance of appropriately selecting projects suitable for AM usage. According to the interviewees, there is a hybrid approach that combines traditional and AM but does not fully align with either.

Regarding the item "For many client companies, what should be executed by contractors is determined by a work statement that defines the main requirements and tasks," one of the owners mentioned it. He believes that the client is interested in working with AM but still does not feel comfortable doing so. Figure 3 presents excerpts from the interviews that highlight the challenges related to processes

Figure 3

Analysis of the challenges dimension of AM: Processes


Figure 3
Analysis of the challenges dimension of AM: Processes
Note: Elaborated by the authors.

Note: Elaborated by the authors.

The items "short, iterative, and test-driven development that emphasizes adaptability," "managing large and scalable projects," "technology (tools and techniques)," "fitting existing technology and tools," and "technical skills" were not mentioned as existing challenges in the company.

A more in-depth analysis of the interviewees' comments reveals that most of the challenges in this "processes" dimension are related to a lack of knowledge and experience in correctly using practices and frameworks. This finding is supported by research that links EO and AM, and possible solutions are addressed by presenting how the convergence between these topics can be encouraged (Garcia, Martens et al., 2021; Garcia et al., 2022). These aspects also influence the appropriate selection of projects and the level of trust from client companies regarding the contractors' ability to deliver requirements.

Among the highlighted positive aspects are: (a) the use of AM through "short, iterative, and test-driven development that emphasizes adaptability", and (b) “the existence of tools that support the technical skills of employees”, aiming to meet market needs not only for the consultancy but also for its clients by adapting AM practices and frameworks. This is a trend in the current business environment, with reduced product life cycles and business models (Wiklund & Shepherd, 2005).

Following this line of reasoning, elements related to the "risk-taking" dimension of the EO can be identified, where a variety of actions are taken to achieve the company's objectives, and the "innovativeness" dimension, which involves engagement and support for new ideas, experiments, and creative processes (Martens & Freitas, 2008).

Management and Organization

The challenges of AM related to "management and organization" (Table 1) were pointed out by interviewees who work in agile teams for both types of projects (client-based and consultancy-based) and by HR analysts. The company's owners do not see this dimension as challenging in terms of using AM in project management. This perception makes sense because this dimension requires direct actions from top management, which further confirms the importance of interviewing employees at all levels of the company.

"The lack of specific recruitment policies for agile" was mentioned by the POs in both types of projects, the SM in the consultancy, and one of the HR analysts. This is due to the perception that professionals working with AM should have a distinct profile focused on behavioral aspects, not just technical skills.

“Recruitment” should therefore take this characteristic into account. The same applies to career development planning. For this purpose, there is a need for performance evaluation that aligns with AM, as suggested by the PO and SM in the consultancy and the HR analyst1.

"Reward systems" are recognized as a challenge by HR analyst1, and "adequate training" indicated by the PO in the consultancy is a way of sharing knowledge, considering the work experience with AM by some employees who can disseminate their knowledge to others through training.

"Organizational culture" was highlighted by HR analyst1 and the developer in the consultancy, given the understanding that there are divergences between the management styles of the company and its clients. In Figure 4, excerpts from the interviews are presented, illustrating these challenges.

Figura 4

Analysis of the AM challenges dimension: Management and Organization


Figura 4
Analysis of the AM challenges dimension: Management and Organization
Note: Elaborated by the authors.

Note: Elaborated by the authors.

The item "executive managers" was associated with risk and opportunity focus by the SM in the consultancy. This is because, although the executive management takes risks, the professionals executing the project do not have the same approach, which poses a challenge to working with AM.

"Adequate training" was indicated by HR analyst1 as a positive factor, as there is specific training for interns according to each individual's profile. Thus, it is believed that it is possible to correctly direct the professional to work in the company sector where they are likely to perform better and have greater learning opportunities.

"Management style" did not directly appear in the responses as a challenge; however, it was mentioned alongside other topics considered challenging, such as the case of "executive managers being focused on risks and opportunities".

Some of the aspects presented here were also mentioned in previous dimensions of challenges. This result can be related to a common characteristic in entrepreneurship in small companies, where the personality of the leader influences the company culture (Miller, 1983, 2011).

The challenges related to "people management" ("specific recruitment policies for agility", "performance evaluation compatible with agility", and "reward system and training") can be addressed by recognizing the personal, interpersonal, and technical knowledge required to perform agility roles ("business/products", "technical and leadership"), as well as "organizational and process practices" useful for project execution. With this, companies can incentivize the right needs and be more successful in adopting AM (Garcia, Martens et al., 2021).

Contributions of the EO dimensions in the adoption of AM

In this section, the contributions of EO are addressed in its dimensions: “autonomy", "innovativeness", "risk-taking", "proactiveness", and "competitive aggressiveness", aiming at the adoption of AM.

Autonomy

"Autonomy" appears in the responses of interviewees working in agile teams of both project types (client-based and consultancy-based), HR analysts, and company owners as a potential solution to the challenges of adopting AM.

In general, the interviewees understand that autonomy can bring many benefits, such as the creation of new products or services and the expansion of knowledge. However, some consider maturity as a necessary condition for granting autonomy.

According to the developer's perception, not all managers encourage autonomy, and when they do, the encouragement does not last.

Another point raised is that the lack of encouragement from some managers can lead to dissatisfaction within the team, resulting in the departure of employees whose profiles were promising for working on projects that use AM.

In Figure 5, excerpts from interviews are highlighted, which provide evidence for the analyses presented here.

Figure 5

Analysis of the EO dimension: Autonomy


Figure 5
Analysis of the EO dimension: Autonomy
Note: Elaborated by the authors.

Note: Elaborated by the authors.

Therefore, it can be stated that all the points presented can be addressed through the dimension of EO, with empirical actions related to coordinating activities by measuring and monitoring the activities of autonomous work teams (Martens & Freitas, 2008).

Innovativeness

"Innovativeness" was highlighted by the interviewees who work in agile teams of both types of projects, as well as by HR analysts and business owners. Different perceptions are observed among team members in projects allocated to the client and those in the consultancy. For those in the consultancy, actions related to innovativeness are being encouraged, considering the selection of suitable profiles for such initiatives, as well as rewards. However, for professionals allocated to the client, the perception is not the same, meaning that there is no encouragement for innovation. The organizational culture of the project's execution location may explain this fact. Despite the encouragement of innovativeness, according to both business owners, caution must be exercised due to the company's size.

This result, obtained from the evidence (Figure 6) in the interviewees' responses, can indeed be explained by the cultural differences between industries (Lomberg et al., 2017). In short, there is a variation in the importance of dimensions and their shared effects depending on the organizational context in which they occur (Lomberg et al., 2017; Miller, 2011).

Figure 6

Analysis of the EO dimension: Innovativeness


Figure 6
Analysis of the EO dimension: Innovativeness
Note: Elaborated by the authors.

Note: Elaborated by the authors.

Risk-taking

The "risk-taking" appears in the responses of interviewees working in agile teams allocated to consultancy, HR analysts, and the company's owners. Although it is considered a positive factor for addressing the AM challenges in the company, this dimension of EO was highlighted primarily by those allocated to consultancy.

In general, mistakes are not punished, but the assumed risks are related to uncertainties within the company rather than the client. A point emphasized by the consultancy-allocated SM is the excessive assumption of risk, a perception that may be motivated by the low level of risk assumption on the part of the contracting client, as mentioned by one of the HR analysts. In Figure 7, excerpts from the interviews that generated the analysis of this dimension are presented.

Figure 7

Analysis of the EO dimension: Risk-taking


Figure 7
Analysis of the EO dimension: Risk-taking
Note: Elaborated by the authors.

Note: Elaborated by the authors.

Practical actions related to this dimension can help in addressing the existing challenges in the company, such as providing formal encouragement to take risks both in business and personal contexts. This can happen if managers adopt a less conservative approach in decision-making and exhibit risk-taking behavior (Martens & Freitas, 2008).

Proactiveness

"Proactiveness" was mentioned by interviewees working in agile teams of both project types and by the company's owners. Although it was considered highly important for addressing AM challenges, it is not among the most encouraged by managers or found in the profiles of professionals allocated to projects at the client or within the consultancy, according to the interviewees. Additionally, none of the HR analysts mentioned it in their responses.

The evidence that generated this analysis is found in the excerpts from the interviews reproduced in Figure 8.

Figure 8

Analysis of the EO dimension: Proactiveness


Figure 8
Analysis of the EO dimension: Proactiveness
Note: Elaborated by the authors.

Note: Elaborated by the authors.

This result is in line with one of the characteristics of empirical actions in the "proactiveness" dimension of EO: the encouragement of continuous market monitoring (Martens & Freitas, 2008), considering that continuous learning can occur in various ways (formal or informal) (Garcia, Martens & Martens, 2021).

Competitive Aggressiveness

"Competitive aggressiveness" appeared in the responses of HR analysts and company owners. The interviewees directly involved in project execution did not consider this dimension relevant to addressing AM challenges - a perception that can be explained by the fact that this EO dimension is more related to top management.

Among the company owners, there is a divergence of perception due to each person's style, conservatism, and the size of the company. The excerpts from the interviews that allowed this analysis are presented in Figure 9.

Figure 9

Analysis of the EO dimension: Competitive aggressiveness


Figure 9
Analysis of the EO dimension: Competitive aggressiveness
Note: Elaborated by the authors.

Note: Elaborated by the authors.

This result aligns with a characteristic of the "competitive aggressiveness" dimension of EO: managerial posture generally influences the level of competitiveness (Martens & Freitas, 2008).

List of EO dimensions for solving AM challenges

In this section, the alignment between EO and AM is established by presenting the dimensions of EO (autonomy, innovativeness, risk-taking, proactiveness, and competitive aggressiveness) that, according to the interviewees' perception, can contribute to addressing AM challenges, based on the previously presented concepts (Table 1).

The EO dimensions of "autonomy" and "proactiveness" were identified by the interviewees as helpful in addressing the challenge categorized as "people" in the adoption of MA. This perception is related to the need for maturity and competence in completing the work, the pursuit of knowledge, communication between teams and business areas, and a sense of ownership. This corroborates the assumptions of Conboy et al. (2011), Coram and Bohner (2005), Gregory et al. (2016), and Nerur et al. (2005).

Regarding the challenge dimension of "processes," the interviewees believe that the solution may lie in "competitive aggressiveness" an EO dimension. This perception is in line with the findings of Coram and Bohner (2005), Dikert et al. (2016), Gregory et al. (2016), and Nerur et al. (2005), emphasizing the correct use of AM processes, as frequent increments can create and deliver software products that better meet the actual needs of customers in a timely manner.

Regarding the "management and organization" challenge, the interviewees mentioned the characteristics presented in the EO dimensions of "risk-taking" and "innovativeness" as a solution. This perception may be related to the need for an innovative and entrepreneurial organizational culture, manifested through behaviors and actions such as seeking opportunities, entrepreneurial leadership, creating collaborative cross-functional teams, and informal communication channels. This finding aligns with the research of Coram and Bohner (2005), Dikert et al. (2016), Gregory et al. (2016), and Nerur et al. (2005), advancing the understanding that adopting AM requires a shift from command and control management to leadership and collaboration.

Based on the above, it can be stated that stimulating the dimensions of EO can have a positive impact on addressing the various challenges identified in the literature and encountered during the adoption of AM.

Furthermore, it is important to emphasize the need to analyze how these challenges occur in startups, specifically which topics within each dimension need to be addressed and how the characteristics of the EO dimensions can be encouraged through joint actions between top management, HR, and employees.

Figure 10 presents the response to the study proposition, i.e., the EO dimensions that can indeed assist in addressing the challenges of AM adoption. This conclusion was reached by linking the EO dimensions (Figure 1) with the research field's responses (Figures 2 to 9), aiming to encourage entrepreneurship in IT startups, considering their positive contribution to the adoption of AM by these companies.

Figura 10

Modelo conceitual do estudo


Figura 10
Modelo conceitual do estudo
Note: Elaborated by the authors.

Note: Elaborated by the authors.

FINAL CONSIDERATIONS

This study achieved the objective of analyzing how the dimensions of Entrepreneurial Orientation can help address the challenges arising from the adoption of Agile Methods.

It was observed that there are different perceptions among "agile teams" regarding the challenges of AM adoption, depending on the context of allocation (client or consultancy).

The influence of "organizational culture" on the adoption of AM is highlighted by professionals working with clients. This was evident in all dimensions of AM challenges and EO, confirming the importance of this characteristic for both constructs, as this culture can motivate employee behavior and actions.

According to the interview responses, the dimensions of EO are recognized as important in addressing the challenges of AM, although they are not equally incentivized when the team is allocated with the client.

Furthermore, even with this agreement, each employee's responses may vary depending on what is allowed and encouraged by the EO. Therefore, for HR analysts, the major challenges related to the "management and organization" dimension, particularly in terms of hiring suitable profiles. On the other hand, for business owners, the client's expectations and the types of requested contracts are the most challenging requirements.

Considering these findings, this study has contributed to the advancement of literature on AM, EO, and the relationship between these topics in project management. The contribution for organizations lies in understanding the challenges inherent in the adoption and use of AM and reflecting on how encouraging specific actions can help solve problems associated with the AM, utilizing entrepreneurship concepts and, more specifically, EO.

This study had the limitation of not being able to extrapolate the results, as it adopted a single case study as the method. Following the viewpoint of Mariotto et al. (2014), we believe that researchers or practitioners can transfer the results to a new situation based on their knowledge and life experience and apply them to a new context. Therefore, generalization is left to the reader/researcher; if they choose to follow the same steps as this research, they may arrive at similar insights (Mariotto et al., 2014).

For future research, it is recommended to conduct more in-depth studies on the relationship between EO and the challenges of AM or to intervene in the study context by presenting the results and the resulting benefits.

Conflit of interest statement

The authors declare that there is no conflict of interest.

Authors’ statement of individual contributions




Note: Acc. CRediT (Contributor Roles Taxonomy): https://credit.niso.org/

Supplementary material
Additional information

JEL classification:: M13, M14, M15, L26

Article ID:: 2404

Editor-in-Chief1 or Adjunct2:: 1 Dr. Edmundo Inácio Júnior Univ. Estadual de Campinas, UNICAMP

Associate Editor:: Dr. Pedro Lucas de Resende Melo Universidade Paulista, UNIP Pontifícia Univ. Catól. de São Paulo, PUCSP

Executive1 or Assistant2 Editor:: 1 M. Eng. Patrícia Trindade de Araújo

How to Cite:: Garcia, V. B., Martens, C. D. P., Penha, R., & Martens, M. L. (2023). Entrepreneurial Orientation as support in solving the challenges of Agile Methods adoption: A case study in a Brazilian startup. REGEPE Entrepreneurship and Small Business Journal, 12(2), e2404. https://doi.org/10.14211/regepe.esbj.e2404

Related item (is Translation Of):: https://doi.org/10.14211/regepe.esbj.e2286

Acknowledgments

We appreciate the support of the National Council for Scientific and Technological Development (CNPq) and the Research Support Fund (FAP-UNINOVE) in the development of this study.

REFERENCES
Bardin, L. (2004). Análise de conteúdo. Edições 70.
Beck, K et al. (2001). Manifesto for Agile Software Development. Retrieved from https://www.camcode.com.au/download/aac_manifesto-for-agile-software-development
Bosch, J., Holmström Olsson, H., Björk, J., Ljungblad, J. (2013). The Early Stage Software Startup Development Model: A Framework for Operationalizing Lean Principles in Software Startups. In: Fitzgerald, B., Conboy, K., Power, K., Valerdi, R., Morgan, L., Stol, KJ. (eds) Lean Enterprise Software and Systems. LESS 2013. Lecture Notes in Business Information Processing, vol 167. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-44930-7_1
Boni, V., & Quaresma, S. J. (2005). Aprendendo a entrevistar: como fazer entrevistas em Ciências Sociais. Em Tese, 2(1), 68–80. http://doi.org/10.5007/18027
Carmona, V. C., Martens, C. D. P., & de Freitas, H. M. R. (2020). Os antecedentes da orientação empreendedora em negócios sociais. Revista de Empreendedorismo e Gestão de Pequenas Empresas, 9(2), 71–96. http://doi.org/10.14211/regepe.v9i2.1411
Conboy, K. (2002). A Framework for the Study of Modelling Techniques in Agile Methods. University of Limerick, Limerick, Ireland. Retrieved from https://citeseerx.ist.psu.edu/
Conboy, K., Coyle, S., Wang, X., & Pikkarainen, M. (2011). People over process: key people challenges in agile development. IEEE Software, 28(4), 48–57. https://doi.org/10.1109/MS.2010.132
Conboy, K., & Fitzgerald, B. (2004, November). Toward a conceptual framework of agile methods: a study of agility in different disciplines. In Proceedings of the 2004 ACM Workshop on Interdisciplinary Software Engineering Research (pp. 37–44). http://doi.org/10.1145/1029997.1030005
Coram, M., & Bohner, S. (2005, April). The impact of agile methods on software project management [Paper Presentation, pp. 363–370]. International Conference and Workshops on the Engineering of Computer-Based Systems (ECBS'05) 12th, Greenbelt, MD, USA. http://doi.org/ 10.1109/ECBS.2005.68
Covin, J. G., & Lumpkin, G. T. (2011). Entrepreneurial orientation theory and research: Reflections on a needed construct. Entrepreneurship theory and practice, 35(5), 855–872. http://doi.org/10.1111/j.1540-6520.2011.00482.x
Covin, J. G., Rigtering, J. C., Hughes, M., Kraus, S., Cheng, C. F., & Bouncken, R. B. (2020). Individual and team entrepreneurial orientation: Scale development and configurations for success. Journal of Business Research, 112, 1–12. https://doi.org/10.1016/j.jbusres.2020.02.023
Covin, J. G., & Wales, W. J. (2019). Crafting high-impact entrepreneurial orientation research: Some suggested guidelines. Entrepreneurship theory and practice, 43(1), 3–18. https://doi.org/10.1177/1042258718773181
Dikert, K., Paasivaara, M., & Lassenius, C. (2016). Challenges and success factors for large-scale agile transformations: A systematic literature review. Journal of Systems and Software, 119, 87–108. https://doi.org/10.1016/j.jss.2016.06.013
Freitas, H., Martens, C. D. P., Boissin, J.-P., & Behr, A. (2012). Elementos para guiar ações visando à orientação empreendedora em organizações de software. Revista de Administração, 47(2), 163–179. https://doi.org/10.5700/rausp1032
Frare, A. B., Horz, V., Barbosa, M. A. G., & da Cruz, A. P. C. (2021). Interface entre orientação empreendedora, planejamento estratégico e orçamento: Configurações para o alto desempenho. Iberoamerican Journal of Entrepreneurship and Small Business, 10(2) e1934. https://doi.org/10.14211/regepe.e1934
Gandomani, T. J., & Nafchi, M. Z. (2016). Agile transition and adoption human-related challenges and issues: A Grounded Theory approach. Computers in Human Behavior, 62, 257–266. https://doi.org/10.1016/j.chb.2016.04.009
Garcia, V. M. B., Martens, C. D. P., Carvalho, R. B., & Martens, M. L. (2021). Contributions of entrepreneurial orientation in the use of agile methods in Project management. Innovation & Management Review, 18(1), 17–33. https://doi.org/10.1108/INMR-01-2019-0002
Garcia, V. M. B., Martens, C. D. P., Carvalho, R. B., & Martens, M. L. (2022). Adoção de Métodos Ágeis com enfoque da Orientação Empreendedora em Gerenciamento de Projetos: Proposição de um Artefato via Design Science Research [Apresentação de Trabalho]. Associação Nacional de Pós-Graduação e Pesquisa em Administração (ANPAD), Encontro da ANPAD (EnANPAD), 46º, São Paulo, SP.
Garcia, V. M. B., Martens, C. D. P., & Martens, M. L. (2021). Análise da Convergência entre Orientação Empreendedora e Métodos Ágeis: Estudo sob a Perspectiva dos Princípios Ágeis. Associação Nacional de Pós-Graduação e Pesquisa em Administração (ANPAD), Encontro da ANPAD (EnANPAD), 45º, São Paulo, SP.
Garçon, M. M., & Nassif, V. M. J. (2021). Orientação empreendedora individual sob medida: Desenvolvimento de escala voltada ao empreendedorismo social. Revista de Empreendedorismo e Gestão de Pequenas Empresas, 10(1), 1–8. https://doi.org/10.14211/regepe.v10i1.2008
Ghezzi, A., & Cavallo, A. (2020). Agile business model innovation in digital entrepreneurship: Lean startup approaches. Journal of business research, 110, 519–537. http://doi.org/10.1016/j.jbusres.2018.06.013
Gregory, P., Barroca, L., Sharp, H., Deshpande, A., & Taylor, K. (2016). The challenges that challenge: Engaging with agile practitioners’ concerns. Information and Software Technology, 77, 92–104. https://doi.org/10.1016/j.infsof.2016.04.006
Highsmith, J., & Cockburn, A. (2001). Agile software development: The business of innovation. Computer, 34(9), 120–127
Kalyanasundaram, G. (2018). Why Do Startups Fail? A Case Study Based Empirical Analysis in Bangalore. Asian Journal of Innovation & Policy, 7(1), 79–102. http://dx.doi.org/10.7545/ajip.2018.7.1.079
Kaufmann, C., Kock, A., & Gemünden, H. G. (2020). Emerging strategy recognition in agile portfolios. International Journal of Project Management, 38(7), 429–440. https://doi.org/10.1016/j.ijproman.2020.01.002
Ladas, C. (2009). Scrumban-essays on kanban systems for lean software development. Seattle, WA, USA: Modus Cooperandi Press.
Li, Q., Wang, C., Wu, J., Li, J., & Wang, Z. Y. (2011). Towards the business–information technology alignment in cloud computing environment: an approach based on collaboration points and agents. International Journal of Computer Integrated Manufacturing, 24(11), 1038-1057. https://doi.org/10.1080/0951192X.2011.592994
Linton, G. (2019). Innovativeness, risk-taking, and proactiveness in startups: a case study and conceptual development. Journal of Global Entrepreneurship Research, 9(1), 1–21. https://doi.org/10.1186/s40497-019-0147-5
Lomberg, C., Urbig, D., Stöckmann, C., Marino, L. D., & Dickson, P. H. (2017). Entrepreneurial orientation: The dimensions’ shared effects in explaining firm performance. Entrepreneurship theory and practice, 41(6), 973–998 https://doi.org/10.1111/etap.1223
Lumpkin, G. T., & Dess, G. G. (1996). Clarifying the entrepreneurial orientation construct and linking it to performance. Academy of management Review, 21(1), 135–172. https://doi.org/10.2307/258632
Lumpkin, G.T. and Dess, G.G. (2001) Linking Two Dimensions of Entrepreneurial Orientation to Firm Performance: The Moderating Role of Environment and Industry Life Cycle. Journal of Business Venturing, 16, 429-451. http://dx.doi.org/10.1016/S0883-9026(00)00048-3
Mariotto, F. L., Zanni, P. P., & Moraes, G. H. S. (2014). What is the use of a single-case study in management research? Revista de Administração de Empresas, 54(4), 358–369. https://doi.org/10.1590/S0034-759020140402
Martens, C. D. P., & Freitas, H. (2008). Orientação empreendedora nas organizações e a busca de sua facilitação. Gestão.Org, 6(1), 90–108.
Martens, C. D. P., Lacerda, F. M., Belfort, A. C., & Freitas, H. M. R. D. (2016). Research on entrepreneurial orientation: current status and future agenda. International Journal of Entrepreneurial Behavior & Research, 22(4), 556–583. http://doi.org/10.1108/IJEBR-08-2015-0183
Martens, C. D. P., Machado, F. J., Martens, M. L., & de Freitas, H. M. R. (2018). Linking entrepreneurial orientation to project success. International Journal of Project Management, 36(2), 255–266. https://doi.org/10.1016/j.ijproman.2017.10.005
Maruping, L. M., Venkatesh, V., & Agarwal, R. (2009). A control theory perspective on agile methodology use and changing user requirements. Information Systems Research, 20(3), 377–399. http://doi.org/10.1287/isre.1090.0238
Merriam, S. B. (1988). Case study research in education: A qualitative approach. Jossey-Bass.
Mkpojiogu, E., Hashim, N. L., Al-Sakkaf, A., & Hussain, A. (2019). Software startups: Motivations for agile adoption. International Journal of Innovative Technology and Exploring Engineering, 8(8S), 454–459.
Miller, D. (2011). Miller (1983) revisited: A reflection on EO research and some suggestions for the future. Entrepreneurship theory and practice, 35(5), 873–894. https://doi.org/10.1111/j.1540-6520.2011.00457.x
Miller, D. (1983). The correlates of entrepreneurship in three types of firms. Management Science, 29(7), 770–792. https://doi.org/10.1287/mnsc.29.7.770
Mustafa, G., & Sönmezisik, B. (2020). The Role of Proactive and Adaptive Behaviors in Overcoming Individuals-related Challenges of Agile Project Management Implementation Process: A Case Study Within Two Large-sized Banks [Master’s Thesis, Halmstad University]. Digitala Vetenskapliga Arkivet (DiVA). Retrieved from http://urn.kb.se/resolve?urn=urn:nbn:se:hh:diva-42822
Nerur, S., Mahapatra, R., & Mangalaraj, G. (2005). Challenges of migrating to agile methodologies. Communications of the ACM, 48(5), 72–78. https://doi.org/10.1145/1060710.1060712
Noronha, M. S. E. S. de, Bento, L. F., Rufino, J. P. F., & Rocha, T. V. (2022). Research Overview about Competencies of Startups. International Journal of Professional Business Review, 7(2), e0293. Retrieved from https://ssrn.com/abstract=4025486
Oblog, T., Oblog, K., & Pratt, M. G. (2010). Dominant logic and entrepreneurial firms’ performance in a transition economy. Entrepreneurship Theory and Practice, 34(1), 151–170. https://doi.org/10.1111%2Fj.1540-6520.2009.00367.x
Paternoster, N., Giardino, C., Unterkalmsteiner, M., Gorschek, T., & Abrahamsson, P. (2014). Software development in startup companies: A systematic mapping study. Information and Software Technology, 56(10), 1200–1218. https://doi.org/10.1016/j.infsof.2014.04.014
Ragin-Skorecka, K. (2016). Agile enterprise: A human factors perspective. Human Factors and Ergonomics in Manufacturing & Service Industries, 26(1), 5–15. https://doi.org/10.1002/hfm.20610
Rank, J., Unger, B. N., & Gemünden, H. G. (2015). Preparedness for the future in project portfolio management: the roles of proactiveness, riskiness and willingness to cannibalize. International Journal of Project Management, 33(8), 1730–1743. https://doi.org/10.1016/j.ijproman.2015.08.002
Rauch, A., Wiklund, J., Lumpkin, G. T., & Frese, M. (2009). Entrepreneurial orientation and business performance: An assessment of past research and suggestions for the future. Entrepreneurship theory and practice, 33(3), 761–787. http://doi.org/10.1111/j.1540-6520.2009.00308.x
Ries, E. (2008). Principles of Lean Startups, presentation for Maples Investments. Online available at: http://www.startuplessonslearned.com/2008/11/principles-of-lean-startups.html.
Ries, E. (2011). The Lean Startup: How Today’s Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses. New York: Crown Business.
Salin, N. (2017). Supporting proactivity in agile project teams through self-organizing and shared leadership. LUT School of Business and Management. Retrieved from https://urn.fi/URN:NBN:fi-fe201703204855
Schwaber, K., & Sutherland, J. (2011). The scrum guide. Scrum Alliance, 21(19), 1-38.
Serrador, P., & Pinto, J. K. (2015). Does Agile work? — A quantitative analysis of agile project success. International journal of project management, 33(5), 1040–1051. https://doi.org/10.1016/j.ijproman.2015.01.006
Sheffield, J., & Lemétayer, J. (2013). Factors associated with the software development agility of successful projects. International Journal of Project Management, 31(3), 459–472. https://doi.org/10.1016/j.ijproman.2012.09.011
Siakas, K. V., Georgiadou, E., & Berki, E. (2005, April). Agile methodologies and software process improvement [Paper Presentation]. IADIS International Virtual Multi Conference on Computer Science and Information Systems. Portugal. Middlesex University Research Repository.
Silva, D. S., Ghezzi, A., de Aguiar, R. B., Cortimiglia, M. N., & ten Caten, C. S. (2020). Lean Startup, Agile Methodologies and Customer Development for business model innovation: A systematic review and research agenda. International Journal of Entrepreneurial Behavior & Research, 26(4), 595–628. https://doi.org/10.1108/IJEBR-07-2019-0425
Söderlund, J., & Geraldi, J. (2012). Classics in project management: revisiting the past, creating the future. International Journal of Managing Projects in Business, 5(4), 559–577. https://doi.org/10.1108/17538371211280245
Souza, R., Rocha, L., Silva, F., & Machado, I. (2019, September). Investigating agile practices in software startups. In Proceedings of the XXXIII Brazilian Symposium on Software Engineering (pp. 317-321).
Strode, D. E., Huff, S. L., & Tretiakov, A. (2009, January). The impact of organizational culture on agile method use. Proceedings of 42nd Hawaii International Conference on System Sciences (pp. 1–9). IEEE Xplore. Waikoloa, HI, USA. http://doi.org/ https://doi.org/10.1109/HICSS.2009.436
Sugimori, Y., Kusunoki, K., Cho, F., & Uchikawa, S. (2007). Toyota production system and kanban system materialization of just-in-time and respect-for-human system. The international journal of production research, 15(6), 553–564. https://doi.org/10.1080/00207547708943149
Tavares, B. G., da Silva, C. E. S., & de Souza, A. D. (2019). Practices to improve risk management in agile projects. International Journal of Software Engineering and Knowledge Engineering, 29(3), 381–399. http://doi.org/10.1142/S0218194019500165
Tripp, J. F., Riemenschneider, C., & Thatcher, J. B. (2016). Job satisfaction in agile development teams: Agile development as work redesign. Journal of the Association for Information Systems, 17(4), 1. http://doi.org/10.17705/1jais.00426
Version One. (2020). 14th Annual State of Agile Survey. Retrieved from https://www.qagile.pl/wp-content/uploads/2020/06/14th-annual-state-of-agile-report.pdf.
Wiklund, J., & Shepherd, D. (2005). Entrepreneurial orientation and small business performance: a configurational approach. Journal of business venturing, 20(1), 71–91. https://doi.org/10.1016/j.jbusvent.2004.01.001
Yazan, B. (2015). Three approaches to case study methods in education: Yin, Merriam, and Stake. The Qualitative Report, 20(2), 134–152. Retrieved from http://nsuworks.nova.edu/tqr/vol20/iss2/12
Yin, R. K. (2015). Estudo de Caso: Planejamento e Métodos. Bookman Editora.
Notes
Author notes
AUTHOR BIOGRAPHY Vanessa Mesquita Blas Garcia is head of projects and agility and professor of undergraduate and graduate programs. She has a doctorate in business administration and a professional master's degree in project management from the Universidade Nove de Julho-SP, a postgraduate degree in knowledge management, BI and CRM from FASP and a degree in data processing from FATEC-BS.
AUTHOR BIOGRAPHY Cristina Dai Prá Martens is coordinator of the Postgraduate Program in Project Management (PPGP) and professor of the Postgraduate Program in Business Administration (PPGA) at the Universidade Nove de Julho - UNINOVE. He has a Post-Doctorate in Entrepreneurship and Strategy from the Université Pierre Mendès France (Grenoble - France), a Doctorate and a Master's Degree in Business Administration from PPGA/EA/UFRGS - Federal University of Rio Grande do Sul, and a Bachelor's Degree in Business Administration. Companies by the University of Passo Fundo (UPF). Her areas of interest include Entrepreneurship, Business Guidance, Information Management and Project Management. She is a member of the National Association of Studies on Entrepreneurship and Small Business Management (ANEGEPE). She is a Productivity Researcher 2 at CNPq.
AUTHOR BIOGRAPHY Renato Penha is a professor at the Graduate Program in Project Management at Universidade Nove de Julho (UNINOVE). He holds a doctorate in Business Administration from Universidade Nove de Julho, a professional master's degree in Project Management from Universidade Nove de Julho and a Bachelor's degree from Universidade Bandeirante in São Paulo. His areas of interest include Predictive and Iterative Project Management.
AUTHOR BIOGRAPHY Mauro Luiz Martens is a Full Professor in the Postgraduate Program (Master and Doctorate) in Business Administration at Paulista University (UNIP) in Brazil. He holds a PhD in Production Engineering from the renowned Polytechnic School of the University of São Paulo (USP) and a MSc in Production Engineering from the University of Santa Catarina (UFSC), both in Brazil. With his extensive expertise, he has focused his research on various areas including Project Management, Industry 4.0, Digital Transformation, Sustainability, Project Success, and Organizational Success. Additionally, he is recognized as a PQ CNPq 2 Researcher, actively exploring the intersections between Industry 4.0 and its implications for project management, sustainability, and project success.

vmbg17@gmail.com


Table 1
Conceptual framework: EO dimensions and AM challenges
Note: Elaborated by the authors.

Figure 1
Modelo conceitual do estudo
Note: Elaborated by the authors.

Table 2
Characterization of respondents
Note: SM = Scrum master. PO = product owner. Note: Elaborated by the authors.

Figure 2
Analysis of the challenges dimension of AM: People
Note: Elaborated by the authors.

Figure 3
Analysis of the challenges dimension of AM: Processes
Note: Elaborated by the authors.

Figura 4
Analysis of the AM challenges dimension: Management and Organization
Note: Elaborated by the authors.

Figure 5
Analysis of the EO dimension: Autonomy
Note: Elaborated by the authors.

Figure 6
Analysis of the EO dimension: Innovativeness
Note: Elaborated by the authors.

Figure 7
Analysis of the EO dimension: Risk-taking
Note: Elaborated by the authors.

Figure 8
Analysis of the EO dimension: Proactiveness
Note: Elaborated by the authors.

Figure 9
Analysis of the EO dimension: Competitive aggressiveness
Note: Elaborated by the authors.

Figura 10
Modelo conceitual do estudo
Note: Elaborated by the authors.



Note: Acc. CRediT (Contributor Roles Taxonomy): https://credit.niso.org/
Buscar:
Contexto
Descargar
Todas
Imágenes
Scientific article viewer generated from XML JATS4R by Redalyc