Anastasiia Tkalich

Anastasiia Tkalich

Auto-generated profile, based on publicly available information

Anastasiia Tkalich

SINTEF Trondheim Norway

Research Focus & Metrics

Academic Career Length

6Years (2021-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications
27 December 2021 in Journal of Systems and Software
Verified
Journal Article
Open access
DSDarja Smite
Darja Smite
ATAnastasiia Tkalich
Anastasiia Tkalich
NMNils Brede Moe
Nils Brede Moe
EPEfi Papatheocharous
Efi Papatheocharous
EKEriks Klotins
Eriks Klotins
MBMarte Pettersen Buvik
Marte Pettersen Buvik
The COVID-19 pandemic triggered a natural experiment of an unprecedented scale as companies closed their offices and sent employees to work from home. Many managers were concerned that their engineers would not be able to work effectively from home, or lack the motivation to do so, and that they would lose control and not even notice when things go wrong. As many companies announced their post-COVID permanent remote-work or hybrid home/office policies, the question of what can be expected from software engineers who work from home becomes more and more relevant. To understand the nature of home telework we analyze the evidence of perceived changes in productivity comparing office work before the pandemic with the work from home during the pandemic from thirteen empirical surveys of practitioners. We analyzed data from six corporate surveys conducted in four Scandinavian companies combined with the results of seven published surveys studying the perceived changes in productivity in industrial settings. In addition, we sought explanations for the variation in perceived productivity among the engineers from the studied companies through the qualitative analysis of open-ended questions and interviews. Combined results of 7686 data points suggest that though on average perceived productivity has not changed significantly, there are developers who report being more productive, and developers being less productive when working from home. Positively affected individuals in some surveys form large groups of respondents (up to 50%) and mention benefiting from a better organization of work, increased flexibility and focus. Yet, there are equally large groups of negatively affected respondents (up to 51%) who complain about the challenges related to remote teamwork and collaboration, as well as emotional issues, distractions and poor home office environment and equipment. Finally, positive trends are found in longitudinal surveys, i.e., developers’ productivity in the later months of the pandemic show better results than those in the earlier months. We conclude that behind the average “no change” lays a large variation of experiences, which means that the work from home might not be for everyone. Yet, a longitudinal analysis of the surveys is encouraging, as it shows that the more pessimistic results might be influenced by the initial experiences of an unprecedented crisis. At the end, we put forward the lessons learned during the pandemic that can inspire the new post-pandemic work policies.

9 December 2022 in IEEE Software
Verified
Journal Article
Open access
ATAnastasiia Tkalich
Anastasiia Tkalich
DŠDarja Šmite
Darja Šmite
NANina Haugland Andersen
Nina Haugland Andersen
NMNils Brede Moe
Nils Brede Moe
We explore how Norwegian software developers experienced remote work under the pandemic and after restrictions were waved and describe simple behaviors and attitudes related to psychological safety. We find flexible work to offer a trade-off between being able to stay focused and as a team being able to maintain psychological safety.

7 March 2025 in Empirical Software Engineering
Verified
Journal Article
Open access
PDF file
ATAnastasiia Tkalich
Anastasiia Tkalich
EKEriks Klotins
Eriks Klotins
TSTor Sporsem
Tor Sporsem
VSViktoria Stray
Viktoria Stray
NMNils Brede Moe
Nils Brede Moe
ABAstri Barbala
Astri Barbala
Context: Organizations opt for continuous delivery of incremental updates to deal with uncertainty and minimize waste. However, applying continuous engineering (CSE) practices requires a continuous feedback loop with input from customers and end-users. Challenges: It becomes increasingly challenging to apply traditional requirements elicitation and validation techniques with ever-shrinking software delivery cycles. At the same time, frequent deliveries generate an abundance of usage data and telemetry informing engineering teams of end-user behavior. The literature describing how practitioners work with user feedback in CSE, is limited. Objectives: We aim to explore the state of practice related to utilization of user feedback in CSE. Specifically, what practices are used, how, and the shortcomings of these practices. Method: We conduct a qualitative survey and report analysis from 21 interviews in 13 product development companies. We apply thematic and cross-case analysis to interpret the data. Results: Based on our earlier work we suggest a conceptual model of how user feedback is utilized in CSE. We further report the identified challenges with the continuous collection and analysis of user feedback and identify implications for practice. Conclusions: Companies use a combination of qualitative and quantitative methods to infer end-user preferences. At the same time, continuous collection, analysis, interpretation, and use of data in decisions are problematic. The challenges pertain to selecting the right metrics and analysis techniques, resource allocation, and difficulties in accessing vaguely defined user groups. Our advice to practitioners in CSE is to ensure sufficient resources and effort for interpretation of the feedback, which can be facilitated by telemetry dashboards.

9 June 2022
Verified
Book Chapter
Open access
PDF file
ATAnastasiia Tkalich
Anastasiia Tkalich
RURasmus Ulfsnes
Rasmus Ulfsnes
NMNils Brede Moe
Nils Brede Moe
The product manager (PM) role is well established in leading technological companies, such as Google, Amazon, Microsoft, and Facebook. PMs are responsible for integrating technical, design, and business perspectives when developing software products and product portfolios. In agile methods (e.g., Scrum), similar responsibilities are linked to the Product Owner (PO) role. In contrast, in large-scale agile, one can find both Product Owners and product managers who sometimes compete. Despite the widespread adoption of the product manager role, the attention toward it in the agile academic community has been surprisingly limited. In this multiple case study, we analyzed 17 interviews with 11 product managers from four agile companies. We found that the PMs facilitated continuous product experimentation and innovation, supported the product teams, and engaged in additional activities to achieve optimal product development. Our summary of the product management activities can guide product managers working in agile companies.

14 November 2022
Verified
Book Chapter
Closed access
PDF file
DŠDarja Šmite
Darja Šmite
NMNils Brede Moe
Nils Brede Moe
ATAnastasiia Tkalich
Anastasiia Tkalich
GHGeir Kjetil Hanssen
Geir Kjetil Hanssen
KNKristina Nydal
Kristina Nydal
MHMalin Holte
Malin Holte