A Comparison of the Structural Contingency and Risk-Based Perspectives on Coordination in Software-Development Projects

Nidumolu, Sarma R.

doi:10.1080/07421222.1996.11518124

Cited by 134 publications

(144 citation statements)

References 51 publications

Supporting

Mentioning

141

Contrasting

Unclassified

Order By: Relevance

“…Because larger projects generally involve more people, coordination tends to be more mechanistic [28,33] than the more organic methods typical of smaller projects. Expressed differently, larger projects tend to use plans, standards and formal exchanges to coordinate their work whilst smaller projects tend to use stand-up meetings or co-location.…”

Section: Methods Enactmentmentioning

confidence: 99%

“…Coordination is usually achieved through developing a work breakdown structure, a schedule for its completion and reintegration, plans of how the work is to be completed, standards of how the work is to be done and standards relating to what work needs to be produced [27][28][29]. Since software development is inherently uncertain, there is usually a need for dynamic coordination, achieved through meetings, reviews and other exchanges.…”

Section: Methods Designmentioning

confidence: 99%

“…Various authors have identified sources of uncertainty including platform and market uncertainty [35], requirements uncertainty [28], outcome uncertainty and task programmability [36] as significantly influencing choices of method and its tailoring. While specific relationships between different types of uncertainty and method may need some investigation, the general connection seems to be well accepted.…”

Section: Methods Enactmentmentioning

confidence: 99%

See 2 more Smart Citations

A Method Assessment Framework

McBride

Henderson‐Sellers

2011

IFIP Advances in Information and Communication Technology

View full text Add to dashboard Cite

Abstract. Situational method engineering is used to create methods for use on projects. It is vital that such constructed methods be of good quality and relevant to the software development project in hand. Current capability assessment approaches cannot readily be applied to such SME-constructed methods since they do not differentiate between the three "phases" of method construction and enactment: method design, method enactment and method performance. Here, we clearly differentiate the kind of quality assessment activities that need to be performed in these three different situations.

show abstract

Section: Methods Enactmentmentioning

confidence: 99%

Section: Methods Designmentioning

confidence: 99%

Section: Methods Enactmentmentioning

confidence: 99%

See 1 more Smart Citation

A Method Assessment Framework

McBride

Henderson‐Sellers

2011

IFIP Advances in Information and Communication Technology

View full text Add to dashboard Cite

show abstract

“…We realized that some studies used term ‗performance' to denote all variations between a failure and a success, e.g. studies [32][33][34][35]. Both the terms ‗failure' and ‗success' were replaced by the term ‗performance', and the set of searches was re-run with those changes.…”

Section: Doi: 102478/v10143-011-0010-9 2011mentioning

confidence: 99%

The Presence of the Customer and the Supplier Perspectives in Studies on Software Development Project Success

Ahonen¹,

Savolainen²

2011

Scientific Journal of Riga Technical University. Computer Sciences

View full text Add to dashboard Cite

-A systematic literature review on software development project success/failure from customer's or supplier's perspective is presented. The review covers studies published in peer-reviewed journals only. The results show that knowledge on software development project success/failure is multidisciplinary and fragmented. In addition, there are very few studies that consider software development project success from the supplier's perspective. One of the main contributions of this article is the table of articles in which articles have been classified by the perspective which they discuss. Another contribution is the list of journals in which the accepted articles have been published. Moreover, these results show a clear lack in our understanding of software development project success in outsourcing situations.

show abstract

“…Journal of Operational Risk, 9(3), 53-88. IT literature has produced a number of conceptual frameworks to explain different types of software development risk, risk management strategies and measures of software project performance (Dingsoyr et al, 2012;Nidumolu, 1996;. Many studies suggest that failure to manage risks causes common problems such as cost overruns, unsuitability for intended task, unmet user requirements and schedule overruns (Appari & Benaroch, 2010;Capilla et al, 2014;Magdaleno et al, 2012).…”

Section: Introductionmentioning

confidence: 99%

Factor reduction and clustering for operational risk in software development

Mohd-Rahim¹,

Chen²,

Boussabaine³

et al. 2014

JOP

View full text Add to dashboard Cite

Software development failures frequently emerge as a result of the failure to understand and identify risks.The aim of this paper is to identify the most salient risk factors during a software development project lifecycle, in terms of occurrence likelihood and impacts on cost overrun. A questionnaire survey was circulated to 2000 software development companies, IT consultancy and management companies, and web development companies in the UK, USA, Europe, India, China, Japan, Canada, Australia and Asian countries.This asked respondents to evaluate a number of risk factors. However, many factors were closely related and so we apply a factor reduction and clustering process to allow a smaller number of crucial risk factors to be identified. The three main clusters of risk factors identified in this study are 'feasibility study', 'project team management', and 'technology requirements'. While 'feasibility study' may be unlikely to occur it can have significant impact on outcomes; 'project team management' is likely to occur but has relatively little impact on outcomes in comparison to 'technology requirements'. Professionals will need to carefully check and balance these factors and generate a risk mitigation plan to reduce the severity of the project failures. These results allow them to connect the probability of occurrence and overall impact to focus their scarce resources on reducing the most pertinent risks in their project.Keywords: factor reduction, factor clustering, software development risk, risk occurrence likelihood, cost overrun INTRODUCTIONSoftware projects are dynamic and tend to have volatile requirements making them difficult to manage and control as the project scope can change frequently. Failure to understand and to identify risks leads to software development failures (Stahl & Bosch, 2014;Reyes et al., 2011). Literature on how to manage a development project often refers to cost, time, and quality as the key project success criteria; however, there are also many other different, broad, and overlapping definitions of project success and failures (Portillo-Rodríguez et al., 2014;Jorgensen, 2010;Baccarini et al., 2004;Linberg, 1999;Ropponen, 2000). Various researchers observe that in practice it may be very difficult to claim the project was really successful or a failure (Martín & Yelmo, 2014). A single project can be considered successful by one stakeholder and failure by another (Naquin & Tynan, 2003;Thüm et al., 2014). This is a copy of the "Post-print" (i.e., final authors' copy, post-refereeing). Published as:Mohd-Rahim, F. A., Wang, C., Boussabaine, H., . Factor reduction and clustering for operational risk in software development. Journal of Operational Risk, 9(3), 53-88. IT literature has produced a number of conceptual frameworks to explain different types of software development risk, risk management strategies and measures of software project performance (Dingsoyr et al., 2012;Nidumolu, 1996;. Many studies suggest that failure to manage risks causes common problems such as cost...

show abstract

A Comparison of the Structural Contingency and Risk-Based Perspectives on Coordination in Software-Development Projects

Cited by 134 publications

References 51 publications

A Method Assessment Framework

A Method Assessment Framework

The Presence of the Customer and the Supplier Perspectives in Studies on Software Development Project Success

Factor reduction and clustering for operational risk in software development

Contact Info

Product

Resources

About