Baumeister Hubert - Agile processes in software engineering and extreme programming: 18th International Conference, XP 2017, Cologne, Germany, May 22-26, 2017, proceedings
Here you can read online Baumeister Hubert - Agile processes in software engineering and extreme programming: 18th International Conference, XP 2017, Cologne, Germany, May 22-26, 2017, proceedings full text of the book (entire story) in english for free. Download pdf and epub, get meaning, cover and reviews about this ebook. City: Cham;Cologne;Germany, year: 2017, publisher: Springer International Publishing, genre: Business. Description of the work, (preface) as well as reviews are available. Best literature library LitArk.com created for fans of good reading and offers a wide selection of genres:
Choose a favorite category and find really read worthwhile books. Enjoy immersion in the world of imagination, feel the emotions of the characters or learn something new for yourself, make an fascinating discovery.
Book:
Agile processes in software engineering and extreme programming: 18th International Conference, XP 2017, Cologne, Germany, May 22-26, 2017, proceedings
Agile processes in software engineering and extreme programming: 18th International Conference, XP 2017, Cologne, Germany, May 22-26, 2017, proceedings: summary, description and annotation
We offer to read an annotation, description, summary or preface (depends on what the author of the book "Agile processes in software engineering and extreme programming: 18th International Conference, XP 2017, Cologne, Germany, May 22-26, 2017, proceedings" wrote himself). If you haven't found the necessary information about the book — write in the comments, we will try to find it.
Baumeister Hubert: author's other books
Who wrote Agile processes in software engineering and extreme programming: 18th International Conference, XP 2017, Cologne, Germany, May 22-26, 2017, proceedings? Find out the surname, the name of the author of the book and a list of all author's works by series.
Agile processes in software engineering and extreme programming: 18th International Conference, XP 2017, Cologne, Germany, May 22-26, 2017, proceedings — read online for free the complete book (whole text) full work
Below is the text of the book, divided by pages. System saving the place of the last page read, allows you to conveniently read the book "Agile processes in software engineering and extreme programming: 18th International Conference, XP 2017, Cologne, Germany, May 22-26, 2017, proceedings" online for free, without having to search again every time where you left off. Put a bookmark, and you can go to the page where you finished reading at any time.
Hubert Baumeister , Horst Lichter and Matthias Riebisch (eds.) Agile Processes in Software Engineering and Extreme Programming Lecture Notes in Business Information Processing 10.1007/978-3-319-57633-6_1
Reflection in Agile Retrospectives
Yanti Andriyani 1
(1)
SEPTA Research, Department of Electrical and Computer Engineering, The University of Auckland, Building 903, 386 Khyber Pass, New Market, 1023 Auckland, New Zealand
(2)
Department of Computer Science, The University of Auckland, Auckland, New Zealand
Yanti Andriyani (Corresponding author)
Email:
Rashina Hoda
Email:
Robert Amor
Email:
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.
Keywords
Agile retrospective meeting Reflection Levels of reflection Teams Agile software development Reflective practice
Introduction
Retrospective meetings embody the inspect and adapt principle of Agile Software Development (ASD) [].
Much of the existing research focuses on the techniques of performing retrospective meetings and provides lesser detail about the reflection process involved []. However, what is focused on during retrospectives and how reflection occurs in this practice is not well understood.
To address this gap, we conducted Case Study research by observing four agile teams and interviewing 16 of their members guided by the following research questions:
RQ 1: What aspects are focused on during the retrospective meeting?
RQ 2: How does reflection occur in the retrospective meeting?
Related Work
2.1 Agile Retrospective Meeting
There is a standard format commonly used to conduct an agile retrospective meeting which involves setting the stage, gathering data, generating insight, deciding what to do and closing the retrospective meeting []. Setting the stage involves welcoming and explaining the aim of the retrospective meeting. Gathering data involves agile teams sharing their review and feedback, reporting on what happened during the previous sprint and briefly discussing with other team members. In generating insight , agile teams participate in a further discussion and making agreements about what issues to focus on, and then on how to solve those issues and what areas that need to improve in the deciding what to do stage . Closing the retrospective involves summarizing the retrospective meeting and appreciating all team members efforts.
There are several recommendations for embedding reflective practice within standard agile practices as it is related to team performance improvement [].
Most of the existing research focuses on the techniques of performing a retrospective or identifying a broad classification of the type of reflection that occurs, e.g. reflection-on-action []. What actual topics or aspects are discussed during a retrospective and how reflection occurs, however, is not well understood. We build upon these works by investigating the retrospective meeting in depth.
2.2 Reflective Practice
Reflective practice according to Osterman and Kottkamp [], is defined as a means by which practitioners can develop a greater level of self - awareness about the nature and impact of their performance, an awareness that creates opportunities for professional growth and development.
Bain et al. [] classified reflection into five levels: reporting, responding, relating, reasoning and reconstructing. Level 1 and 2 are reporting and responding and enable learners to share brief descriptions of their experience, their feelings about events, facts or problems that they encountered. Level 3 is relating and involves connecting experience with personal meaning. Understanding at this level occurs when learners try to highlight good points (e.g. their ability, successful work) and negative points (e.g. mistakes, failure) to learn and identify areas of improvement. Level 4 is reasoning where learners explore the information shared as well as background knowledge related to the occurrences. Level 5 is reconstructing which signifies a high level of learning where learners generate the general framework of thinking, which is specified in a plan or action for responding to similar obstacles in the future.
Our study refers to levels of reflection proposed by Bain et al. [] and adjusts the levels into three main levels, i.e. reporting and responding, relating and reasoning and reconstructing , based on our observations of the agile retrospectives in practice. Reporting and responding are grouped together as the first level as these levels closely related to reviews sharing and discussions at the beginning of the retrospective meeting. Relating and responding are grouped as the second level as agile teams participate in a further discussion after they reported and responded to the reviews. The third level, the reconstructing level is embodied when agile teams discuss to formulate a plan as an improvement for the next sprint.
Research Method
The aim of this study is to investigate how reflection occurs in retrospective meetings. Understanding this is particularly important as agile teams are reported to focus more on their technical progress and tend to pay less attention to how reflection is performed thereby compromising their potential for improvement [].
This research is conducted by implementing the Case Study research method [. All interviews and observation data were collected by the first author in person. The raw data and emerging findings from the analysis were discussed in detail with the supervisory team (co-authors) who provided feedback and guidance.
Table 1.
Team and team members demographics (RMD: Retrospective meeting duration in minutes; P#: Individual participant number; FAP: first agile project)
Similar books «Agile processes in software engineering and extreme programming: 18th International Conference, XP 2017, Cologne, Germany, May 22-26, 2017, proceedings»
Look at similar books to Agile processes in software engineering and extreme programming: 18th International Conference, XP 2017, Cologne, Germany, May 22-26, 2017, proceedings. We have selected literature similar in name and meaning in the hope of providing readers with more options to find new, interesting, not yet read works.
Reviews about «Agile processes in software engineering and extreme programming: 18th International Conference, XP 2017, Cologne, Germany, May 22-26, 2017, proceedings»
Discussion, reviews of the book Agile processes in software engineering and extreme programming: 18th International Conference, XP 2017, Cologne, Germany, May 22-26, 2017, proceedings and just readers' own opinions. Leave your comments, write what you think about the work, its meaning or the main characters. Specify what exactly you liked and what you didn't like, and why you think so.
