Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.

J. Alberto Espinosa

dblp:71/3833 · DBLP profile ↗
← Back
3ranked-venue papers
2as first author
0since 2021 · last 2013
0000-0002-4537-9945ORCID · corroborated

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 2 · 1 first-authorHuman-computer interaction and ubiquitous computing · 1 · 1 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
1 paper
Empirical software engineering · 67% Requirements engineering and software design · 33%
Human-computer interaction and pervasive computing
1 paper
Collaborative and social computing · 61% User interface design and tools · 30% Usability and user experience research · 9%

Topics — the 5 heaviest of 7, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Empirical software engineering › developer studies
global software development
0.212013
Task Environment Complexity, Global Team Dispersion, Process Capabilities, and Coordination in Software Development · IEEE Trans. Software Eng. 2013
Requirements engineering and software design
software process
0.212013
Task Environment Complexity, Global Team Dispersion, Process Capabilities, and Coordination in Software Development · IEEE Trans. Software Eng. 2013
Empirical software engineering › software project management
team coordination
0.212013
Task Environment Complexity, Global Team Dispersion, Process Capabilities, and Coordination in Software Development · IEEE Trans. Software Eng. 2013
Collaborative and social computing › awareness
awareness systems
0.012000
Coming to the wrong decision quickly: why awareness tools must be matched with appropriate tasks · CHI 2000
Collaborative and social computing › computer-supported cooperative work › distributed collaboration
distributed problem solving
0.012000
Coming to the wrong decision quickly: why awareness tools must be matched with appropriate tasks · CHI 2000

Methods — techniques the papers use, named apart from their topics

hypothesis testing · 0.2field survey · 0.2laboratory study · 0.0
YearPublicationVenuePosition
2013 Task Environment Complexity, Global Team Dispersion, Process Capabilities, and Coordination in Software Development
abstract
Software development teams are increasingly global. Team members are separated by multiple boundaries such as geographic location, time zone, culture, and organization, presenting substantial coordination challenges. Global software development becomes even more challenging when user requirements change dynamically. However, little empirical research has investigated how team dispersion across multiple boundaries and user requirements dynamism, which collectively increase task environment complexity, influence team coordination and software development success in the global context. Further, we have a limited understanding of how software process capabilities such as rigor, standardization, agility, and customizability mitigate the negative effects of global team dispersion and user requirements dynamism. To address these important issues, we test a set of relevant hypotheses using field survey data obtained from both project managers and stakeholders. Our results show that global team dispersion and user requirements dynamism have a negative effect on coordination effectiveness. We find that the negative effect of global team dispersion on coordination effectiveness decreases as process standardization increases and that the negative effect of user requirements dynamism on coordination effectiveness decreases as process agility increases. We find that coordination effectiveness has a positive effect on global software development success in terms of both process and product aspects.
Gwanhoo Lee, J. Alberto Espinosa, William H. DeLone
IEEE Trans. Software Eng.2
2007 Do Gradations of Time Zone Separation Make a Difference in Performance? A First Laboratory Study
abstract
We often hear that global software engineering teams are affected by time differences. While there is considerable research on the difficulties of distance, culture and other dimensions, there has been little research that isolated the impact of just time differences. The research question that guides us is whether there are gradual differences across time zones that impact team performance. In this study we conducted a laboratory experiment with 42 dyadic teams. The teams were randomly assigned into 4 time zone overlap conditions: full overlap, 2/3 overlap, 1/3 overlap and no overlap. Using a fictional map task, we found that participants' perceptions of process are unrelated to actual objective performance measures of speed and accuracy. Consistent with our expectations, we found that a small time separation has no effect on accuracy, but that more time separation has a significant effect on accuracy. Also consistent with our expectations, we found that a small amount of time separation has a significant effect on production speed. However, contrary to our expectations, we found that further increases in partial overlap have less significant effects on speed, and when there is no overlap speed actually increases, albeit not significantly - a "U-shaped" effect.
J. Alberto Espinosa, Ning Nan, Erran Carmel
ICGSE1
2000 Coming to the wrong decision quickly: why awareness tools must be matched with appropriate tasks
abstract
This paper presents an awareness tool designed to help distributed, asynchronous groups solve problems quickly. Using a lab study, it was found that groups that used the awareness tool tended to converge and agree upon a solution more quickly. However, it was also found that individuals who did not use the awareness tool got closer to the correct solution. Implications for the design of awareness tools are discussed, with particular attention paid to the importance of matching the features of an awareness tool with a workgroup's tasks and goals.
J. Alberto Espinosa, Jonathan J. Cadiz, Luis Rico-Gutierrez, Robert E. Kraut, William L. Scherlis, Glenn Lautenbacher
CHI1