Objective: Circadian rhythms regulate essential cellular functions, yet their presence and entrainment in human umbilical cord-derived mesenchymal stem cells (hUC-MSCs) remain poorly defined.Methods: hUC-MSCs were cultured under 12-hour light/12-hour dark (light-dark [LD]) cycles or constant darkness (DD) for four days. Cell proliferation, senescence, and gene expression were assessed by Alamar Blue assay, senescence-associated β-galactosidase staining, fluorescence microscopy, and reverse transcription-quantitative polymerase chain reaction. Circadian rhythmicity was analyzed using Cosinor software. Dexamethasone (Dex; 100–500 nM, 2 hr) was applied to evaluate glucocorticoid-induced entrainment.Results: LD cycles were associated with increased cell proliferation and BMAL1 protein levels compared with DD conditions. Only PER3 showed evidence of rhythmic expression under LD exposure (Cosinor p<0.05), whereas other core clock genes did not show evidence of rhythmicity. Light exposure was not associated with a detectable increase in cellular senescence or changes in the expression of stemness markers (OCT4, SOX2, NANOG, C-MYC). Short-term Dex treatment (100–500 nM, 2 hr) did not markedly impair cell proliferation or migration. Notably, treatment with 500 nM Dex was associated with rhythmic BMAL1 mRNA expression over the 24-hour observation period, whereas CLOCK expression did not show evidence of rhythmicity.Conclusion: hUC-MSCs show partial and selective clock-gene responses to photoperiodic and glucocorticoid exposure. Moderate LD exposure was associated with increased proliferation and BMAL1 expression, while Dex was associated with rhythmic BMAL1 expression and was relatively well tolerated in hUC-MSCs under the conditions tested. These findings provide preliminary insight into how circadian rhythmicity may influence mesenchymal stem cells culture conditions.
This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.
P. Abrahamsson, O. Salo, Jussi Ronkainen et al.· arXiv.org· 727 citations· ⚡54
The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.
M. Pikkarainen, Jukka Haikara, O. Salo et al.· Empirical Software Engineeri...· 401 citations· ⚡48
The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.
Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al.· Information and Software Tec...· 394 citations· ⚡54
The results show that the embedded industry has been able to apply agile methods in its development processes and that the appreciation of the agile methods and their individual practices appears to increase once adopted and applied in practice.
O. Salo, P. Abrahamsson· IET Software· 238 citations· ⚡9
Consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts are found.
D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al.· Journal of Systems and Softw...· 236 citations· ⚡13
The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed, which helped develop an agile development approach for mobile application development.
P. Abrahamsson, Antti Hanhineva, H. Hulkko et al.· Conference on Object-Oriente...· 225 citations· ⚡18
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduOct 6, 2026
Writing as a participant and researcher, PhD student JS Tan SM ’22 has co-authored a new book about the rise of tech worker protests and the employer backlash that followed.
Requirements in large systems rarely exist in isolation. Their meaning depends on the wider project context - other requirements, policies, decisions, tests, and implementation details. That becomes especially important when AI is used for review, because spotting a possible conflict or gap is only the beginning. ReqSpace explores how AI, visualisation, and connected project context can help reviewers understand those findings, trace the relationships behind them, and focus on the questions that…
AI is making software generation faster, but speed does not remove the need for expertise. As more work is delegated to AI, tacit knowledge may become one of the most important human advantages in software engineering. The post Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering appeared first on GPT-Lab.
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.