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.

Veikko Isotalo

dblp:167/0201 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
0since 2021 · last 2015
—ORCID · unresolved

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

Software engineering, systems software and programming languages · 1

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 · 100%
Interdisciplinary, comprehensive, and emerging computing
1 paper
Computing education · 100%

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

TopicWeightPapersLastEvidence papers
Computing education › software engineering education
global software engineering education
0.212015
Learning Global Agile Software Engineering Using Same-Site and Cross-Site Teams · ICSE (2) 2015
Computing education
software engineering education
0.212015
Learning Global Agile Software Engineering Using Same-Site and Cross-Site Teams · ICSE (2) 2015
Empirical software engineering
collaborative software development
0.212015
Learning Global Agile Software Engineering Using Same-Site and Cross-Site Teams · ICSE (2) 2015
Empirical software engineering › developer studies
global software development
0.212015
Learning Global Agile Software Engineering Using Same-Site and Cross-Site Teams · ICSE (2) 2015
Empirical software engineering
developer studies
0.112015
Learning Global Agile Software Engineering Using Same-Site and Cross-Site Teams · ICSE (2) 2015

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

repository mining · 0.4questionnaire · 0.4mixed-method study · 0.4interviews · 0.4
YearPublicationVenuePosition
2015 Learning Global Agile Software Engineering Using Same-Site and Cross-Site Teams
abstract
We describe an experience in teaching global software engineering (GSE) using distributed Scrum augmented with industrial best practices. Our unique instructional technique had students work in both same-site and cross-site teams to contrast the two modes of working. The course was a collaboration between Aalto University, Finland and University of Victoria, Canada. Fifteen Canadian and eight Finnish students worked on a single large project, divided into four teams, working on interdependent user stories as negotiated with the industrial product owner located in Finland. Half way through the course, we changed the teams so each student worked in both a local and a distributed team. We studied student learning using a mixed-method approach including 14 post-course interviews, pre-course and Sprint questionnaires, observations, meeting recordings, and repository data from git and Flow dock, the primary communication tool. Our results show no significant differences between working in distributed vs. Non-distributed teams, suggesting that Scrum helps alleviate many GSE problems. Our post-course interviews and survey data allows us to explain this effect, we found that students over time learned to better self-select tasks with less inter-team dependencies, to communicate more, and to work better in teams.
Maria Paasivaara, Kelly Blincoe, Casper Lassenius, Daniela E. Damian, Jyoti Sheoran, Francis Harrison, Prashant Chhabra, Aminah Yussuf, Veikko Isotalo
ICSE (2)9