Antecedents and Consequences of Time Pressure in Scrum Projects: Insights from a Qualitative Study

Linßen, Stefan; Basten, Dirk; Richter, Janek

doi:10.24251/hicss.2018.608

Cited by 3 publications

(4 citation statements)

References 20 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Furthermore, the participants attributed limited time availability to Agile practices. A study by Linß et al found ten antecedents to, and five consequences of time pressure, by analysing time pressure in software projects that apply Scrum [37]. It is evidence that time pressure is intrinsic to the agile development method -scrum.…”

Section: Classification Of Antecedentsmentioning

confidence: 99%

“…According to our results, ambiguous and incomplete requirements promote a disconfirmatory behaviour, however, under time pressure this leads to a confirmatory behaviour manifestation. More studies are needed on how to improve the requirement specifications that may deteriorate software quality especially in the context of Agile that also constraints time [37]. Yet, the manifestation of confirmation bias in the case of complete requirements is not detrimental for software quality because a tester is then validating all the specified required and not required behaviours of the SUT [3].…”

Section: Implications For Research and Practicementioning

confidence: 99%

See 1 more Smart Citation

What Leads to a Confirmatory or Disconfirmatory Behavior of Software Testers?

Salman

Rodríguez

Turhan

et al. 2022

IIEEE Trans. Software Eng.

View full text Add to dashboard Cite

Background: The existing literature in software engineering reports adverse effects of confirmation bias on software testing. Confirmation bias among software testers leads to confirmatory behaviour, which is designing or executing relatively more specification consistent test cases (confirmatory behaviour) than specification inconsistent test cases (disconfirmatory behaviour). Objective: We aim to explore the antecedents to confirmatory and disconfirmatory behaviour of software testers. Furthermore, we aim to understand why and how those antecedents lead to (dis)confirmatory behaviour. Method: We follow grounded theory method for the analyses of the data collected through semi-structured interviews with twelve software testers. Results: We identified twenty antecedents to (dis)confirmatory behaviour, and classified them in nine categories. Experience and Time are the two major categories. Experience is a disconfirmatory category, which also determines which behaviour (confirmatory or disconfirmatory) occurs first among software testers, as an effect of other antecedents. Time Pressure is a confirmatory antecedent of the Time category. It also contributes to the confirmatory effects of antecedents of other categories. Conclusion: The disconfirmatory antecedents, especially that belong to the testing process, e.g., test suite reviews by project team members, may help circumvent the deleterious effects of confirmation bias in software testing. If a team's resources permit, the designing and execution of a test suite could be divided among the test team members, as different perspectives of testers may help to detect more errors. The results of our study are based on a single context where dedicated testing teams focus on higher levels of testing. The study's scope does not account for the testing performed by developers. Future work includes exploring other contexts to extend our results.

show abstract

Section: Classification Of Antecedentsmentioning

confidence: 99%

Section: Implications For Research and Practicementioning

confidence: 99%

What Leads to a Confirmatory or Disconfirmatory Behavior of Software Testers?

Salman

Rodríguez

Turhan

et al. 2022

IIEEE Trans. Software Eng.

View full text Add to dashboard Cite

show abstract

“…There are multiple reasons that create (negative) time pressure in software projects. For example, budget constraints, bottlenecks due to functional dependencies, inadequate time estimations, change of requirements during sprints (agile development method), dependencies on external suppliers, and technical uncertainties are the usual grounds for time pressure [42], [43], [44]. Another factor that constrains the development schedule is the competition in the global market [43].…”

Section: Introductionmentioning

confidence: 99%

Confirmation Bias and Time Pressure: A Family of Experiments in Software Testing

Salman,

Turhan,

Ramač

et al. 2023

IIEEE Trans. Software Eng.

View full text Add to dashboard Cite

Background: Software testers manifest confirmation bias (the cognitive tendency) when they design relatively more specification consistent test cases than specification inconsistent test cases. Time pressure may influence confirmation bias of testers per the research in the psychology discipline. Objective: We examine the manifestation of confirmation bias of software testers while designing functional test cases, and the effect of time pressure on confirmation bias in the same context. Method: We executed one internal and two external experimental replications concerning the original experimentation in Oulu. We analyse individual replications and meta-analyse our family of experiments (the original and replications) for joint results on the phenomena. Results: Our findings indicate a significant manifestation of confirmation bias by software testers during the designing of functional test cases. Time pressure significantly promoted confirmation bias among testers per the joint results of the family. The different experimental sites affected the results; however, we did not detect any effects of site-specific variables. Conclusion: Software testers should develop an outside-of-the-box thinking attitude to counter the manifestation of confirmation bias. Time pressure can be manoeuvred by centring manual suites on the designing and consequently the execution of inconsistent test cases, while automated testing focuses on consistent ones.

show abstract

“…Controlled experiments in the lab have investigated the impact of sleep deprivation [17], emotional arousal induced by time pressure [38] and emotional states of dominance and valence [18]. Quantitative [46] and qualitative studies [34] have showed the impact of time pressure on the field. Studies on mining software repositories have made several recent attempts to build tools and reason about the emotional states of software developers by utilizing sentiment analysis [23,24,33,37,47].…”

Section: Introductionmentioning

confidence: 99%

Using experience sampling to link software repositories with emotions and work well-being

Kuutila

Mäntylä

Claes

et al. 2018

Proceedings of the 12th ACM/IEEE International Symposium on Empirical Software Engineering and Measurement

View full text Add to dashboard Cite

Background: The experience sampling method studies everyday experiences of humans in natural environments. In psychology it has been used to study the relationships between work wellbeing and productivity. To our best knowledge, daily experience sampling has not been previously used in software engineering. Aims: Our aim is to identify links between software developers self-reported affective states and work well-being and measures obtained from software repositories. Method: We perform an experience sampling study in a software company for a period of eight months, we use logistic regression to link the well-being measures with development activities, i.e. number of commits and chat messages. Results: We find several significant relationships between questionnaire variables and software repository variables. To our surprise relationship between hurry and number of commits is negative, meaning more perceived hurry is linked with a smaller number of commits. We also find a negative relationship between social interaction and hindered work well-being. Conclusions: The negative link between commits and hurry is counter-intuitive and goes against previous lab-experiments in software engineering that show increased efficiency under time pressure. Overall, our work is an initial step in using experience sampling in software engineering and validating theories on work well-being from other fields in the domain of software engineering.

show abstract

Antecedents and Consequences of Time Pressure in Scrum Projects: Insights from a Qualitative Study

Cited by 3 publications

References 20 publications

What Leads to a Confirmatory or Disconfirmatory Behavior of Software Testers?

What Leads to a Confirmatory or Disconfirmatory Behavior of Software Testers?

Confirmation Bias and Time Pressure: A Family of Experiments in Software Testing

Using experience sampling to link software repositories with emotions and work well-being

Contact Info

Product

Resources

About