Nils Brede Moe

Nils Brede Moe

Auto-generated profile, based on publicly available information

Nils Brede Moe

SINTEF

Research Focus & Metrics

Academic Career Length

26Years (2001-Present)

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

Representative Publications

View All Publications
1 June 2012 in Journal of Systems and Software
Verified
Journal Article
Open access
TDTorgeir Dingsøyr
Torgeir Dingsøyr
SNSridhar Nerur
Sridhar Nerur
VBVenuGopal Balijepally
VenuGopal Balijepally
NMNils Brede Moe
Nils Brede Moe
Ever since the agile manifesto was created in 2001, the research community has devoted a great deal of attention to agile software development. This article examines publications and citations to illustrate how the research on agile has progressed in the 10 years following the articulation of the manifesto. Specifically, we delineate the conceptual structure underlying agile scholarship by performing an analysis of authors who have made notable contributions to the field. Further, we summarize prior research and introduce contributions in this special issue on agile software development. We conclude by discussing directions for future research and urging agile researchers to embrace a theory-based approach in their scholarship.

1 May 2010 in Information and Software Technology
Verified
Journal Article
Closed access
NMNils Brede Moe
Nils Brede Moe
TDTorgeir Dingsøyr
Torgeir Dingsøyr
TDTore Dybå
Tore Dybå

2 June 2017 in Empirical Software Engineering
Verified
Journal Article
Open access
PDF file
TDTorgeir Dingsøyr
Torgeir Dingsøyr
NMNils Brede Moe
Nils Brede Moe
TFTor Erlend Fægri
Tor Erlend Fægri
ESEva Amdahl Seim
Eva Amdahl Seim
Agile development methods were believed to best suit small, co-located teams, but the success in small teams has inspired use in large and very large-scale software development. However, fundamental assumptions of agile development are challenged when applying the methods at a very large scale. An interpretative revelatory case study on one of the largest software development programmes in Norway shows how agile methods were adapted and complemented with practices from traditional methods to handle the scale. The programme ran over four years with 12 co-located development teams and a total of 175 people involved. The case study was conducted retrospectively using group interviews with 24 participants and documents. Findings on key challenging areas are reported: customer involvement, software architecture, and inter-team coordination. The revelatory study also suggests refinements of a research agenda for very large-scale agile development.

1 August 2012 in Information and Software Technology
Verified
Journal Article
Closed access
NMNils Brede Moe
Nils Brede Moe
AAAybüke Aurum
Aybüke Aurum
TDTore Dybå
Tore Dybå

9 September 2022 in Journal of Systems and Software
Verified
Journal Article
Open access
DŠDarja Šmite
Darja Šmite
NMNils Brede Moe
Nils Brede Moe
EKEriks Klotins
Eriks Klotins
JGJavier Gonzalez-Huerta
Javier Gonzalez-Huerta
The COVID-19 outbreak has admittedly caused interruptions to production, transportation, and mobility, therefore, having a significant impact on the global supply and demand chain’s well-functioning. But what happened to companies developing digital services, such as software? How has the enforced Working-From-Home (WFH) mode impacted their ability to deliver software, if at all? This article shares our findings from monitoring the WFH during 2020 in an international software company with engineers located in Sweden, the USA, and the UK. We analyzed different aspects of productivity, such as developer job satisfaction and well-being, activity, communication and collaboration, efficiency and flow based on the archives of commit data, calendar invites, Slack communication, the internal reports of WFH experiences, and 30 interviews carried out in April/May and September 2020. We add more objective evidence to the existing COVID-19 studies the vast majority of which are based on self-reported productivity from the early months of the pandemic. We find that engineers continue committing code and carrying out their daily duties, as their routines adjust to “the new norm”. Our key message is that software engineers can work from home and quickly adjust their tactical approaches to the changes of unprecedented scale. Further, WFH has its benefits, including better work-life balance, improved flow, and improved quality of distributed meetings and events. Yet, WFH is not challenge free: not everybody feels equally productive working from home, work hours for many increased, while physical activity, socialization, pairing and opportunities to connect to unfamiliar colleagues decreased. Information sharing and meeting patterns also changed. Finally, experiences gained during the pandemic will have a lasting impact on the future of the workplace. The results of an internal company-wide survey suggest that only 9% of engineers will return to work in the office full time. Our article concludes with the InterSoft’s strategy for work from anywhere (WFX), and a list of useful adjustments for a better WFH.

1 May 2008 in Software Process: Improvement and Practice
Verified
Journal Article
Closed access
PDF file
NMNils Brede Moe
Nils Brede Moe
DŠDarja Šmite
Darja Šmite