2015
DOI: 10.5614/itbj.ict.res.appl.2015.9.1.4
|View full text |Cite
|
Sign up to set email alerts
|

Requirement Volatility, Standardization and Knowledge Integration in Software Projects: An Empirical Analysis on Outsourced IS Development Projects

Abstract: Information systems development (ISD) projects are highly complex, with different groups of people having to collaborate and exchange their knowledge. Considering the intensity of knowledge exchange that takes place in outsourced ISD projects, in this study a conceptual model was developed, aiming to examine the influence of four antecedents, i.e. standardization, requirement volatility, internal integration, and external integration, on two dependent variables, i.e. process performance and product performance… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
4
0

Year Published

2016
2016
2023
2023

Publication Types

Select...
7
1

Relationship

1
7

Authors

Journals

citations
Cited by 10 publications
(5 citation statements)
references
References 39 publications
0
4
0
Order By: Relevance
“…The literature consistently indicates that variations in project/task requirements pose significant risks to the project/team performance because they can significantly disturb the arrangement of the use of critical team resources (Thakurta, 2010), and thus can result in task and relationship conflicts among team members (Sawyer, 2001). Additionally, while it is essential to integrate and to utilize, appropriately, various kinds of team member knowledge to handle variations in project/task requirements in the team's assignment, poor integration of knowledge can result in conflicting interpretations of the project/task requirements and a decrease in the effectiveness of intrateam collaboration, which may eventually lead to conflict between team members (Govindaraju et al , 2015). Huzooree and Ramdoo (2015) also imply that frequent changes in project requirements increase the probability of the occurrence of interpersonal conflicts in project teams because it makes it more difficult to reconcile the different perceptions of team members who have different perspectives regarding the focal project.…”
Section: Discussionmentioning
confidence: 99%
“…The literature consistently indicates that variations in project/task requirements pose significant risks to the project/team performance because they can significantly disturb the arrangement of the use of critical team resources (Thakurta, 2010), and thus can result in task and relationship conflicts among team members (Sawyer, 2001). Additionally, while it is essential to integrate and to utilize, appropriately, various kinds of team member knowledge to handle variations in project/task requirements in the team's assignment, poor integration of knowledge can result in conflicting interpretations of the project/task requirements and a decrease in the effectiveness of intrateam collaboration, which may eventually lead to conflict between team members (Govindaraju et al , 2015). Huzooree and Ramdoo (2015) also imply that frequent changes in project requirements increase the probability of the occurrence of interpersonal conflicts in project teams because it makes it more difficult to reconcile the different perceptions of team members who have different perspectives regarding the focal project.…”
Section: Discussionmentioning
confidence: 99%
“…The factors such as Lack of detailed specifications, ambiguous requirements, and project specificity all have a significant impact on global IT development. Both the vendor and the client must establish collaboration when working on an IT project [95]. Similar to this Beulen et al [6] have discussed that any change in the business process at the time of project's execution, leads to changes in requirements.…”
Section: ) Decision Making Using Proposed Frameworkmentioning
confidence: 92%
“…Another most recurring factor in our study was requirement volatility. According to [63], requirement volatility can be defined "as any change or growth in project's requirement specification". It is essential to mention here that requirement volatility contributed as a critical factor in project failure according to chaos report [37].…”
Section: Requirement Volatility (F5)mentioning
confidence: 99%