2011
DOI: 10.1016/j.ijproman.2010.06.004
|View full text |Cite
|
Sign up to set email alerts
|

Towards a conceptualisation of quality in information technology projects

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
29
0

Year Published

2012
2012
2022
2022

Publication Types

Select...
7
1
1

Relationship

3
6

Authors

Journals

citations
Cited by 36 publications
(29 citation statements)
references
References 42 publications
0
29
0
Order By: Relevance
“…Individual projects utilise elements of standardised technology solutions together with well-defined operational processes and structures, emphasising exploitation. However, since each customer requirement offers its own unique set of challenges, this must be supported by exploratory activities (Geraldi et al, 2011b). This project-based context is therefore one that provides an ideal environment to examine the mechanisms by which ambidexterity is achieved at an operational level.…”
Section: Case Context and Methodsmentioning
confidence: 99%
“…Individual projects utilise elements of standardised technology solutions together with well-defined operational processes and structures, emphasising exploitation. However, since each customer requirement offers its own unique set of challenges, this must be supported by exploratory activities (Geraldi et al, 2011b). This project-based context is therefore one that provides an ideal environment to examine the mechanisms by which ambidexterity is achieved at an operational level.…”
Section: Case Context and Methodsmentioning
confidence: 99%
“…Care must be taken in interpreting its benefits, though, as a single factor such as sales growth rate (e.g. He and Wong 2004) may be achieved by trading‐off other aspects, whereas achieving multiple, potentially contradictory, objectives can be understood in terms of ambidexterity (Geraldi et al . 2011).…”
Section: Introductionmentioning
confidence: 99%
“…However, software project risk management seems to be rather immature as risks are still not managed effectively (Aloini et al, 2007;Bannerman, 2008;de Bakker et al, 2010;Geraldi et al, 2011;Kappelman et al, 2006;Kutsch and Hall, 2005;Osipova and Eriksson, 2013). In addition to technical risks, software projects are subjected to organizational risks since they affect or are affected by the way of doing things in an organization (Benaroch et al, 2006;Sanderson, 2012;Sharma and Gupta, 2012).…”
Section: Introductionmentioning
confidence: 99%