Enabling Software Development Team Performance During Requirements Definition: A Behavioral Versus Technical Approach.

Author List: Guinan, Patricia J.; Cooprider, Jay G.; Faraj, Samer;
Information Systems Research, 1998, Volume 9, Issue 2, Page 101-125.
As software development projects continue to be over budget and behind schedule, researchers continue to look for ways to improve the likelihood of project success. In this research we juxtapose two different views of what influences software development team performance during the requirements development phase. In an examination of 66 teams from 15 companies we found that team skill, managerial involvement, and little variance in team experience enable more effective team processes than do software development tools and methods. Further, we found that development teams exhibit both positive and negative boundary-spanning behaviors. Team members promote and champion their projects to the outside environment, which is considered valuable by project stakeholders. They also, however, guard themselves from their environments; keeping important information a secret from stakeholders negatively predicts performance.
Keywords: Case Tools; Information Systems Development; Managerial Effectiveness; Software Development; Team Processes
Algorithm:

List of Topics

#135 0.191 project projects development management isd results process team developed managers teams software stakeholders successful complex develop contingencies problems greater planning
#152 0.157 software development process performance agile processes developers response tailoring activities specific requirements teams quality improvement outcomes productivity improve fit maturity
#87 0.108 team teams virtual members communication distributed performance global role task cognition develop technology involved time individual's affects project geographically individuals
#75 0.096 behavior behaviors behavioral study individuals affect model outcomes psychological individual responses negative influence explain hypotheses expected theories consequences impact theory
#261 0.086 software development maintenance case productivity application tools systems function tool engineering projects effort code developed applications analysis estimation methodology methods
#139 0.071 project projects failure software commitment escalation cost factors study problem resources continue prior escalate overruns taken failing troubled sunk fail
#154 0.071 memory support organizations information organizational requirements different complex require development provides resources organization paper transactive depth process outside difficult breadth
#221 0.056 competence experience versus individual disaster employees form npd concept context construct effectively focus functionalities front-end knowledge-intensive stage explores set definition