Sep 2026· Zenodo (CERN European Organization for Nuclear Research)
Abstract
HIPPOGRID — evidence pack for the preliminary results (2026) Raw result files and figures behind the preliminary results cited in the MSCA-PF proposal HIPPOGRID (SEP-211387371, call HORIZON-MSCA-2026-PF-01). Researcher: Álvaro González-Redondo (University of Granada). Each bundle below backs one claim of the proposal; each result file is the unmodified output of the experiment that produced it, and the commit hash anchors it in the (currently private) research repository, scheduled for open release (Apache-2.0) with the corresponding papers. Numbers were produced with 10 random seeds and paired comparisons against non-degenerate null models unless stated otherwise. License: CC-BY 4.0. Contact: alvarogr@ugr.es Bundle Claim it backs (as in the proposal) Key files Commit B1_real_sensor_binding Image and posture written to one shared address are recovered from each other on a real robot's sensor stream (8,346 frames, 10 seeds); writing to a shuffled address destroys the binding asymmetrically while the memory stays intact `n562_real.json`, figure 5498007e B2_innate_template_binding A one-shot Hebbian binding anchors an innate grid-module set at 1.0–1.4 cells median under biological-level velocity noise (10/10 seeds; bounded at 3× that noise; shuffled-binding and shuffled-velocity nulls fail); the anchored map reproduces the signature of classic deformation experiments (partial rescaling; anisotropic field stretching, cf. Barry et al. 2007; merged-map seam, cf. Wernle et al. 2018) `n569_ancla*.json`, `n569_deformada.json`, `n569_defensa.json`, figures 0f20cb40 B3_rate_grid_recipe A purely local Hebbian/anti-Hebbian rule yields clean 2-D grid maps with no explicit normalisation: best-unit grid score 0.81 (torus) / 0.71 (walled box), medians over 10 seeds `n565_toro.json`, `n565_caja.json`, `n565_repro.json`, figure 2c6455c7 B4_place_stage_chain The chain closes from raw sensed input through a competitive place stage (grid score ≥ 0.4 in 9/10 seeds; direct input 0/20); small modules of distinct grid units at small grid-layer sizes; a stored-experience place stage performs like a trained one `n567_u4096_rejilla.json`, `n568_10semillas.json`, `n568_nulos.json`, `n568_redundancia.json` 0243e5b0 B5_blackboard_capacity With learned addresses the blackboard's capacity grows ~N/2 vs ~N^0.45 without learning (`n562_escalado.json`, keys `ley*`); the worst alias between two distant places falls from 0.995 to 0.093 at 4,096 cells (`n562_aprendido_dos_tablas.json`; N-dependent: 0.904 at 1,024 cells) `n562_escalado.json`, `n562_aprendido_dos_tablas.json` 16d3322e / 3a22657e B6_local_rule_ceiling A single-layer delta rule with a self-generated teacher ties the exact optimum of its family (+0.71 vs +0.70) and the non-negative constraint improves it (+0.82, 16/16) `n541_techo_exacto.json`, `n542_delta.json`, `n542_rectificada.json` d764a6fd Figures are included where the proposal reproduces them. JSON field names are in Spanish (the project's working language); each file is self-describing, with seeds and conditions as keys.
Software startups are newly created companies with no operating history and oriented towards producing cutting-edge products. However, despite the increasing importance of startups in the economy, few scientific studies attempt to address software engineering issues, especially for early-stage startups. If anything, startups need engineering practices of the same level or better than those of larger companies, as their time and resources are more scarce, and one failed project can put them out of business. In this study we aim to improve understanding of the software development strategies employed by startups. We performed this state-of-practice investigation using a grounded theory approach. We packaged the results in the Greenfield Startup Model (GSM), which explains the priority of startups to release the product as quickly as possible. This strategy allows startups to verify product and market fit, and to adjust the product trajectory according to early collected user feedback. The need to shorten time-to-market, by speeding up the development through low-precision engineering activities, is counterbalanced by the need to restructure the product before targeting further growth. The resulting implications of the GSM outline challenges and gaps, pointing out opportunities for future research to develop and validate engineering practices in the startup context.
Carmine Giardino, Nicolò Paternoster, M. Unterkalmsteiner et al.· IEEE Transactions on Softwar...· 179 citations· ⚡14
Software startup companies develop innovative, software-intensive products within limited timeframes and with few resources, searching for sustainable and scalable business models. Software startup ...
M. Unterkalmsteiner, P. Abrahamsson, Xiaofeng Wang et al.· e-Informatica Software Engin...· 157 citations· ⚡17
In the context of software startups, project failure is embraced actively and considered crucial to obtain validated learning that can lead to pivots. A pivot is the strategic change of a business concept, product or the different elements of a business model. A better understanding is needed on different types of pivots and different factors that lead to failures and trigger pivots, for software entrepreneurial teams to make better decisions under chaotic and unpredictable environment. Due to the nascent nature of the topic, the existing research and knowledge on the pivots of software startups are very limited. In this study, we aimed at identifying the major types of pivots that software startups make during their startup processes, and highlighting the factors that fail software projects and trigger pivots. To achieve this, we conducted a case survey study based on the secondary data of the major pivots happened in 49 software startups. 10 pivot types and 14 triggering factors were identified. The findings show that customer need pivot is the most common among all pivot types. Together with customer segment pivot, they are common market related pivots. The major product related pivots are zoom-in and technology pivots. Several new pivot types were identified, including market zoom-in, complete and side project pivots. Our study also demonstrates that negative customer reaction and flawed business model are the most common factors that trigger pivots in software startups. Our study extends the research knowledge on software startup pivot types and pivot triggering factors. Meanwhile it provides practical knowledge to software startups, which they can utilize to guide their effective decisions on pivoting.
Sohaib Shahid Bajwa, Xiaofeng Wang, Anh Nguyen-Duc et al.· Empirical Software Engineeri...· 127 citations· ⚡15
In the context of cloud computing, risks associated with underlying technologies, risks involving service models and outsourcing, and enterprise readiness have been recognized as potential barriers for the adoption. To accelerate cloud adoption, the concrete barriers negatively influencing the adoption decision need to be identified. Our study aims at understanding the impact of technical and security-related barriers on the organizational decision to adopt the cloud. We analyzed data collected through a web survey of 352 individuals working for enterprises consisting of decision makers as well as employees from other levels within an organization. The comparison of adopter and non-adopter sample reveals three potential adoption inhibitor, security, data privacy, and portability. The result from our logistic regression analysis confirms the criticality of the security concern, which results in an up to 26-fold increase in the non-adoption likelihood. Our study underlines the importance of the technical and security perspectives for research investigating the adoption of technology.
Nattakarn Phaphoom, Xiaofeng Wang, S. Samuel et al.· Journal of Systems and Softw...· 111 citations· ⚡8
To compete in this age of disruption, large companies cannot rely on cost efficiency, lead time reduction and quality improvement. They are now looking for ways to innovate like startups. Meanwhile, the awareness and use of the Lean startup approach have grown rapidly amongst the software startup community in recent years. This study investigates how Lean internal startup facilitates software product innovation in large companies and identifies its enablers and inhibitors. A multiple case study approach is followed in the investigation. Two software product innovation projects from two large companies are examined, using a conceptual framework that is based on the method-in-action framework and extended with the previously developed Lean-Internal Corporate Venture model. Seven face-to-face in-depth interviews of the employees with different roles are conducted. Within-case analysis and cross-case comparison are applied to draw the findings from the cases. A generic process flow summarises the common key processes of Lean internal startups. The findings suggest that an internal startup that is initiated management or employees faces different challenges. A list of enablers of applying Lean startup in large companies are identified, including top management support and cross-functional team. Both cases face different inhibitors due to the different process of inception, objective of the team and type of the product. Our contributions are threefold. First, this study is one of the first attempt to investigate the use of Lean startup approach in large companies empirically. Second, the study shows the potential of the method-in-action framework to investigate the Lean startup approach in non-startup context. The third is a general process of Lean internal startup and the evidence of the enablers and inhibitors of implementing it, which are both theory-informed and empirically grounded.
Henry Edison, Nina M. Smørsgård, Xiaofeng Wang et al.· Journal of Systems and Softw...· 78 citations· ⚡6
The application of agile software methods and more recently the integration of Lean practices contribute to the trend of continuous improvement in the software industry. One such area warranting proper empirical evidence is a project’s operational efficiency when using the Kanban method. This short paper takes a new angle and explores waste in the Kanban-driven software development project context. A preliminary research model is presented for helping the consequent replication of the study. The results from the empirical analysis suggest Kanban can be an effective method in visualizing and organizing the current work, but does not prevent waste from creeping in, although the overall project outcome may be successful.
Marko Ikonen, Petri Kettunen, Nilay V. Oza et al.· EUROMICRO Conference on Soft...· 67 citations· ⚡9