dc.contributor.author |
Andriyani, Yanti |
en |
dc.contributor.author |
Hoda, Rashina |
en |
dc.contributor.author |
Amor, Robert |
en |
dc.contributor.editor |
Baumeister, H |
en |
dc.contributor.editor |
Lichter, H |
en |
dc.contributor.editor |
Riebisch, M |
en |
dc.coverage.spatial |
Cologne, Germany |
en |
dc.date.accessioned |
2018-06-11T03:02:39Z |
en |
dc.date.issued |
2017 |
en |
dc.identifier.citation |
In: Baumeister H., Lichter H., Riebisch M. (eds) Agile Processes in Software Engineering and Extreme Programming. XP 2017. Lecture Notes in Business Information Processing, vol 283. Springer |
en |
dc.identifier.isbn |
978-3-319-57633-6 |
en |
dc.identifier.issn |
1865-1348 |
en |
dc.identifier.uri |
http://hdl.handle.net/2292/37245 |
en |
dc.description.abstract |
A retrospective is a standard agile meeting practice designed for agile software teams to reflect and tune their process. Despite its integral importance, we know little about what aspects are focused upon during retrospectives and how reflection occurs in this practice. We conducted Case Study research involving data collected from interviews of sixteen software practitioners from four agile teams and observations of their retrospective meetings. We found that the important aspects focused on during the retrospective meeting include identifying and discussing obstacles, discussing feelings, analyzing previous action points, identifying background reasons, identifying future action points and generating a plan. Reflection occurs when the agile teams embody these aspects within three levels of reflection: reporting and responding, relating and reasoning, and reconstructing. Critically, we show that agile teams may not achieve all levels of reflection simply by performing retrospective meetings. One of the key contributions of our work is to present a reflection framework for agile retrospective meetings that explains and embeds three levels of reflection within the five steps of a standard agile retrospective. Agile teams can use this framework to achieve better focus and higher levels of reflection in their retrospective meetings. |
en |
dc.description.uri |
https://www.agilealliance.org/xp2017/ |
en |
dc.publisher |
Springer |
en |
dc.relation.ispartof |
XP 2017 |
en |
dc.relation.ispartofseries |
Agile Processes in Software Engineering and Extreme Programming: 18th International Conference, XP 2017, Proceedings |
en |
dc.rights |
Items in ResearchSpace are protected by copyright, with all rights reserved, unless otherwise indicated. Previously published items are made available in accordance with the copyright policy of the publisher. Details obtained from https://www.springernature.com/gp/open-research/policies/book-policies |
en |
dc.rights.uri |
https://researchspace.auckland.ac.nz/docs/uoa-docs/rights.htm |
en |
dc.rights.uri |
https://creativecommons.org/licenses/by/4.0/ |
en |
dc.title |
Reflection in agile retrospectives |
en |
dc.type |
Conference Item |
en |
dc.identifier.doi |
10.1007/978-3-319-57633-6_1 |
en |
pubs.begin-page |
3 |
en |
pubs.volume |
LNBIP, vol 283 |
en |
dc.description.version |
VoR - Version of Record |
en |
dc.rights.holder |
Copyright: The author |
en |
pubs.author-url |
https://link.springer.com/chapter/10.1007/978-3-319-57633-6_1 |
en |
pubs.end-page |
19 |
en |
pubs.finish-date |
2017-05-26 |
en |
pubs.publication-status |
Published |
en |
pubs.start-date |
2017-05-22 |
en |
dc.rights.accessrights |
http://purl.org/eprint/accessRights/OpenAccess |
en |
pubs.subtype |
Proceedings |
en |
pubs.elements-id |
626565 |
en |
pubs.org-id |
Engineering |
en |
pubs.org-id |
Department of Electrical, Computer and Software Engineering |
en |
pubs.org-id |
Science |
en |
pubs.org-id |
School of Computer Science |
en |
dc.identifier.eissn |
1865-1356 |
en |
pubs.record-created-at-source-date |
2017-08-09 |
en |
pubs.online-publication-date |
2017-04-14 |
en |