1. From zero to one: a new perspective on the fuzzy front end of innovation and the Stage-Gate® modelPeter Alešnik, Igor Vrečko, Iztok Palčič, 2025, original scientific article Abstract: The Stage-Gate® model has historically provided a systematic framework for New Product Development (NPD). However, the evolving landscape of innovation necessitates continuous enhancement. This paper redefines the model's foundational structure by advocating for the recognition of the Discovery Phase as Stage 1, emphasizing its essential role in aligning initial ideation with strategic goals, streamlining processes, and enhancing NPD efforts. Using a mixed-methods approach, including a systematic literature review, synthesis of illustrative examples and secondary data and case study analysis, the research demonstrates that formalizing the Discovery Phase improves earlystage decision-making, enhances alignment between front-end exploration and downstream execution and mitigates risks by supporting more informed project development. Synthesised sectoral examples show that incorporating the Discovery Phase improves feasibility, reduces risk, and boosts efficiency. For example, simulation planning early in innovation process increased manufacturing throughput by 52 %, while early IP checks lowered infringement risk. The proposed revision boosts the Stage-Gate® model's adaptability and integration with modern methodologies such as AI, Agile, Lean Startup, Design Thinking and TRIZ. The findings highlight how this change promotes a comprehensive approach to NPD. The implications extend to practical applications and future research, offering organizations a flexible framework that meets modern market and technological demands.
Keywords: Stage-Gate® model, fuzzy front end of innovation (FFEI), new product development (NPD), innovation management, discovery phase, agile, TRIZ, design thinking, large language model (LLM), sustainability
Published in DKUM: 03.11.2025; Views: 0; Downloads: 5
 Full text (641,93 KB)
