Playing the Sprint Retrospective

Wawryk, Maciej; Ng, Yen Ying

doi:10.15439/2019f284

Cited by 7 publications

(4 citation statements)

References 17 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Przybyłek & Kotecka [22] adopted 5 retrospective games, which improved team members' creativity, involvement, and communication as well as produced better results than the standard retrospective. In our previous work [15,25], we confirmed their findings, while this paper complements and extends this research area.…”

Section: Introductionsupporting

confidence: 85%

“…We also concluded that the Sprint Retrospective should be fixed first. Accordingly, in the first cycle, we planed to implement all retrospective games that we used in our prior study [25] and in addition try a new game, namely Mountain Climbing. Besides, we decided to implement each game twice, first in non-anonymous and then in anonymous way.…”

Section: B Action Planningmentioning

confidence: 99%

“…We expect that anonymity will encourage participants to express their true feelings and critical thinking, which in turn will increase the quality and quantity of ideas generated [26]. Besides, we intend to replicate our previous studies [15,25] in which we adopted the "game-based retrospectives" approach initially introduced by Przybyłek & Kotecka [22]. [21] defined an extension to Open Kanban, which consists of 12 collaborative games to help novice Kanban practitioners to understand the Kanban principles.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Fun Retrospectives in Intel Technology Poland

Mich¹,

Ng²

2020

Proceedings of the 2020 Federated Conference on Computer Science and Information Systems

Self Cite

View full text Add to dashboard Cite

One of the Agile principles is that the team should regularly reflect on "how to become more effective, then tunes and adjusts its behavior accordingly". While the setup of a retrospective session is intuitive, in praxis, conducting successful retrospectives is challenging. This paper is a continuation of our previous work on the use collaborative games in addressing common retrospective problems. In addition to the replication of our previous action research in a new context, we aim to investigate whether preliminary anonymous idea generation mitigates negative social influences that have been identified as causes of poor performance of brainstorming. The obtained results confirms the previous findings that game-based retrospectives produces better results than the standard retrospective as well as improves participants' creativity, involvement, and communication. Our findings also suggest benefits to the preliminary anonymous idea generation.

show abstract

Section: Introductionsupporting

confidence: 85%

Section: B Action Planningmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Fun Retrospectives in Intel Technology Poland

Mich¹,

Ng²

2020

Proceedings of the 2020 Federated Conference on Computer Science and Information Systems

Self Cite

View full text Add to dashboard Cite

show abstract

“…The retrospective stage of an agile sprint is a critical component of the scrum methodology for creating, delivering and managing complex projects. Its goal is to identify the achievements and mistakes of the previous sprint and to connect the resulting experience to action suggestions for improvement [19].…”

Section: Scrummentioning

confidence: 99%

Hybrid agile development phases: the practice in software projects as performed by software engineering team

Yahya

Maidin²

2023

IJEECS

View full text Add to dashboard Cite

<span lang="EN-US">The combination of scrum and waterfall is one of the software engineering teams that preferred hybrid agile models. The purpose of combining the two models is to leverage the advantages of each also to tailor the hybrid agile model to the needs of the project. However, to what extent are the phases, stages, and features of scrum and waterfall implemented in a software project remains unclear. Additionally, which phase will employ scrum, and when will waterfall be deemed optimal is also the arising question. This research adopted a qualitative study, and interviews are used as a data collection instrument. The interview is conducted based on an interview protocol, and thematic analysis is utilized to extract the themes from the interviews. This study investigates how the scrum and waterfall models are utilized in a software project, and three themes were identified in answering the research question. The findings indicate five development phases in a hybrid agile project and that waterfall is the preferable model in planning, while development is on scrum, and project testing and deployment could be either waterfall or scrum.</span>

show abstract