A conceptual framework for effective management of conflict risk within Agile software development environments

Copyright: © 2021. The Authors. Licensee: AOSIS. This work is licensed under the Creative Commons Attribution License. Introduction The world today is a hugely inter-connected competitive space that has created a critical demand for organisations to adapt and rise above the need to maintain their technological effectiveness and adequacy (Tokody 2018). The main drivers of the world’s correct state have been mainly globalisation and digital transformation. These two elements have tremendously fuelled the constant demand and ever-changing demands of the market (World Economic Forum 2016:6). This has, in turn, requested organisations to be innovative and come up with techniques and methods they can employ to handle and manage this situation effectively and continuously (Kuteynikov et al. 2019:3964). The process and employment of technology across majority of industries and business sectors to curb this ongoing demand have been the cornerstone and answer for most organisations. This is known as ‘technology competitiveness’ (Berawi 2018:1). Technology competitiveness is the organisation’s ability to provide products and services more effectively and efficiently than its current, relevant competitors using technology and digital means (Rodrigues & José 2015:56). Mizanbekova, Bogomolova and Shatohina (2020) suggested that effective technology competitiveness facilitates companies to obtain higher market share, superior user experience and overall business excellence. The attaining of technology competitiveness in organisations provides the foundation for effective, successful response to the changing market demands (Mbelli & Hira Background: Whenever teams obtain together to work towards a common goal, the lingering of an inherent conflict risk is always a possibility. This applies to software development teams as well. Researchers even argue this inherent conflict existence as necessary. Agile development environment is no exception. The main purpose for adopting Agile is to improve the technology adequacy to facilitate organisation competitiveness. Agile manages the achievement of this through its advocacy for change, adaptability and constant satisfaction of market demands. This is because Agile enables organisations to create software of quality standard that allows for quicker response to the continuously changing market needs of todays’ world.


Introduction
The world today is a hugely inter-connected competitive space that has created a critical demand for organisations to adapt and rise above the need to maintain their technological effectiveness and adequacy (Tokody 2018). The main drivers of the world's correct state have been mainly globalisation and digital transformation. These two elements have tremendously fuelled the constant demand and ever-changing demands of the market (World Economic Forum 2016:6). This has, in turn, requested organisations to be innovative and come up with techniques and methods they can employ to handle and manage this situation effectively and continuously (Kuteynikov et al. 2019:3964). The process and employment of technology across majority of industries and business sectors to curb this ongoing demand have been the cornerstone and answer for most organisations. This is known as 'technology competitiveness' (Berawi 2018:1). Technology competitiveness is the organisation's ability to provide products and services more effectively and efficiently than its current, relevant competitors using technology and digital means (Rodrigues & José 2015:56). Mizanbekova, Bogomolova and Shatohina (2020) suggested that effective technology competitiveness facilitates companies to obtain higher market share, superior user experience and overall business excellence. The attaining of technology competitiveness in organisations provides the foundation for effective, successful response to the changing market demands (Mbelli & Hira Background: Whenever teams obtain together to work towards a common goal, the lingering of an inherent conflict risk is always a possibility. This applies to software development teams as well. Researchers even argue this inherent conflict existence as necessary. Agile development environment is no exception. The main purpose for adopting Agile is to improve the technology adequacy to facilitate organisation competitiveness. Agile manages the achievement of this through its advocacy for change, adaptability and constant satisfaction of market demands. This is because Agile enables organisations to create software of quality standard that allows for quicker response to the continuously changing market needs of todays' world. http://www.sajim.co.za Open Access 2016). One technique adopted in response to this need was the adoption of Agile.
Agile facilitates and improves the technology adequacy and effectiveness within organisations through its advocacy for change, adaptability and constant satisfaction of market demands (Rix et al. 2016). Through Agile, organisations can create software of quality standard, which allows for quicker response to the continuously changing market needs of todays' world (Choudhary & Rakesh 2016). A proficient Agile environment within organisations facilitates successful, constructive interactions and collaborations among team members (Kiitam, McLay & Pilli 2016). Constructive interactions and effective customer collaborations lead to successful continuous iterations, which then lead to high chances of successful project implementation and deployment (Gren & Lenberg 2018). The constant, successful implementations of various Agile projects enable organisations to satisfy and fulfil the high competition-based market demands and requirements of this fast-paced market demands (Mbelli & Hira 2016). This, in turn, improves the organisations' technological adequacy that helps organisations attain the strategic reason for adopting the Agile methodology.
However, according to existing literature, there is always one lingering negative element that is continuous to affect attainment of proficient, effective Agile environment, which, in turn, hinders organisations in achieving the benefits the study has outlined. Conflict is identified by the current literature a risk in software projects (Saxena, Venkatagiri & Bandi 2016). According to Chiyangwa and Mnkandla (2018), project success depends heavily on a productive working atmosphere among project stakeholders, in particular projects implemented using the Agile methodology. Conflict-risk existence among project team members poses a risk to such effective working environment (Kiitam et al. 2016). The current literature further states that one solution to maintaining a productive working relation among project team members is effective management of the inherent conflict risk (Gren & Lenberg 2018). Nesterkin and Porterfield (2016) suggested that constructive conflict-risk management features as a risk-reducing element within the global information technology (IT) development environments.
According to Adkins (2010), research paper that evaluates coaching techniques to constructive conflict management in Agile projects, conflict as a risk among Agile teams, is unavoidable, especially in comparison to other project environments. This is because Agile promotes for a more interdependent stakeholder environment to other project management methodologies, like the traditional waterfall (Gren 2017). The main aim of Agile approach concerning this interdependency among team members is the attainment of a broader viewpoint that is likely to come up with great, well-thought results (Mergel 2016). Effective conflict risk and Agile environments are two facets that need to be orderly and effectively coordinated to achieve organisation technology sufficiency (Saxena et al. 2016). Sudhakar (2015) stated that effective conflict-risk management delivers an improved and increased team maturity and effectiveness within Agile environments. Agile assists companies to fulfil the demand for the increasing ever-changing customer needs and requirements. This is achieved through continuous development of highquality standard software that supports organisations to constantly meet the customer needs of the ever-changing modern world of today (Balbes 2014).
The attainment of organisation's technology competitiveness is a direct result of the organisation's capability to stay on top of the competition through delivery of goods and services using technology (Morris, Ma & Wu 2015). On the other hand, Agile facilitates organisation's capability to meet the continuous, flexible customer demands through the development of strategy-based systems or technology (Rigby, Sutherland & Takeuchi 2016). This study investigates the influence of effectively managed conflict risk within Agile teams towards the organisations' technology competitiveness. To achieve this goal, the study will be guided by the following objectives: • determine if there is any existing conflict risk within Agile development teams • outline the nature of such risk and how it affects Agile environments, and the successful delivery of Agile projects • develop a framework on how effectively managed conflict risk within Agile environments can facilitate the achievement of technology competitiveness within organisations.

Problem statement
Globalisation has forced organisations to think about business far beyond physical boarders (Bianchi & Labory 2018). This created a critical urge for organisations to come up with ways to rise above and beyond this new way of business and realise profits. Information technology has been the main enabler of globalisation, and therefore, organisations have had to ensure efficiency and effectiveness of their IT (Ottonicar, Valentim & Mosconi 2018). Successful delivery of IT systems over the last two decades has fostered the world to become the giant online space it is today. Effective management of IT development projects has been the cornerstone for such successful delivery (Ching & Mutuc 2019). To improve on the success rate of IT development projects, companies adopted the Agile. Not only has this approach enabled organisations the flexibility to satisfy the constant changing market conditions and customer needs but has also positioned the world in a technology fuelled competition and readiness that facilitated digital transformation across the entire world's sectors and industries (Yanık & Işıklı 2019). Conflict risk, which is inherent in project teams, is identified as a hindrance to the successful delivery of IT projects, Agile software development projects included (Saxena et al. 2016).
Previous research has been conducted on conflict within Agile and the impact of effective conflict management within Agile environments. However, no research has directly linked the outcomes of effectively managed conflict risk within Agile environments towards organisations ability to attain technology competitiveness. Henceforth, this study aims to close this identified research gap.

Conflict-risk management
Globalisation has forced organisations to maintain an effective and efficient technology (Saniuk & Saniuk 2018).
Agile as a methodology largely adopted in software development environments facilities and manages this challenge of an unpredictable, ever-changing market demands through dependency on 'people and their creativity instead of on the processes' (Rix et al. 2016); however, wherever people are involved in groups, the risk of conflict risk is imminent. To achieve the benefits associated with the adoption of Agile, an effective team, which leads to effective projects implementation, is the foundation (Emejom et al. 2019). According to Chaudhry and Asif (2015), effective conflict-risk management is an organisation's strategic advantage and an enabler of efficient Agile development environment. Nevertheless, the 'trick' to this efficiency is effective mitigation of such conflict risk (Gren 2017). Conflict risk that is effectively mitigated yields positive team interactions and engagements (Gren 2017). Studies by Crawford et al. (2014), Sudhakar (2015) and Nesterkin and Porterfield (2016) agreed on the following benefits of effectively managed conflict risk within project teams: • improved understanding that uplifts creativity • it promotes existence of functional, constructive conflict within the team, which usually boosts levels of creativity and productivity over time • fosters solid relationships among team members because they are skilled with sufficient conflict resolution techniques • speedy problem-solving process and reduced tension because of a conflict resolution skilled team.
When there is accomplishment of the above benefits within an Agile environment, there is likelihood of successful, an effective team environment, which positively influences the attainment of successful implementations of various Agile projects within organisations (Sudhakar 2015).
According to Nesterkin and Porterfield (2016), effective conflict-risk management refers to the process of managing conflicts, and it entails the development of constructive strategies to mitigate the dysfunctions caused by conflict that arise in a group of people. Balbes (2014) supported this fact by suggesting that this escalates the constructive and productive outcomes of conflict that improves team effectiveness. Effectively managing conflict risk yields effective team relationships, and effective team relations then lead to effective communication, which is a critical element to any task success (Deshpande 2014). Crawford et al. (2014) indicated that Agile teams require an effective conflict management strategy. This attains a strong mixture of constructive and negative outcomes of conflicts within projects, which then results in productive, solid team relationships (Gren 2017). Software projects success relies heavily on effective team relationships, because this affects the effectiveness of communication among team members (Deshpande 2014). The criticality of ensuring effective conflict-risk management within software development environments, specifically Agile environments, is one element that needs thorough investigation and possible solutions.

Overview of agile
Agile was first introduced as an iterative approach for software development (Beck et al. 2001 (Balashova & Gromova 2017). The idea of Agile or 'agility' has existed in the software sector since the 1990s and its success and wide adoption have been realised across the world (O'Leary, Cota & Otis 2017). The Agile approach has insighted organisations to realise the benefit in valuing outcome over rules, encouraging broader participation over control, focussing on continual change response as well as promoting self-organisation over centralised governance (Khalil & Kotaiah 2018). Agile is currently the vast adopted project management methodology within the IT development sector, with over 58% of companies implementing Agile or a hybrid of Agile and other methodologies, such as waterfall, scrum or six sigma (Asirvatham et al. 2018).
The current literature indicates the following as some of the main goals to implement IT projects in Agile ( • improved productivity • delivery of right, quality software products • meeting the project time-to-market constraint • visibility and transparency among project teams • stakeholder satisfaction • an improved feedback mechanism. Constant achievement of the above Agile software project goals facilitates digital transformations within organisations and provides organisations with the ability to keep up with the constant market demands (Mbelli & Hira 2016). Effective response to the critical urge for digital transformation is the driver behind organisations' survival or failure in today's world. The success or failure mainly depends on the organisation's ability to provide products and services more effectively and efficiently than its current, relevant competitors using technology and digital means. This is what the existing literature refers to as technology competitiveness (Kohnová, Papula & Salajová 2019).

Research methodology
This research study has been undertaken with an objective to investigate the theory of conflict-risk management in Agile teams and the impact it has on the organisations' technological competitiveness. According to Chaudhry and Asif (2015), conflict-risk management is defined as a process of managing the negative aspects that could hinder the success of software projects among project team members. Quantitative research techniques and tools were applied for data collection as well as data analysis. IBM SPSS was specifically used for data analysis. A structured questionnaire with closed-ended questions was used for data collection. In order to obtain in-depth understanding of conflict-risk management in Agile teams, purposive sampling method was deemed suitable. The questionnaire used Likert scales from Strongly Disagree to Strongly Agree. Purposive sampling method ensures that only experts or well-skilled and experience professionals participate in a research study. The unit analyses were professionals within IT sector, who are project team members involved in Agile software development within software developing organisations in South Africa. Because this study is quantitative, a positivism approach was followed (Kothari 2004). A total number of 179 responses were received and analysed. A total number of 13 items were tested for reliability and resulted in a Cronbach's Alpha of 0.738 which is acceptable (Tavakol & Dennick 2011). The reliability statistics results are shown (Table 1). According to Mühl (2014), validity measures the instruments to ensure that they measure what they are expected to measure. Construct validity was used in this study.

Conflict-risk existence within Agile teams
The findings depict several facts around the tested issues of conflict as a risk in Agile teams within South African (SA) companies. Firstly, the findings show affirming results on the existence of conflict risk among Agile teams in SA. The existing literature (Balbes 2014;Crawford et al. 2014;Gren 2017) has tested this theory within Agile environments in other countries. Researchers such as Sudhakar (2015), Nesterkin and Porterfield (2016) and Gren and Lenberg (2018) have investigated conflict and its significant presence within software development teams. The study findings show that about 76/179 participants, which makes over 40% of the participants experienced conflict risk or some sort of disagreement within their respective Agile teams (Table 2). These findings correlate with Gren (2017), which indicated conflict as a risk within Agile teams. This shows tremendous importance on conflict as a risk element and its constructive management in teams to have smooth relations among team members who can lead to an effective working team environment. A need for an effective technique or method to mitigate and manage such risk is vital. The frequency results for conflict existence are shown ( Table 2).

Influence of conflict as a risk in Agile teams
In addition to the questions on conflict-risk existence presented to participants concerning their current Agile teams, more questions on the impact of such risk were presented, which included: (1) to state whether most of the conflicts they experienced led to constructive discussions or dysfunctional, non-constructive disagreements.
(2) Also, participants had to provide the outcomes of such conflictrisk effect on their team relations.
(3) Lastly, participants were questioned on the existence of constructive ways of managing conflict risk within their respective Agile teams and its benefits towards set Agile teams (Table 3), project goals. The study findings on these tested theories as well as respective percentages of the quantitative data collected are shown (Figure 1 and Figure 2).
The study findings depicted two kinds of outcomes conflict existence brought within Agile (Table 3) which are constructive as depicted ( Figure 2) and dysfunctional conflict outcomes as depicted ( Figure 1). The first outcome, constructive conflict,  conveyed a positive effect within teams. This kind of conflict outcome was brought by effectively managed conflict risk, and this yielded a functional team environment. This finding on functional conflict and its tremendous advantages for an Agile environment is in line with the studies of Balbes (2014) that investigated the theory of making conflict management a strategic advantage within Agile teams.
The benefit of attaining the 'right product' because of functional conflict risk has been fully explored in a study by Crawford et al. (2014).
This study finding also determined the outcomes of constructive conflict in Agile teams, which concur with findings in the current literature by researchers Nesterkin and Porterfield (2016) and Thomas (2017). The other impact of conflict in Agile teams, identified by the study, is one that brings a negative impact to the working relations among team members. This occurs when conflict risk has not been effectively mitigated and managed. Various researchers including Chaudhry and Asif (2015) and Kiitam et al. (2016) have suggested that conflict risk within development teams most times brings negative outcomes because it yields to several repercussions like the lack of timely communication.
A lack of timely communication then affects effective team discussions and negotiations as well as feedback, which reduces team performance.  The correlations analysis between the benefits of effective conflict-risk management and Agile goals is shown (Table 4). The objective of this analysis was to check if there is any correlation between the two variables. To test the significant relationships if any, Pearson's correlation is used. According to Pallant (2016) with Pearson's correlation, it is also possible to determine the strength of the relationships above just showing relationships. This indicates how much each variable determines or correlates with other variables. The Pearson's correlations r values indicate numbers between 0 and 1 and there are specific rules that guide the interpretation of these numbers (Fricker et al. 2019;Pallant 2016). The following rules according to Pallant (2016) apply when interpreting r values to determine the strength of relationships: • small r = 0.10 to 0.29 • medium r = 0.30 to 0.49 • large r = 0.50 to 1.0.
Based on the results (Table 4), the following were concluded.
• The results indicate that there is a strong positive significant correlation between effective interaction, discussions and quality software application (r = 0.776 and p = 0.000). These results indicate that when teams continually interact during software projects development, the likelihood of the team to deliver quality software product is high. These results are inline with Freire et al. (2015) and Moe, Dingsøyr and Dybå (2010), stating that teams interact and communicate to deliver quality software projects. • The results indicate that there is a strong positive significant correlation between team engagements and right software products (r = 0.807 and p = 0.000). This is in relation to the Agile Manifesto's values. Vithana et al.
(2019) stated that teams need to keep on engaging to deliver valuable software products, hence the string relationship between the two variables. • The results indicate that there is a strong positive significant correlation between better team understandings and time-to-market constraints (r = 0.628 and p = 0.000). As stated by Project Management Institute (2018), frequent delivery of working software is of utmost important when using Agile methodologies. • The results indicate that there is a strong positive significant correlation between team effectiveness, maturity and team transparency and effectiveness (r = 0.807 and p = 0.000). These results indicate that working with matured teams can result in effectiveness in software development process as indicated by Gren, Torkar and Feldt (2017). • The results indicate that there is a strong positive significant correlation between productive negotiations and right software quality (r = 0.807 and p = 0.000). Lack of negotiations can reduce teams' performance (Gren & Lenberg 2018). With the strength of the relationship evident, it is therefore implied that in order to deliver right-quality software products, project team leaders must ensure all positive negotiations with all stakeholders involved.

Conceptual framework for conflict-risk management
Conflict as a risk in Agile teams has been explored in current literature; however, there is no research that has directly established a link between effective conflict-risk management within Agile teams towards organisations ability to attain technology adequacy and competitiveness. Researchers Crawford et al. (2014); Saxena et al. (2016) and Gren (2017) have investigated the conflict within Agile environments, its relative sources as well as means of handling and managing it to enable better team collaborations. Effective teams are the ground work for every successful organisation, and organisations generally fail at their strategic goals if they lack effective teams (Kiitam et al. 2016). Organisations without teams who work well together normally struggle, even with the simplest task implemented, while effective teams support in improved quality, facilitation of the completion of projects and aid in increasing productivity and efficiency (Anumah 2017). Effectiveness of the team is the foundation for successful Agile development and successful implementation of Agile projects (Hoda & Noble 2017). Effective continuous delivery of successful Agile projects within the organisations is the foundation of the organisations' ability to keep up with the fast-paced technological world, and hence constantly be able to survive the technology-based competition and needs (Morris et al. 2015).
According to Galli (2018), team effectiveness can be described as the capability for a team to achieve the goals or objectives set by authorised employees or by the organisation. Agile methodology advocacy for frequent team interactions and constant customer collaborations throughout the project life cycle signifies that there should be some degree to effective management of disagreements that arise, as this would have a direct effect to future team interactions (Hummel, Rosenkranz & Holten 2016). According to Crawford et al. (2014) and Balbes (2014), when conflict risk within Agile teams is mishandled and mismanaged, the effect of the risk becomes negative to the future team interactions and collaborations. However, when conflict risk is effectively managed, it leads to constructive sharing of views, ideas and opinions among team members (Crawford et al. 2014). The constructive sharing of views, ideas and opinions leads to smarter solutions of handling the project, and hence improves the team effectiveness (Balbes 2014). The results as indicated (Figure 3) illustrate that effective conflictrisk management enables Agile goals, while Agile goals facilitate organisational goals for adopting Agile to ensure that there is improved technology competitiveness.

Discussions and implication of the study findings
The study examined how constructive conflict in Agile teams affects the team-specific Agile goals, particularly the benefits of effective conflict management on set project Agile goals within Agile teams. To achieve this study objective, the researcher conducted a Pearson's correlation analysis among the variables that constitutes the outcomes of constructive conflict versus the variables that constitute Agile goals. The study findings highlight a strong connection between constructive conflict outcome, 'Effective interactions and discussion' on the achievement of, 'Improved Productivity', 'Delivery of right, quality software' that meets the set 'Timeto-market constraint' and 'Client satisfaction and approval'. 'Effective interactions and discussion' also facilitates 'Team transparency and effectiveness'. Moreover, the study can identify the constructive conflict outcomes; 'Team engagements', 'Team understanding', 'Team effectiveness and maturity', and 'Productive negotiations' as having a direct relation and connection on the achievement of specific Agile goals such as 'Team effectiveness', 'Effective input and feedback' and 'Improved Productivity, 'Delivery of right, quality product that meets the set time-to-market constraint'.
On the other hand, there is a constant significant highlight in the findings, which indicates that the specific Agile goal 'client satisfaction and approval' shares very limited correlation and relation towards majority of the constructive conflict outcomes. This particular finding shows that existence of conflict management within Agile teams has no apparent significance to the client' system approval or satisfaction.
These study findings are beneficial to all members and stakeholders of Agile developing environment because the results address: • the issue of conflict as a risk in IT projects, particularly Agile projects • the impact of effectively managed conflict in Agile environments, which the current literature identifies as a promoter of team effectiveness, which leads to the successful delivery of Agile development projects • the impact of unmanaged conflict in Agile environments, which the current literature identifies as a facilitator of project failure • most importantly validated how various outcomes of constructive conflict existence within project teams are directly related to the achievement of set Agile project goals, which, in turn, facilitates organisations ability to attain technology competitiveness.

Conclusion
This article has positively illustrated the relationship between an organisations technology competitiveness and effectively managed conflict risk in Agile teams. The findings show an extreme and vital role of conflict as a risk and its effective mitigation concerning an organisation's ability to maintain an effective technology adequacy, which can assist in its total success. The existing literature identified effective conflict-risk management as a constituent towards successful Agile projects. Constructive management of conflict among Agile teams fosters team effectiveness and continuous delivery of high-quality standard software product deliverables. This, in turn, facilitates organisations to maintain a productive and efficient response to the ongoing, changing customer demands using technology (Mbelli & Hira 2016). This technology advantage enables organisations to then realise the benefits of technology investments made, including the adoption of Agile, and this encourages them to maintain further technology competitiveness (Rodrigues & José 2015).

Ethical considerations
This letter serves to confirm that the proposed research project has been granted ethical clearance by the School of Consumer Intelligence and Information Systems Ethics committee at the University of Johannesburg. Please refer to the report below for the ethical clearance number and specified conditions of approval.

Funding information
This research received no specific grant from any funding agency in the public, commercial or not-for-profit sectors.