dc.contributor.author | Isomöttönen, Ville | |
dc.contributor.author | Taipalus, Toni | |
dc.date.accessioned | 2023-01-13T11:13:29Z | |
dc.date.available | 2023-01-13T11:13:29Z | |
dc.date.issued | 2023 | |
dc.identifier.citation | Isomöttönen, V., & Taipalus, T. (2023). Status indicators in software engineering group projects. <i>Journal of Systems and Software</i>, <i>198</i>, Article 111612. <a href="https://doi.org/10.1016/j.jss.2023.111612" target="_blank">https://doi.org/10.1016/j.jss.2023.111612</a> | |
dc.identifier.other | CONVID_165010079 | |
dc.identifier.uri | https://jyx.jyu.fi/handle/123456789/85002 | |
dc.description.abstract | A segment of studies on group structure and performance in software engineering (SE) project-based learning (PjBL) have focused on roles, including studies that use Belbin team roles and studies that address problematic roles such as social loafing. The present study focuses on the status, which is basically missing in SE PjBL studies, although relating to roles. The study investigates the aspects that students identified as indicators of rising or declining status in their project groups. The status theory was utilized as the framework that motivated the research and on which the results were reflected. An inductive qualitative content analysis was applied to learning reports in which students reflected on their statuses. The indicators of rising status included technical know-how, commitment, management responsibility, and idea ownership, while also group-level attributes such as a caring atmosphere and joint responsibility. The indicators of a declining status included aspects that appear as counterparts of rising status indicators, while also more refined aspects such as no one willing to be a leader or study background. The results are concluded to provide material for educating students about intra-group relations and promoting self-regulation for fruitful collaboration in groups. The authors believe that the results also initiate further PjBL research in which status theory can be utilized. | en |
dc.format.mimetype | application/pdf | |
dc.language.iso | eng | |
dc.publisher | Elsevier | |
dc.relation.ispartofseries | Journal of Systems and Software | |
dc.rights | CC BY 4.0 | |
dc.subject.other | group work | |
dc.subject.other | status concept | |
dc.subject.other | higher education | |
dc.title | Status indicators in software engineering group projects | |
dc.type | article | |
dc.identifier.urn | URN:NBN:fi:jyu-202301131310 | |
dc.contributor.laitos | Informaatioteknologian tiedekunta | fi |
dc.contributor.laitos | Faculty of Information Technology | en |
dc.contributor.oppiaine | Computing Education Research | fi |
dc.contributor.oppiaine | Tutkintokoulutus | fi |
dc.contributor.oppiaine | Computing Education Research | en |
dc.contributor.oppiaine | Degree Education | en |
dc.type.uri | http://purl.org/eprint/type/JournalArticle | |
dc.type.coar | http://purl.org/coar/resource_type/c_2df8fbb1 | |
dc.description.reviewstatus | peerReviewed | |
dc.relation.issn | 0164-1212 | |
dc.relation.volume | 198 | |
dc.type.version | publishedVersion | |
dc.rights.copyright | © 2023 The Author(s). Published by Elsevier Inc. | |
dc.rights.accesslevel | openAccess | fi |
dc.subject.yso | korkeakouluopetus | |
dc.subject.yso | ohjelmistotuotanto | |
dc.subject.yso | ryhmätyö | |
dc.format.content | fulltext | |
jyx.subject.uri | http://www.yso.fi/onto/yso/p1246 | |
jyx.subject.uri | http://www.yso.fi/onto/yso/p17097 | |
jyx.subject.uri | http://www.yso.fi/onto/yso/p4079 | |
dc.rights.url | https://creativecommons.org/licenses/by/4.0/ | |
dc.relation.doi | 10.1016/j.jss.2023.111612 | |
dc.type.okm | A1 | |