Explaining Developer Attitude Toward Using Formalized Commercial Methodologies: Decomposing Perceived Usefulness

dc.contributor.authorHenderson, David Lockhart IIIen
dc.contributor.committeecochairSheetz, Steven D.en
dc.contributor.committeecochairBelanger, Franceen
dc.contributor.committeememberRees, Loren P.en
dc.contributor.committeememberTegarden, David P.en
dc.contributor.committeememberWallace, Linda G.en
dc.contributor.departmentAccounting and Information Systemsen
dc.date.accessioned2014-03-14T20:16:10Zen
dc.date.adate2007-09-25en
dc.date.available2014-03-14T20:16:10Zen
dc.date.issued2007-09-07en
dc.date.rdate2010-10-27en
dc.date.sdate2007-09-12en
dc.description.abstractAlthough methodology use generally leads to fewer software defects and reductions in development time, the introduction of a formalized systems development methodology is often met with substantial resistance. Motivated by the purported benefits of methodology use, yet resistance to the introduction of a methodology, this study explains developer attitude toward using a formalized commercial methodology. An important variable for explaining attitude is perceived usefulness, defined as the degree to which using a methodology will enhance a developer's job performance. If, however, a benefit of using a methodology is different than increased job performance, then limiting the definition of perceived usefulness to beliefs surrounding job performance may provide an incomplete representation of what makes a methodology useful to developers. A methodology may be perceived as a rational process, used to achieve objectives such as increasing job performance or as a political process used to achieve objectives particular to one person or group. In order to determine what makes a methodology useful to developers, the perceived usefulness construct was expanded to include benefits of methodology use related toward achieving political objectives. In addition to broadening the perceived usefulness construct, this research also broke down perceived usefulness into its referent dimensions. Decomposing perceived usefulness provided a deeper understanding of what makes a methodology useful to developers and revealed the relative importance of each dimension of perceived usefulness. The study surveyed 120 developers. Partial least squares regression was used to test the antecedents of developer attitude as well as the hypothesized structure of perceived usefulness. Results indicate that developers will have more favorable attitudes toward methodologies they perceive as useful, easy to use, and consistent with the way they like to develop systems. Additionally, findings suggest that developers may find methodologies not only useful for achieving rational goals such as increasing system quality, raising productivity, and enhancing communication, but also useful for achieving political goals such as increasing career opportunities, showing others that professional development practices are being used, reducing anxiety, and defending against unreasonable user demands.en
dc.description.degreePh. D.en
dc.identifier.otheretd-09122007-195738en
dc.identifier.sourceurlhttp://scholar.lib.vt.edu/theses/available/etd-09122007-195738/en
dc.identifier.urihttp://hdl.handle.net/10919/28954en
dc.publisherVirginia Techen
dc.relation.haspartDaveHendersonDissertation.pdfen
dc.rightsIn Copyrighten
dc.rights.urihttp://rightsstatements.org/vocab/InC/1.0/en
dc.subjectsystems development methodologiesen
dc.subjectattitudeen
dc.subjectdeveloperen
dc.subjectperceived usefulnessen
dc.titleExplaining Developer Attitude Toward Using Formalized Commercial Methodologies: Decomposing Perceived Usefulnessen
dc.typeDissertationen
thesis.degree.disciplineAccounting and Information Systemsen
thesis.degree.grantorVirginia Polytechnic Institute and State Universityen
thesis.degree.leveldoctoralen
thesis.degree.namePh. D.en
Files
Original bundle
Now showing 1 - 1 of 1
Loading...
Thumbnail Image
Name:
DaveHendersonDissertation.pdf
Size:
1.97 MB
Format:
Adobe Portable Document Format