This document has many files! More... |
2. From zero to one: a new perspective on the fuzzy front end of innovation and the Stage-Gate® modelPeter Alešnik, Igor Vrečko, Iztok Palčič, 2025, original scientific article Abstract: The Stage-Gate® model has historically provided a systematic framework for New Product Development (NPD). However, the evolving landscape of innovation necessitates continuous enhancement. This paper redefines the model's foundational structure by advocating for the recognition of the Discovery Phase as Stage 1, emphasizing its essential role in aligning initial ideation with strategic goals, streamlining processes, and enhancing NPD efforts. Using a mixed-methods approach, including a systematic literature review, synthesis of illustrative examples and secondary data and case study analysis, the research demonstrates that formalizing the Discovery Phase improves earlystage decision-making, enhances alignment between front-end exploration and downstream execution and mitigates risks by supporting more informed project development. Synthesised sectoral examples show that incorporating the Discovery Phase improves feasibility, reduces risk, and boosts efficiency. For example, simulation planning early in innovation process increased manufacturing throughput by 52 %, while early IP checks lowered infringement risk. The proposed revision boosts the Stage-Gate® model's adaptability and integration with modern methodologies such as AI, Agile, Lean Startup, Design Thinking and TRIZ. The findings highlight how this change promotes a comprehensive approach to NPD. The implications extend to practical applications and future research, offering organizations a flexible framework that meets modern market and technological demands.
Keywords: Stage-Gate® model, fuzzy front end of innovation (FFEI), new product development (NPD), innovation management, discovery phase, agile, TRIZ, design thinking, large language model (LLM), sustainability
Published in DKUM: 13.10.2025; Views: 0; Downloads: 6
Full text (641,93 KB) |
3. Can large-language models replace humans in agile effort estimation? Lessons from a controlled experimentLuka Pavlič, Vasilka Saklamaeva, Tina Beranič, 2024, original scientific article Abstract: Effort estimation is critical in software engineering to assess the resources needed for development tasks and to enable realistic commitments in agile iterations. This study investigates whether generative AI tools, which are transforming various aspects of software development, can improve effort estimation efficiency. A controlled experiment was conducted in which development teams upgraded an existing information system, with the experimental group using the generative-AI-based tool GitLab Duo for estimation and the control group using conventional methods (e.g., planning poker or analogy-based planning). Results show that while generative-AI-based estimation tools achieved only 16% accuracy—currently insufficient for industry standards—they offered valuable support for task breakdown and iteration planning. Participants noted that a combination of conventional methods and AI-based tools could offer enhanced accuracy and efficiency in future planning.
Keywords: software engineering, agile development, iteration planning, effort estination, generative AI, tool accuracy
Published in DKUM: 24.12.2024; Views: 0; Downloads: 20
Full text (1,29 MB) |
4. Agile Machine Learning Model Development Using Data Canyons in Medicine : A Step towards Explainable Artificial Intelligence and Flexible Expert-Based Model ImprovementBojan Žlahtič, Jernej Završnik, Helena Blažun Vošner, Peter Kokol, David Šuran, Tadej Završnik, 2023, original scientific article Abstract: Over the past few decades, machine learning has emerged as a valuable tool in the field of medicine, driven by the accumulation of vast amounts of medical data and the imperative to harness this data for the betterment of humanity. However, many of the prevailing machine learning algorithms in use today are characterized as black-box models, lacking transparency in their decision-making processes and are often devoid of clear visualization capabilities. The transparency of these machine learning models impedes medical experts from effectively leveraging them due to the high-stakes nature of their decisions. Consequently, the need for explainable artificial intelligence (XAI) that aims to address the demand for transparency in the decision-making mechanisms of black-box algorithms has arisen. Alternatively, employing white-box algorithms can empower medical experts by allowing them to contribute their knowledge to the decision-making process and obtain a clear and transparent output. This approach offers an opportunity to personalize machine learning models through an agile process. A novel white-box machine learning algorithm known as Data canyons was employed as a transparent and robust foundation for the proposed solution. By providing medical experts with a web framework where their expertise is transferred to a machine learning model and enabling the utilization of this process in an agile manner, a symbiotic relationship is fostered between the domains of medical expertise and machine learning. The flexibility to manipulate the output machine learning model and visually validate it, even without expertise in machine learning, establishes a crucial link between these two expert domains.
Keywords: XAI, explainable artificial intelligence, data canyons, machine learning, transparency, agile development, white-box model
Published in DKUM: 14.03.2024; Views: 299; Downloads: 41
Full text (5,28 MB)
This document has many files! More... |
5. Identifying key activities, artifacts and roles in agile engineering of secure software with hierarchical clusteringAnže Mihelič, Tomaž Hovelja, Simon Vrhovec, 2023, original scientific article Abstract: Different activities, artifacts, and roles can be found in the literature on the agile engineering of secure software (AESS). The purpose of this paper is to consolidate them and thus identify key activities, artifacts, and roles that can be employed in AESS. To gain initial sets of activities, artifacts, and roles, the literature was first extensively reviewed. Activities, artifacts, and roles were then cross-evaluated with similarity matrices. Finally, similarity matrices were converted into distance matrices, enabling the use of Ward’s hierarchical clustering method for consolidating activities, artifacts, and roles into clusters. Clusters of activities, artifacts, and roles were then named as key activities, artifacts, and roles. We identified seven key activities (i.e., security auditing, security analysis and testing, security training, security prioritization and monitoring, risk management, security planning and threat modeling; and security requirements engineering), five key artifacts (i.e., security requirement artifacts, security repositories, security reports, security tags, and security policies), and four key roles (i.e., security guru, security developer, penetration tester, and security team) in AESS. The identified key activities, artifacts, and roles can be used by software development teams to improve their software engineering processes in terms of software security.
Keywords: secure software development, security engineering, agile methods, agile development, software development, software engineering, software security, application security, cybersecurity, cyber resilience
Published in DKUM: 29.11.2023; Views: 417; Downloads: 14
Full text (557,17 KB)
This document has many files! More... |
6. Agile development of secure software for small and medium-sized enterprisesAnže Mihelič, Simon Vrhovec, Tomaž Hovelja, 2023, original scientific article Abstract: Although agile methods gained popularity and became globally widespread, developing secure software with agile methods remains a challenge. Method elements (i.e., roles, activities, and artifacts) that aim to increase software security on one hand can reduce the characteristic agility of agile methods on the other. The overall aim of this paper is to provide small- and medium-sized enterprises (SMEs) with the means to improve the sustainability of their software development process in terms of software security despite their limitations, such as low capacity and/or financial resources. Although software engineering literature offers various security elements, there is one key research gap that hinders the ability to provide such means. It remains unclear not only how much individual security elements contribute to software security but also how they impact the agility and costs of software development. To address the gap, we identified security elements found in the literature and evaluated them for their impact on software security, agility, and costs in an international study among practitioners. Finally, we developed a novel lightweight approach for evaluating agile methods from a security perspective. The developed approach can help SMEs to adapt their software development to their needs.
Keywords: secure software development, security engineering, agile, small and medium sized enterprises, software development management, security
Published in DKUM: 29.11.2023; Views: 494; Downloads: 9
Full text (2,58 MB)
This document has many files! More... |
7. Agile transformation : a case study on early stage of agile adoptionPeter Helmlinger, 2023, original scientific article Abstract: Agile transformation is identified as a facilitator to keep pace with frequent
changes within product development. Although initial research exists, the
empirical literature on the implementation process of the agile approach,
specifically using pilot projects as a change strategy, is scarce. The purpose
of this article is to contribute to closing this gap by investigating into effects
of piloting agile change projects. To shed light on agile pilots a project within
the context of mechatronic system development in the high-tech industry was
accompanied over six months. After the initiation of the members and a period
of practicing agile a survey was performed. The interviewed team members are
bringing up interesting findings, as although they had a different understanding
of agile at the beginning of the pilot, they recognized agile values, principles
and methods as supportive to the products cycle and specifically development
time. Further findings are indicating that professional third-party support is
a key success factor. Also piloting, as a change strategy for agile adoption, is
proven to be supportive. Although piloting is proven a supportive strategy,
the downsides, such as limited scalability caused by extraordinary setups, are
identified and analyzed. The limiting factor of this single-case study is the
small sample size of data due to the intention of the pilot project to limit
impact and risk on the organization.
Keywords: agile product development, organizational transformation, agile adoption, pilot project, case study
Published in DKUM: 01.09.2023; Views: 37468; Downloads: 58
Full text (796,35 KB)
This document has many files! More... |
8. Advantages and disadvantages of agile approach in software development : diplomsko deloDoroteja Minjovič, 2019, undergraduate thesis Abstract: The thesis touches on the agile manifesto, followed by a description of Scrum, where Roles, Ceremonies, Artifacts, and Sprints are described. In addition to Scrum, the thesis describes Extreme Programming, Kanban, and Lean. The last part of the chapter contains an analysis of the pros and cons of agile methods in software development. The thesis concludes with a review of survey results.
Keywords: Agile methods, Software development, Scrum
Published in DKUM: 21.11.2019; Views: 4991; Downloads: 359
Full text (803,77 KB) |
9. Teaching Scrum in cooperation with a software development companyViljan Mahnič, Strahil Georgiev, Tomo Jarc, 2010, original scientific article Abstract: The increasing use of agile methods for software development creates the need for these methods to become part of the education of future computer and information science engineers. On the other hand, teaching these methods gives us an opportunity to verify individual agile concepts and their effectiveness. For that reason, project work is an appropriate and frequently used form of teaching that enables students to get acquainted with agile methods and, at the same time, provides case studies for evaluating individual agile concepts. We describe our approach to teaching the Scrum agile method, within the software technology course, in cooperation with a software development company. Students were taught through work on a real project for which a list of requirements was submitted by the company. A co-worker of this company participated throughout the teaching period playing the role of customer's representative. During their work, students consistently used the Scrum method and at the end of each iteration they evaluated their experience by means of a questionnaire. In the article, the Scrum method is presented first, then a description of work on the project is given and finally the results of the survey are described.
Keywords: agile methods, Scrum, software development, computer engineering education, university industry cooperation
Published in DKUM: 22.01.2018; Views: 1245; Downloads: 427
Full text (974,55 KB)
This document has many files! More... |
10. Usage of agile SCRUM methodology on configuration management applicationŽeljko Stanojević, 2017, master's thesis/paper Abstract: The purpose of the master thesis is to research and determine how to successfully manage a project using agile methodology Scrum. Scrum methodology will be used to improve the functionality of existing internally developed software solutions.
Scrum, being an agile methodology, is an alternative approach to the traditional waterfall methodology, and is typically used in software development. Agile methodologies help teams respond to a project’s unpredictability by using incremental, iterative way of work known as sprints.
The first part of the master’s thesis presents a problem, defines goals and methods used, and the necessary tools required to achieve the objectives.
The following part of the thesis presents the foundations of agile methodologies and describes the used methodology – Scrum - in detail.
In the practical part, the thesis presents the existing software solution and opportunities for its improvement. We use Scrum for upgrading existing application, including all the attributes of the mentioned methodology, from team design to artifacts and events.
The thesis also presents a renewed application in detail. In conclusion, by using the SWOT analysis we observe suitability for use of the Scrum methodology in the case of renewal of application and propose further changes to improve the application.
Keywords: Project Management, Software Development, Agile Project Management, Scrum Implementation, Agile Methodologies
Published in DKUM: 28.06.2017; Views: 1612; Downloads: 147
Full text (3,43 MB) |
