2002
DOI: 10.1080/07421222.2002.11045695
|View full text |Cite
|
Sign up to set email alerts
|

A Contingency Approach to Software Project Coordination

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

3
138
0
1

Year Published

2005
2005
2020
2020

Publication Types

Select...
6
2
1

Relationship

0
9

Authors

Journals

citations
Cited by 195 publications
(150 citation statements)
references
References 53 publications
3
138
0
1
Order By: Relevance
“…Software projects vary in their information needs and capabilities and thus may benefit from a tailored management approach. Shenhar (2001) notes that the importance of tailoring project practices to project characteristics has often been ignored in the "universalist" or "best practices" view of project management; thus a more project specific approach is advocated (Andres and Zmud 2002, MacCormack et al 2003. Differences in project contexts (i.e., in project task, team, and PM) are reflected in differences in the projects' information processing needs or capabilities leading to information gaps and thus in the likelihood of critical incidents.…”
Section: An Information Processing Perspective Of Software Offshore Omentioning
confidence: 99%
“…Software projects vary in their information needs and capabilities and thus may benefit from a tailored management approach. Shenhar (2001) notes that the importance of tailoring project practices to project characteristics has often been ignored in the "universalist" or "best practices" view of project management; thus a more project specific approach is advocated (Andres and Zmud 2002, MacCormack et al 2003. Differences in project contexts (i.e., in project task, team, and PM) are reflected in differences in the projects' information processing needs or capabilities leading to information gaps and thus in the likelihood of critical incidents.…”
Section: An Information Processing Perspective Of Software Offshore Omentioning
confidence: 99%
“…It is thus important to understand the trade-offs under different task environments before designing organizations, such as deciding on simple or complex forms. This approach is also advocated by various contingency theorists (Andres and Zmud 2002;Suchman 1987).…”
Section: The Impact Of Task Environmentmentioning
confidence: 99%
“…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%