Experiential team learning in software startups

Khanna, Dron

doi:10.1145/3234152.3314992

Cited by 6 publications

(5 citation statements)

References 17 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Retrospectives originated from the Latin word "retrospectare" meaning looking back in the past to the thoughts. Retrospectives occur on experiences with tentative dates or periods to trace back the event [6]. A common retrospective practice is called "Agile retrospectives" [6].…”

Section: Literature Reviewmentioning

confidence: 99%

See 1 more Smart Citation

The Know-How of Agile Retrospectives in Software Startups

Khanna,

Wang

2023

Agile Processes in Software Engineering and Extreme Programming – Workshops

Self Cite

View full text Add to dashboard Cite

Software startups are responsible for fast product delivery to the market. To aid this process, a retrospective inside a startup team can be very fruitful for software development. The traditional way of conducting agile retrospectives involves discussion based on what went well, what did not go well, and how to improve the software development cycle helps to save resources, get directed toward the startup vision, and overcome several challenges. To attain insights about the agile retrospective approach in startups, we studied the following question: How are software startups performing agile retrospectives? Hence, we conducted seven multiple case studies with 19 semi-structured interviews that lasted 30–65 min. The results outline that all software startups prefer a reflection through agile retrospectives but not in the traditional manner. Due to the startup’s casual and less restricted working environment, teams prefer informal agile retrospectives, which involve no confined boundaries of time, venue, and participants.

show abstract

Section: Literature Reviewmentioning

confidence: 99%

“…Retrospectives occur on experiences with tentative dates or periods to trace back the event [6]. A common retrospective practice is called "Agile retrospectives" [6]. Agile retrospectives come under the roof of agile methods such as programming, daily stand-up meeting, and short iteration.…”

Section: Literature Reviewmentioning

confidence: 99%

The Know-How of Agile Retrospectives in Software Startups

Khanna,

Wang

2023

Agile Processes in Software Engineering and Extreme Programming – Workshops

Self Cite

View full text Add to dashboard Cite

show abstract

“…O artigo de Dron Khanna (2018) informa que a Retrospectiva habilita o reuso do conhecimento que melhora a performance de projetos na organização, no sentido em que ela é uma "oportunidade para os desenvolvedores entenderem melhor o processo de desenvolvimento de software" (KHANNA, 2018). Este resultado se alinha com a definição utilizada aqui de lições aprendidas.…”

Section: Análise Dos Resultadosunclassified

“…Encerrando a revisão individual dos artigos, o estudo de Yanti Andriyani (2017) traz como resultado relevante para a pesquisa o entendimento dos três tipos de conhecimento utilizados em engenharia de software (projeto, processo e produto), dos quais se podem derivar lições aprendidas. Em um outro aspecto, este artigo também cita o PIW e PMA como práticas utilizadas para conduzir Retrospectivas, confirmando o resultado discutido em (KHANNA, 2018). O conhecimento adquirido com a leitura destes textos levou à inclusão de outras referências na seleção, a saber: os estudos de Salo et al (2004) e Dingsøyr e Hanssen (2003) que detalham, respectivamente, como as práticas de Post-Iteration Workshop e Lightweight Postmortem Analysis foram concebidas como modelos de Retrospectiva.…”

Section: Análise Dos Resultadosunclassified

“…Esse conhecimento é fundamental para a melhoria futura do projeto, no sentido em que a medição objetiva destes artefatos, como ação de retrospectivas, são um caminho para quantificar os resultados das melhorias propostas (Matthies, 2020). Khanna (2018) esclarece que o Post Iteration Workshop (PIW) é uma das técnicas populares para a condução de retrospectivas. Os idealizadores do PIW reconhecem terem simplificado a análise de causa raiz, como está documentado no trabalho de Salo et al (2004): "...uma técnica de análise de causa raiz chamada diagrama Ishikawa, para análise de causas subjacentes, [...], foi considerada, porém não incluída".…”

Section: Ii) Não Inspecionar Os Artefatos Gerados Durante a Sprintunclassified

See 1 more Smart Citation

A Proposal for Reusing Lessons Learned in Scrum Projects

Lima¹,

Gava²

19th CONTECSI International Conference on Information Systems and Technology Management

View full text Add to dashboard Cite

Research reveals that a considerable number of IT projects fail to meet their schedule and/or cost estimates. One of the reasons for this low success rate is that organizations are unable to reuse lessons learned in projects or are doing so in an incomplete or inefficient way. The goal of this study is to build a process for estimulating the reuse of lessons learned in Scrum projects. A systematic literature review is performed, which reveals the most popular techiniques used for conducting Retrospectives have flaws that inhibit the learning process. By reintroducing techniques that will mitigate these flaws, a process is presented with the expected outcome of enabling the reuse of lessons learned during the project and, as a result, to help the team to avoid past mistakes and distribute knowledge in a more homogeneous way among team members.

show abstract

From MVPs to Pivots: A Hypothesis-Driven Journey of Two Software Startups

Khanna

Nguyen-Duc

2018

Lecture Notes in Business Information Processing

Self Cite

View full text Add to dashboard Cite

Software startups have emerged as an interesting multiper-spective research area. Inspired by Lean Startup, a startup journey can be viewed as a series of experiments that validate a set of business hy-potheses an entrepreneurial team make explicitly or inexplicitly about their startup. It is little known about how startups evolve through busi-ness hypothesis testing. This study proposes a novel approach to look at the startup evolution as a Minimum Viable Product(MVP) creat-ing process. We identified relationships among business hypotheses and MVPs via ethnography and post-mortem analysis in two software star-tups. We observe that the relationship between hypotheses and MVPs is incomplete and non-linear in these two startups. We also find that entrepreneurs do learn from testing their hypotheses. However, there are hypotheses not tested by MVPs and vice versa, MVPs not related to any business hypothesis. The approach we proposed visualizes the flow of entrepreneurial knowledge across pivots via MVPs.

show abstract

Experiential team learning in software startups

Cited by 6 publications

References 17 publications

The Know-How of Agile Retrospectives in Software Startups

The Know-How of Agile Retrospectives in Software Startups

A Proposal for Reusing Lessons Learned in Scrum Projects

From MVPs to Pivots: A Hypothesis-Driven Journey of Two Software Startups

Contact Info

Product

Resources

About