Actively involving our information development teams with clients

Rivera, Theodore; Tate, Adam L.; Will, Scott A.

doi:10.1145/944868.944904

Cited by 2 publications

(1 citation statement)

References 1 publication

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Artifacts (i.e., outputs) from software development processes are reviewed and evaluated as indicators of whether systems meet client needs (Ang & Slaughter, 2001;Miyoshi & Azuma, 1993;Rangarajan, Swaminathan, Hegde, & Jacob, 2001;Smith & McKeen, 1996) and as potential indicators of a system's quality (Arthur, 1985;Beise, 1994;Rivera, Tate, & Will, 2003). For these reasons, project teams conduct assessments of project artifacts to ensure that the proposed system, including changes in the project's goals (Barry, Kemerer, & Slaughter, 2006;Bolman & Deal, 1992;Leenders, Engelen, & Kratzer, 2003), meet and are within user and organizational objectives and resource limitations.…”

Section: Implications For Research and Practicementioning

confidence: 99%

Software Development Methodologies in Organizations

Kacmar

McManus

Duggan

et al. 2009

Information Resources Management Journal

View full text Add to dashboard Cite

The theories of social exchange, task-technology fit, and technology acceptance are utilized in a field study of software development methodologies. This investigation includes the effects of user experiences on perceptions of acceptance and usage of a methodology. More specifically, perceptions of the outputs and deliverables from a methodology and perceptions of challenges and obstacles to using and applying a methodology were found to significantly and positively influence perceived usefulness and negatively influence ease of use of a methodology, respectively, within a developer’s organization. Perceived usefulness was a positive and strong antecedent to perceptions of fit between the methodology and client problems, and the strengthening of efficacy beliefs about the methodology.

show abstract