2011
DOI: 10.1007/978-3-642-20677-1_25
|View full text |Cite
|
Sign up to set email alerts
|

Lost in Agility? Approaching Software Localization in Agile Software Development

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2012
2012
2023
2023

Publication Types

Select...
3
2
1

Relationship

0
6

Authors

Journals

citations
Cited by 6 publications
(2 citation statements)
references
References 3 publications
0
2
0
Order By: Relevance
“…In fact, only Malte Ressin seems to have dealt with the problems of agile localization, albeit by looking at relationships between a development team and a localization team working on the same project. Ressin's papers [1], [2] and [3] examine agile localization from a psychological standpoint, pointing at different goals, an understanding of each other's subjects, and concepts of the quality of two involved teams. Ressin also completed a dissertation [4] on this matter.…”
Section: Literature Reviewmentioning
confidence: 99%
“…In fact, only Malte Ressin seems to have dealt with the problems of agile localization, albeit by looking at relationships between a development team and a localization team working on the same project. Ressin's papers [1], [2] and [3] examine agile localization from a psychological standpoint, pointing at different goals, an understanding of each other's subjects, and concepts of the quality of two involved teams. Ressin also completed a dissertation [4] on this matter.…”
Section: Literature Reviewmentioning
confidence: 99%
“…all except one paper was less than ten years of age. [39], Irrazabal et al [40], Hoda et al [41], [42], Dorairaj et al [43], Senapathi et al [44], Ressin et al [45], [46], Santos and Goldman [47], Kim and Ryoo [48], Ihme [49], and Allisy-Roberts et al [4], with publication years ranging from 2008 to 2017. Of the listed challenges, the one that is very peculiar comes from the mixed mode study by Heikkila et al [18], which recorded that cross functional generalist teams were not plausible in the environment.…”
Section: Scrum Adoption Challengesmentioning
confidence: 99%