Agile Software Process Improvement

With more and more digital videos found online, video retrieval researchers have begun to create various representations or surrogates for digital videos, such as poster frames, storyboards, video skims and fast forwards. How to evaluate the effectiveness of these video surrogates has become an issue for researchers. This paper proposes two general classes of user tasks-recognition tasks and tasks requiring inference-for which performance measures were developed. The measures include graphical object recognition, textual object recognition, action recognition, free-text gist d e t e r m i n a t i o n , m u l t i p l e -c h o i c e g i s t determination and visual gist determination. The preliminary results from two user studies applying these six measures are also discussed in this paper.

In this paper, we describe the challenges of assessing human performance during video retrieval episodes and describe several measures of human performance that have been used in developing visual surrogates for the Open Video Digital Library (). These include two sets of cognitive performance measures that aim to assess human recognition and inference and a set of attitudinal measures that aim to assess user satisfaction with video surrogates.

Agile methodology have transformed IT project management by providing a flexible and adaptive framework to address the dynamic nature of software development. The influence of agile approaches was evaluated by this study, particularly Scrum, and the corresponding effect on successful IT projects deliveries. The study employed a structural literature review and thematic analysis to identify key success determinants. Research findings shows that agile strategies markedly enhance project efficiency, adaptability, and customer satisfaction in contrast to conventional methods such as the Waterfall methodology. The research indicates that essential success variables are cross-functional team competence, iterative development, and proactive stakeholder engagement. Nevertheless, obstacles remain, especially in implementing agile methodologies across extensive, dispersed teams and tailoring them to varied business cultures. A comparative analysis employing the Iron Triangle concept underscores Agile's enhanced efficacy in managing time, cost, and quality restrictions, though its efficiency fluctuates across diverse project circumstances. The implementation of a structural literature review guarantees a thorough synthesis of previous research, whereas theme analysis discerns repeating patterns and interconnections among main components. This research provides academic and practical insights, elucidating Agile's role in contemporary IT project management and assisting practitioners in harnessing its potential for project success.

Agile coaching plays an important role in successfully adopting Scrum and overcoming challenges associated with its implementation. Agile coaches support teams by providing resources, tools, and frameworks that allow them to solve problems independently and make data-driven decisions. This article reviews the effectiveness of Agile coaching, discusses the Scrum and Agile adoption challenges, outlines best practices for successful Scrum adoption, and examines the problems Organizations face when implementing Scrum. Scrum has been the most widely adopted Agile methodology over the past decade. While Scrum plays an important role in the success of Agile development, it does come with challenges. A custom model that was transformed from the Diffusion of Innovation theoretical model was developed to detect the Scrum adoption challenges referred to as the Scrum Adoption Challenges Detection Model (SACDM). This model consists of four constructs: i) Individual factors, ii) Team factors, iii) Organizational factors, and iv) Technology factors. Agile has become a hot topic among stakeholders over the last few years. Out of many agile methodologies, Scrum has become at the top of the list as a framework.

Agile programming emphasizes adaptability, iteration, and collaboration in software development. With the rise of quantum computing, new paradigms of probabilistic and hybrid computation challenge conventional Agile workflows. This paper proposes the W-Lambda framework, a waveform calculus that unifies Agile iteration cycles, quantum uncertainty, and reflexivity in organizational systems. Furthermore, we introduce resilience as conceptualized by Professor Levi, modeling the system's capacity to absorb disturbances, adapt dynamically, and recover efficiently. We also draw an analogy between Agile iteration and multi-timeframe stock chart analysis, demonstrating how drilling down from coarse-grained to fine-grained resolutions mirrors iterative software development, feedback, and risk mitigation. Philosophical perspectives (Sun Tzu, Popper, Soros) provide additional conceptual support.

Agile programming emphasizes adaptability, iteration, and collaboration in software development. With the rise of quantum computing, new paradigms of probabilistic and hybrid computation challenge conventional Agile workflows. This paper proposes the W-Lambda framework, a waveform calculus that unifies Agile iteration cycles, quantum uncertainty, and reflexivity in organizational systems. By integrating philosophical perspectives (Sun Tzu, Popper, Soros) with mathematical models of quantum algorithms and W-Lambda dynamics, we argue for a new vision of software development as a waveform process that adapts, oscillates, and converges toward value creation.

Software as a Service (SaaS) has transformed the software industry, offering scalable, accessible, and affordable solutions to companies globally. This study investigates advanced strategies and agile approaches that promote excellence in SaaS product creation. We analyze existing methods, evolving frameworks, and industry case studies to demonstrate how businesses can utilize cutting-edge techniques to deliver high-quality SaaS solutions. The report identifies customer-centric development, microservices architecture, data-driven decision-making, and continuous integration and deployment as essential for SaaS success. Our research shows that companies embracing hybrid agile and DevOps methodologies significantly enhance customer satisfaction and product quality.

As machine learning (ML) systems spread worldwide, a troubling question emerges: Who is held accountable when things go wrong? Laws meant to govern data privacy and AI accountability vary drastically-what's required in Europe under the General Data Protection Regulation (GDPR) differs sharply from rules in California (CCPA) or more lenient regions. These mismatched regulations create real challenges for developers, companies, and regulators trying to ensure fairness, transparency, and responsibility in AI systems.

Since its inception in 2001, the Agile Manifesto has transformed software development and project management by championing individuals, collaboration, and adaptability over rigid processes. Frameworks like Scrum and Kanban have become standard, with teams worldwide engaging in stand-ups, sprints, and retrospectives. Yet, a growing concern has emerged: the rise of "zombie Agile," where teams mechanically perform Agile rituals without embodying the principles of trust, reflection, and continuous improvement. This disconnect between the "how" and "why" of Agile signals a need to reinvigorate its philosophical core.

This paper introduces Aligile, a novel framework that infuses Agile with a deeper sense of purpose by drawing on the ethical wisdom of Imam Ali, a revered figure in Islamic scholarship. Inspired by Ali’s six-stage journey of meaningful faith—Submission (Taslīm), Conviction (Yaqīn), Verification (Tasdīq), Acknowledgment (Iqrār), Fulfillment (Adāʾ), and Action (ʿAmal)—Aligile reimagines Agile as an inner journey of character and integrity. It is not a new methodology but a philosophical lens that aligns Agile practices with universal values, fostering teams that are not only efficient but also principled. By bridging modern Agile principles with a 1,400-year-old ethical framework, Aligile offers a cross-disciplinary approach to enhance management theory and practice, addressing the human elements often overlooked in contemporary Agile implementations. This work sparks a dialogue on how diverse wisdom traditions can enrich organizational agility, urging practitioners to cultivate both productive and soulful teams.

This paper compares and contrasts the practices in developing application software for the Internet in 2000 and 2002. We identify key organizational and technical factors that facilitated or impeded implementation of Internet applications. The identification is done through a grounded theory analysis of data collected from ten companies. A comparison of the 2000 and 2002 data shows how major factors, such as market environment and lack of experience emerged to change the software process and the attitude toward 12 • J. Pries-Heje, R. Baskerville, L. Levine & B. Ramesh quality. The comparative study shows how the interrelationship between the core factors of speed and quality, together with the other major factors, unfolded in a decision process wrought with trade-offs and balancing decisions at multiple levels in the software organization. These trade-offs and balancing decisions -a high speed balancing game -are taking place at three different levels: the market, the portfolio, and the project. Balancing game theory extends existing theories about software development trade-off decisions, providing new insights into how such trade-off decisions are translated into software practices. The paper includes a comparative analysis of the findings from 2000 and 2002.

In traditional projects the project manager has the difficult task of ensuring that the solution developed is exactly the one requested (desired) by the customer. To this end, the project manager will manage everything related to the project in a coherent manner: scope, costs, quality, people, communication, risk, procurement etc. Often, part of these responsibilities belong to other organizational functions. Project scope, for example, is a typical customer responsibility. Who else would be able to make decisions about priorities, timing and market changes? Defining priorities, for example, is not a static activity, a decision to be made once and for all at the beginning of the project. Yet project managers are asked to make plausible hypotheses (estimates and related plans) to create the right product.

On the surface, this Scrum activity appears to be simple and straightforward. But be careful. Without good preparation, this session may be ineffective and create disagreements among participants. The presenter shows the participants what was completed during the release (Sprint). Simple, right? Well, based on experience, a Sprint Review is rarely simple. In practice, it is the most delicate session for a facilitator. The greatest difficulty is to keep the expectations of a heterogeneous group of people (various stakeholders) aligned who are generally not very familiar with the development group (Scrum Team). These people often have more seniority in the company than the team and are certainly less familiar with the typical problems of projects. Without wishing to generalize, they often have a poor ability to pay attention to other people's problems.

The Agile Scrum approach defines three events to controlling the software development process and checking the progress of activities vs the plan, to evaluating and deciding what to release, and to improving the development process. The three events-Daily Scrum, Sprint Review, and Sprint Retrospective-have limited duration and are managed with Time-boxing technique. The events are managed by the Scrum Master and see the participation of the Scrum Team (Development Team), the Process Owner and other stakeholders directly affected by the issue. Each event is managed using specific techniques suggested by Scrum best practices whose effectiveness has been consolidated over the years.

At present, there are wide ranges of reference models that are available to improve the way to develop and manage the software development in an organization, e.g. there are models to improve quality management, such as ISO 9001, for Software Quality Management there is ISO 90003, to improve the capacity of models there are CMMI and ISO 12207, for the IT Governance, there are ITIL, PMBOK and COBIT, Information Security Management Systems such as 27000 and Bodies of Knowledge such as SWEBOK, amongst others. However, the heterogeneity of the models available, together with the need to solve problems from many dimensions and organizational hierarchies, means that organizations face problems in improvement process projects which have to deal with different models at the same time. In this article, a systematic review is presented of works, initiatives and projects published and carried out on the harmonization of multi-model environments. Another objective stemming from the above is to ...

Performing process improvement to deliver qualified products with the expected cost on time has been a requirement for organizations targeting to be successful in the software market. Software organizations usually perform process improvement based on well-known process assessment frameworks such as CMMI and ISO/IEC 15504. A number of derivatives of CMMI and ISO/IEC 15504 have been developed and they are being updated. As a result of this, the software process assessment tool based on them needs to be updated. Process assessment requires judgment and there is an unavoidable manual work. However, there are also opportunities for assessment automation. Therefore, there is a need for a generic software process assessment tool to define process assessment models and facilitate assessment. The existing tools do not meet the expected features of a software process assessment tool completely, as they have generally been developed for single process assessment models. In this study, we present GSPA, a generic software process assessment tool, which has been developed to support all structured process assessment models with its generic framework, facilitate assessment, support parallel assessment and present the reports in a well-structured way to the assessors. A multiple case study has been conducted to measure the sufficiency and the contributions of the tool.

The traditional strategies were chaotic nature of software development, it may be impossible to control or to predict and which did not give the company many chances to integrate all the latest changes effectively. This raised a need for a light weight and flexible methodology to overcome the basic issues in traditional methodologies. So the Agile Methodology was born that aims to overcome the problems faced in traditional development/testing methodologies and also to easily maneuver software activities in today’s complex Business activities using light weight practices and adaptability.

Software Project Management and IT Project Management in general, deals with a variety of problems and difficulties resulting in time and budget overrun. During the last decades a number of methodologies have been introduced, starting from the waterfall model up to the today’s more flexible, referred to as Agile Methods, aiming at the efficient and effective IT project management. This paper aims to describe shortly the evolutionary steps and the reasons beyond the appearance of these methods, as well to identify the preconditions and the limitations for their acceptance, intending to examine the possibilities for the adoption of the Agile Methods in the Greek IT market. Despite of the factors that influence the adoption of Agile methodologies in Greece, the extent of usage and familiarity with these methods (by presenting the results of a relevant survey conducted by the University of Macedonia), is also examined.

A widely recognized fact is that the quality of software products is largely determined by the quality of the process used to develop them. Regardless of the number of tools/frameworks developed to aid companies to perform software process assessment (SPA) and improvement (SPI) activities, the industry often suffers with quality issues in their products. In order to evaluate the SPA and SPI research areas, a systematic mapping was performed to identify the available tools/frameworks and methodologies used in research, as well as the existing gaps in the area. As a result it was possible to identify the current trends in the SPA and SPI research areas that can be used as a guideline to future work and can contribute to the software engineering and quality community.

Abstract—Artificial Intelligence (AI) is transforming project management by automating routine tasks, enhancing decision-making, and improving efficiency. This paper explores how AI influences project planning, risk management, automation, decision-making, collaboration, and adaptive learning. It also examines challenges such as data privacy, workforce adaptation, and ethical concerns. The paper concludes that AI is an invaluable tool for project managers and organizations looking to optimize performance in an increasingly digital world.paper concludes that AI is an invaluable tool for project managers and organizations looking to optimize performance in an increasingly digital world.

Gamification is the concept of applying game elements in non-game context platforms to motivate people to participate in planned activities to achieve goals. As more and more VCCST are formed in recent years, many issues have been raised in those teams stemming from miscommunication and cultural conflicts. This paper uses the EGS to help resolve the issues in VCCST. Also, this paper is an extension of a previous paper written by the same authors in this similar topic.

Gamification is the concept of applying game elements in non-game context platforms to motivate people to participate in planned activities to achieve goals. As more and more VCCST are formed in recent years, many issues have been raised in those teams stemming from miscommunication and cultural conflicts. This paper uses the EGS to help resolve the issues in VCCST. Also, this paper is an extension of a previous paper written by the same authors in this similar topic.

O CMMI é referência mundial para a qualidade de software. Contudo, tem sido pouco adotado por pequenas empresas de desenvolvimento, devido principalmente às restrições de pessoal, ao custo com a implementação e manutenção do processo, além da demora no retorno do capital investido. Este artigo propõe uma alternativa para implantação dos processos da engenharia de requisitos presentes no CMMI, aliados ao planejamento estratégico. Esta alternativa possibilitaria uma eventual observação demelhorias em curto espaço de tempo, talvez, motivando a definição incremental dos processos do modelo, inclusive por pequenas empresas. Para subsidiar empiricamente as reflexões propostas, são apresentados dados iniciais de um estudo de caso realizado.

How to cite this article: Sedghkerdar M.H., Taghikhani V., Ghotbi C., Shariati A., A modified UNIFAC model in predicting the solubility of CO2 and H2 S in imidazolium-based ionic liquids. Journal of Oil, Gas and Petrochemical Technology, 2020; 7(1): 1-13. DOI: 10.22034/JOGPT.2020.113091. In this work, a modified UNIFAC model was proposed to investigate the solubility of acid gases, i.e., CO2 and H2S in nine imidazolium-based ionic liquids (ILs). The influence of effective parameters including temperature, the nature of anions and cations of the ILs, and the length of alkyl chain on the solubility of acid gases in the ILs were studied. The interaction parameters between the new functional subgroups of the fragmented ILs such as [IM], [BF4], [PF6], [Tf2N], CH3 and CH2 with CO2 and H2S molecules were reported using the original UNIFAC model. In the proposed model, the segment fraction in the Flory-Huggins term of the UNIFAC combinatorial part was modified considering the free-volume di...

Gut arbeitende Teams sind essentiell für wirksame Resultate. Das gilt selbstverständlich auch bei der menschzentrierten Gestaltung, besonders im Rahmen agiler Entwicklung. Im angloamerikanischen Diskurs taucht oft der Slogan "design is a team sport" auf, um auf die Notwendigkeit von Teamwork für Human-Centred Design hinzuweisen. Ob nun Affinitätsdiagramme, Personas oder Journey Mapping zur Modellierung von Ist-Zuständen eingesetzt werden, oder Szenarien, Storyboards oder User Story Mapping für Soll-Zustände, immer muss ein Team ein gemeinsames Verständnis von Problemräumen und Lösungswegen herstellen. Warum gelingt das einigen Teams mit Leichtigkeit und anderen nicht? Es gibt Hinweise darauf, dass "psychologische Sicherheit" den Unterschied macht. Ist sie das Fundament gelingender Teamarbeit und ein Erfolgsgeheimnis agiler Arbeitsweisen? Wir präsentieren dazu Forschungu. a. aus dem Hause Googleund beleuchten das theoretische Konzept aus unterschiedlichen Perspektiven. 1 Einleitung "Agil ist heute Standard. IT-Unternehmen, die im Jahr 2018 gar keine agilen Methoden einsetzen, gibt es praktisch nicht mehr." Mit diesem Statement kündigt Bastians Wilhelms seine Keynote für die Manage Agile im Oktober in Berlin an. "Doch wieso gibt es so wenige Unternehmen, in denen agile Arbeitsweisen auf allen Ebenen, in der gesamten Organisation, eingesetzt werden? Wieso nur in diesem einem Projekt, in diesem einen Team, warum nur in der IT-Abteilung?" Seine Antworten passen zum Thema der Konferenz: "Die meisten Organisationen legen zu viel Wert auf Konsens. Das macht sie langsam. Viele müssen erst lernen, die Koexistenz unterschiedlicher Konzepte und Meinungen innerhalb eines Unternehmens zu

L'articolo analizza le citazioni di Tibullo nel corpus leopardiano, che si concentrano in modo particolare nel Saggio sopra gli errori popolari degli antichi (22 occorrenze sulle 34 totali). Tale squilibrio si spiega con la natura stessa del Saggio, che, come scrive l’autore nella Prefazione, nasce dal «rimescolar molti libri e consultar molti vecchi autori». Tutti i brani tibulliani – che Leopardi comunque ricontrolla nelle sue due edizioni di riferimento – sono infatti estrapolati da fonti intermedie (le dissertazioni di Calmet e Carli, le note erudite della Basvilliana di Monti, i lessici di Pitisco e Hofmann), mediante complessi percorsi testuali di volta in volta ricostruiti in questo contributo. È così che il caso di Tibullo, il quale non lascerà altre tracce durature (se non tematiche) nella produzione leopardiana, appare emblematico del modus operandi del giovane autore del Saggio e offre un utile specimen delle molte fonti “rimescolate” da Giacomo, qui riportate alla luce attraverso il metodo filologico messo a fuoco nell’ambito del progetto prin 2020 Leopardi and the Ancients: a Digital Archive.

The interplay between language and space offers profound insights into the conceptualization and interpretation of religious and cultural phenomena. This collection investigates the spatial dynamics of the Great Mosque of Rome as a case study within a multidisciplinary framework. It examines the mosque’s architectural, social, and symbolic dimensions, highlighting its dual role as a monumental representation of Islamic identity and as a locus of urban religious plurality. Integrating historical, sociological, and ethnographic methodologies, the analysis emphasizes the contrast between the mosque's grandeur and the informal sacred spaces in peripheral urban areas. This study underscores the transformative power of spatial and religious dialogues in urban settings, offering new perspectives on the intersection of space, identity, and culture. The collaborative approach of the SHAring Religious Places (ShaRP) project enriches the discourse, demonstrating the utility of integrating digital humanities with traditional academic inquiries.

Un'attenzione particolare è riservata alla lettera-curriculum, senza data, di Leopardi a Pepoli, per la quale vengono forniti ulteriori elementi, interni ed esterni, che contribuiscono anche a una sua più corretta datazione. La riflessione si soπerma pure sul libro dei Versi e sulla sua carsica storia editoriale, accresciuta di nuovi dati e considerazioni. Viene proposta, inoltre, una piccola appendice documentaria per completare il corpus di lettere e biglietti scambiati tra Leopardi e Pepoli. In chiusura, tre approfondimenti trasversali: il primo s'interroga sul rapporto tra i due letterati (con uno sguardo ai Canti), il secondo discute l'importanza di Vincenzo Monti, dedicatario comune di Leopardi e Pepoli, il terzo scioglie il dubbio dell'influsso del Tasso leopardiano sulla Prigione di Tasso di Pepoli.

At present, the issue of abortion is creating a polarity in many societies; the USA is a prime example, where the ‘progressive’ left is in a continual battle against the conservative right-wing party. The opinion presented here is that in their articles, scientists are not supposed to become involved in
doing ‘propaganda’ for one position or the other but should look at issues like the Social Construct of Reality Theory and abortion, from a new perspective based on the cutting edge of scientific thinking and research that is both interdisciplinary and, where necessary, includes ancient spiritual wisdom; it is wholistic. A multidisciplinary approach that draws from multiple fields allows for a more comprehensive understanding of complex issues. Thus, this scientific stance presented here can be considered ‘evolutionary within the tapestry of human evolution’. Scientists must also remember that
science, in essence, is creative and was once considered philosophy and was taught in tandem with the creative arts, including music; from a systemic point of view, all these disciplines are part of a whole, where the whole is greater than the sum of the parts. The holistic approach does not provide nice, tidy answers regarding right and wrong. However, going beyond binary thinking opens dilemmas, creating new unthought-of ways to contemplate issues, which enables policymakers and the public to make more informed decisions backed by scientific evidence and research.

Context: Agile software development aims to
achieve higher software delivery speed, as well as greater
flexibility during the software development process, and
is focused on the value of products and satisfied
users.Aim: This paper aims to find a unique definition of
maturity in the agile software development, as well as to
compile models for measuring maturity in order to
determine their advantages and disadvantages.Method:
In the first part of the paper, a systematic literature
review was carried out in order to gain insight into the
current state, followed by a comparative analysis of the
model for measuring maturity in the agile software
development.Result: 27 relevant studies were identified.
Based on the analysis of the results, the definition of
maturity in the agile software development is proposed
and criteria for determining the level of maturity in the
presented models are determined.Conclusion: The paper
contributes to knowledge about software development by
providing an overview of existing literature in this field,
creating a foundation for analysis of the maturity
measuring model in the agile software development and
identifying the advantages and disadvantages of these
models, which can enable IT companies to select the
model in accordance with their needs.

Die Arbeitskultur ist das unsichtbare Band, das Betriebe zusammenhält, deren Reputation und Attraktivität beeinflusst, sie in Krisen rettet oder in Krisen zu stürzen vermag. Die Arbeitskultur stand lange nicht im Vordergrund der betrieblichen Diskussionen. Oftmals verhindert ein aktueller Krisenmodus, ein traditionelles Strukturdenken, die Sorge vor grundlegenden Hinterfragungen, mangelnde Zeit oder die Fokussierung auf die x-te Strategie eine profunde Diskussion über die Arbeitskultur. Und doch ist die Arbeitskultur immer da. Unterschiedlich in ihrer Ausprägung und mal besser, mal schlechter von den Mitarbeitenden beurteilt. Sie ist aber mehr als nur ein Zustand, eine Randerscheinung: Sie prägt die Diskussionen zwischen Mitarbeitenden, sie setzt Themen, sie beeinflusst, wie gearbeitet, wie kommuniziert wird, wie Führungsentscheide getroffen werden und vor welchem Bedeutungshintergrund sie interpretiert werden. Sie beeinflusst das "Wie" im betrieblichen Alltag, das Klima im Betrieb, die Codes und Praxen, die schon zu Selbstverständlichkeiten geworden sind. Sie hat damit einen großen Einfluss auf Haltung, Professionalität, Zusammenarbeitsbereitschaft, schließlich darauf, ob bestehende Strukturen wirksam werden und ob eine gewählte Strategie erfolgreich wird. Die durchdachtesten Strukturen und die besten Strategien können an einer realen Kulturdifferenz scheitern: "Culture eats strategy for breakfast": Der Peter Drucker zugesprochene Ausspruch besagt, dass zwar Kultur nicht alles, doch ohne eine gute Kultur vieles nichts ist. Lassen Sie uns also über die Arbeitskultur reden. Gehen wir von der Grundprämisse aus, dass der Mensch gerne, und gerne gut arbeitet, so ist es nicht nur das "Was", sondern auch das "Wie", das ihn prägt. Viele Menschen suchen ein harmonisches Beziehungsgeflecht zu ihrem Umfeld, wollen eigene Fertigkeiten kultivieren, wollen in einem kollektiven Bewusstsein beheimatet sein und streben nach einer Kultur, die ihnen hilft, betriebliche Ereignisse anhand kulturell akzeptierter Werte und Normen zu interpretieren. Das alles sind unterschiedliche Funktionen der Arbeitskultur, auf die wir in diesem Buch eingehen wollen. Mitarbeitende wollen nicht nur einer Zweckrationalität ihrer Aufgabe oder ihres Betriebes folgen, sie wollen Sinn und kulturelle Anschlussfähigkeit finden. Doch sie wollen sich auch nicht von plumpen Kultur-Geboten vereinnahmen lassen. Vorwort VII zu widmen. Ihre wertvollen Beiträge, Erfahrungsberichte und Impulse waren strukturbildend und inspirierend für die vorliegende Publikation. Ein zusätzlicher Dank geht an die Fachpersonen in unserem Review Board, welche uns bei der Beurteilung und der Auswahl der Textbeiträge im "double-blind-Verfahren" unterstützt haben. Schließlich danken wir noch jenen, welche organisierend oder redigierend die Komplexität eines Ausschreibeverfahrens für Textbeiträge, die Koordination aller Einzelarbeiten und schließlich das kritische Gegenlesen unterstützt haben. Es sind dies in alphabetischer Reihenfolge Alexandra Bernhardt, Samanta Riklin, Manuela Ruf und Claudia Züger. Ihnen allen sagen wir herzlich Danke. Nun wünschen wir Ihnen ein gutes Quantum Zeit, nicht nur zum Lesen der diversen Textbeiträge, sondern auch für die Reflexion, was das Thema der Arbeitskultur in ihrem (Arbeits-)Leben und ihrer betrieblichen Funktion verändern mag. Wir wünschen Ihnen eine inspirierende Lektüre. Sebastian Wörwag und Alexandra Cloots c Aus Gründen der Lesbarkeit verwenden wir in diesem Buch überwiegend das generische Maskulinum. Dies impliziert beide Formen, schließt also das weibliche Geschlecht mit ein.

Die Arbeitskultur ist das unsichtbare Band, das Betriebe zusammenhält, deren Reputation und Attraktivität beeinflusst, sie in Krisen rettet oder in Krisen zu stürzen vermag. Die Arbeitskultur stand lange nicht im Vordergrund der betrieblichen Diskussionen. Oftmals verhindert ein aktueller Krisenmodus, ein traditionelles Strukturdenken, die Sorge vor grundlegenden Hinterfragungen, mangelnde Zeit oder die Fokussierung auf die x-te Strategie eine profunde Diskussion über die Arbeitskultur. Und doch ist die Arbeitskultur immer da. Unterschiedlich in ihrer Ausprägung und mal besser, mal schlechter von den Mitarbeitenden beurteilt. Sie ist aber mehr als nur ein Zustand, eine Randerscheinung: Sie prägt die Diskussionen zwischen Mitarbeitenden, sie setzt Themen, sie beeinflusst, wie gearbeitet, wie kommuniziert wird, wie Führungsentscheide getroffen werden und vor welchem Bedeutungshintergrund sie interpretiert werden. Sie beeinflusst das "Wie" im betrieblichen Alltag, das Klima im Betrieb, die Codes und Praxen, die schon zu Selbstverständlichkeiten geworden sind. Sie hat damit einen großen Einfluss auf Haltung, Professionalität, Zusammenarbeitsbereitschaft, schließlich darauf, ob bestehende Strukturen wirksam werden und ob eine gewählte Strategie erfolgreich wird. Die durchdachtesten Strukturen und die besten Strategien können an einer realen Kulturdifferenz scheitern: "Culture eats strategy for breakfast": Der Peter Drucker zugesprochene Ausspruch besagt, dass zwar Kultur nicht alles, doch ohne eine gute Kultur vieles nichts ist. Lassen Sie uns also über die Arbeitskultur reden. Gehen wir von der Grundprämisse aus, dass der Mensch gerne, und gerne gut arbeitet, so ist es nicht nur das "Was", sondern auch das "Wie", das ihn prägt. Viele Menschen suchen ein harmonisches Beziehungsgeflecht zu ihrem Umfeld, wollen eigene Fertigkeiten kultivieren, wollen in einem kollektiven Bewusstsein beheimatet sein und streben nach einer Kultur, die ihnen hilft, betriebliche Ereignisse anhand kulturell akzeptierter Werte und Normen zu interpretieren. Das alles sind unterschiedliche Funktionen der Arbeitskultur, auf die wir in diesem Buch eingehen wollen. Mitarbeitende wollen nicht nur einer Zweckrationalität ihrer Aufgabe oder ihres Betriebes folgen, sie wollen Sinn und kulturelle Anschlussfähigkeit finden. Doch sie wollen sich auch nicht von plumpen Kultur-Geboten vereinnahmen lassen. Vorwort VII zu widmen. Ihre wertvollen Beiträge, Erfahrungsberichte und Impulse waren strukturbildend und inspirierend für die vorliegende Publikation. Ein zusätzlicher Dank geht an die Fachpersonen in unserem Review Board, welche uns bei der Beurteilung und der Auswahl der Textbeiträge im "double-blind-Verfahren" unterstützt haben. Schließlich danken wir noch jenen, welche organisierend oder redigierend die Komplexität eines Ausschreibeverfahrens für Textbeiträge, die Koordination aller Einzelarbeiten und schließlich das kritische Gegenlesen unterstützt haben. Es sind dies in alphabetischer Reihenfolge Alexandra Bernhardt, Samanta Riklin, Manuela Ruf und Claudia Züger. Ihnen allen sagen wir herzlich Danke. Nun wünschen wir Ihnen ein gutes Quantum Zeit, nicht nur zum Lesen der diversen Textbeiträge, sondern auch für die Reflexion, was das Thema der Arbeitskultur in ihrem (Arbeits-)Leben und ihrer betrieblichen Funktion verändern mag. Wir wünschen Ihnen eine inspirierende Lektüre. Sebastian Wörwag und Alexandra Cloots c Aus Gründen der Lesbarkeit verwenden wir in diesem Buch überwiegend das generische Maskulinum. Dies impliziert beide Formen, schließt also das weibliche Geschlecht mit ein.

The publications of research papers are increasing exponentially and to find the relevant paper to a research area or according a user query is crucial task. It is due to the large corpus of text data in different formats. If a user query on search engine to read a research paper, it will provide him a bundle of papers, now to find the relevancy of the paper; user will read one by one each paper. There are some techniques already exist as TF*IDF with many variations and content match search cited by and co-citation. Document ranking and the vector space model is nearest to our system. In this paper, we used a new approach for recommender system , it examine identify paper section then assign weights to each section , applying Paper section weights to determine what documents are more relevant to a user query. When papers retrieved then rank it on the basis of section weights. each paper ha four main sections are Paper Title, Abstract, Keywords, Introduction and Conclusion. In online...

Internet of things (IoT) is an important part of a new generation of technology that every object no matter things or human could be connected to Internet. There are many wireless protocols such as IEEE 802.11 Series, 802.15 Series and Zigbee for communication between devices. However, considering a lot of small devices are unable to communicate efficiently with constrained resources, Internet Engineering Task Force (IETF) has developed a lightweight protocol: Constrained Application Protocol (CoAP). In CoAP, the notion of “notifications ” is introduced. A client can request a server that it wants to get notified when the value changes. The server then makes a note of the client request (if it supports observation). From there on, when a value changes at server side, it notifies all registered clients. Keyword: -Constrained Environment, IoT, Resource Observation, Request -Response Model .

Agile Methoden sind seit einigen Jahren in der Softwareentwicklung etabliert und erfahren vor dem Hintergrund digitaler Transformationsprojekte aktuell eine sehr hohe Aufmerksamkeit. Gleichzeitig erscheinen der Zusammenhang zwischen dem gewählten Agilitätsgrad eines Softwareentwicklungsprojekts und seinem Erfolg sowie die moderierende Rolle der Unternehmenskultur weitestgehend ungeklärt. An dieser Stelle setzt unsere Forschung an, indem sie die Erfolgswirkung von Agilität in Softwareprojekten quantitativ-empirisch untersucht und dabei die spezifische Kultur des jeweiligen Unternehmens berücksichtigt. Hierzu wurden mit Hilfe eines Fragebogens insgesamt 108 verwertbare Antworten von IT-Projektmitarbeitern gesammelt und mit dem Ansatz Partial Least Squares in einer Mehrgruppenanalyse statistisch ausgewertet. Die Ergebnisse zeigen, dass einerseits ein höherer Agilitätsgrad zu einem höheren Projekterfolg führt, diese Wirkung andererseits aber von der Unternehmenskultur beeinflusst wird. Entsprechend erweitern unsere Forschungsergebnisse die Wissensbasis in diesem Bereich und liefern wertvolle Erkenntnisse für die Praxis der Softwareentwicklung.

Agile Methoden sind seit einigen Jahren in der Softwareentwicklung etabliert und erfahren vor dem Hintergrund digitaler Transformationsprojekte aktuell eine sehr hohe Aufmerksamkeit. Gleichzeitig erscheinen der Zusammenhang zwischen dem gewählten Agilitätsgrad eines Softwareentwicklungsprojekts und seinem Erfolg sowie die moderierende Rolle der Unternehmenskultur weitestgehend ungeklärt. An dieser Stelle setzt unsere Forschung an, indem sie die Erfolgswirkung von Agilität in Softwareprojekten quantitativ-empirisch untersucht und dabei die spezifische Kultur des jeweiligen Unternehmens berücksichtigt. Hierzu wurden mit Hilfe eines Fragebogens insgesamt 108 verwertbare Antworten von IT-Projektmitarbeitern gesammelt und mit dem Ansatz Partial Least Squares in einer Mehrgruppenanalyse statistisch ausgewertet. Die Ergebnisse zeigen, dass einerseits ein höherer Agilitätsgrad zu einem höheren Projekterfolg führt, diese Wirkung andererseits aber von der Unternehmenskultur beeinflusst wird. ...

National Registrations Document Management System is an efficient, time saving and easy way to view and control the version of a citizen's registrations file. It is now an easy task and managing it is much easier. This research project focuses on the development of a computerized and web-based Document Management System for the Department of National Registration, Passport and Citizenship, Ministry of Home Affairs. The topic was selected due to the handicaps of the existing system of document management in the department. This new system has been designed to eliminate the delay, loss, insecurity and immobility of the existing system. The methodology used in the analysis of the new system is Object Oriented Analysis and Design (OOAD). The new system was implemented using PHP serverside scripting language for the front end and MySQL as the database management system for storing information obtained from the front end. The result is a web-based application that can efficiently store documents, provide document security, retrieve documents when needed and can be accessed at anywhere and on any device supporting internet applications I.

Soon, the integration of Generative AI into the software development life cycle will revolutionize how applications are imagined, developed, tested, and deployed. This paper will discuss how the software development life cycle can be automated using Generative AI and improve on the areas that involve code generation, testing, and deployment. Here, methodologies such as artificial intelligence take over the process, minimizing the impact of manual work and increasing accuracy and speed. The generative AI's capability to write superior quality code and perform testing and deployment activities helps the development teams reduce development time frames. It is likely to yield better and more reliable software products. This approach is a stark revolution in software engineering as it provides a smooth, selective, and intelligent execution process from the design stage to implementation.

Agile techniques have transformed project management and software development by stressing flexibility, collaboration, and customer-centricity. Data warehouse initiatives have traditionally used a waterfall methodology, which may delay, cost more, and misalign with business needs. Agile techniques are applied to data warehouse projects in this article, examining their pros and cons. The study starts with Agile fundamentals including iterative development, incremental delivery, and adaptive planning. It compares these concepts with the linear, sequential waterfall approach employed in data warehousing. Agile approaches like Scrum or Kanban may help data warehouse projects adapt to changing business demands and improve results. The report recommends creating cross-functional Agile teams with data administration, analytical, and development competence to execute Agile in data warehouses. Collaborative teams encourage communication and feedback loops. Sprints, stand-ups, and retrospectives help data warehousing teams make quick changes and meet business goals, according to the report. Integrating Agile techniques with structured and complicated data warehouse projects is a major problem. The study tackles data governance, quality assurance, and data architectural issues. It suggests using Agilefriendly technologies and methods to improve data management and governance in an Agile framework. Agile data warehouse project success stories are also examined in the study. The case studies demonstrate the advantages of enhanced flexibility, decreased time-to-market, and stakeholder satisfaction. They also

Este artigo apresenta uma abordagem para Melhoria de Processo de Software, definida através da simplificação e adaptação do DMAIC, tendo como foco principal a melhoria baseada na medição dos processos. A abordagem visa trabalhar os processos prioritários para a organização e relevantes para os clientes, utilizando ciclos de melhoria menores, com intuito de obter resultados rápidos e significativos.

Aim/Purpose. This exploratory study seeks to surface a richer understanding regarding the direct experience of software developers (SDs) working in sprints as part of the adoption of agile methodology principles. Background. The software development industry is increasingly adopting agile development methods. In the agile methodology, the delivery cycle is broken down into sprints, also known as iterations. There is relatively little empirical knowledge produced to date on agile software development methods. Specifically, the SDs’ authentic work experience in agile sprints is a subject that is missing from the literature. Methodology. This paper presents results based on data collected through preliminary in-depth interviews with SDs working in research and development teams of Israeli high-tech companies. As a heuristic device for describing their experience, an interpretive phenomenological perspective was adopted. Content analysis was used as a central methodology to analyze the data. Findings. The preliminary results present the ways of managing a development project in sprints, put a spotlight on the value of the agile method, and provide a unique glimpse of its challenges. Contribution. Our work adds to the growing body of research investigating the SDs’ perceptions. The preliminary results develop the theoretical and practical knowledge related to managing agile sprints, with reference to optimal communication, monitoring, control, and knowledge sharing among SDs in agile projects.

Internet of things (IoT) is an important part of a new generation of technology that every object no matter things or human could be connected to Internet. There are many wireless protocols such as IEEE 802.11 Series, 802.15 Series and Zigbee for communication between devices. However, considering a lot of small devices are unable to communicate efficiently with constrained resources, Internet Engineering Task Force (IETF) has developed a lightweight protocol: Constrained Application Protocol (CoAP). In CoAP, the notion of “notifications ” is introduced. A client can request a server that it wants to get notified when the value changes. The server then makes a note of the client request (if it supports observation). From there on, when a value changes at server side, it notifies all registered clients. Keyword: -Constrained Environment, IoT, Resource Observation, Request -Response Model .

Öz Yazılım Geliştirme Metodolojileri, farklı ürün yapılarına ve farklı çalışma ortamlarına uygun olarak, yazılım geliştirme ekiplerinin performanslarının arttırılması ve geliştirilen yazılım üzerinde daha etkin bakım adımları yürütülmesini sağlamak amacıyla hazırlanan süreçlerdir. Bu süreçlerin tanımlanması ve uygulanmasında, başarısı kanıtlanmış süreçlerin kullanılması tercih edilse de, çoğu zaman ekiplerin kendilerine özgü durumları bu süreçlerin başarılı sonuçlar elde etmesini imkansız hale getirir. Bu nedenle hem yazılım geliştirme ekibinin çalışma performansını yükseltecek, hem de gerçekçi bir süreç oluşturulması önemli bir fayda sağlayacaktır. Hazırlanan çalışma ile yazılım geliştirme ekiplerinin adım adım gelişimini sağlayacak ve uygulanabilirliği yüksek bir gelişimsel metodoloji açıklanmaktadır.

Code smells represent code decay and as such should be eradicated from a system to prevent future maintenance problems. A range of twenty smells described by Fowler and Beck each require varying numbers and combinations of refactorings in order to be eradicated-but exactly how many are needed when we consider related, nested refactorings is unclear. In this paper, we enumerate these refactorings when categorised according to Mantyla's smell taxonomy. We then show how, ironically, the 'smelliest' of smells (and hence most difficult to eradicate) are actually those best understood by developers. So, code smells are not only unpleasant to have around, but are deceptive in their nature and make-up. The study is thus a warning against attempting to eradicate what are seemingly easily eradicated smells-these are often the smells the developer needs to be most wary of. Finally, we incorporate the answers to six questions suggested by Paul for 'How to write a paper properly' to position the paper in a reflective way.

Code smells reflect code decay, and, as such, developers should seek to eradicate such smells through application of “deodorant” in the form of one or more refactorings. However, a relative lack of studies exploring code smells either theoretically or empirically when compared with literature on refactoring suggests that there are reasons why smell eradication is neither being applied in anger, nor the subject of significant research. In this paper, we present three studies as supporting evidence for this stance. The first is an analysis of a set of five, open-source Java systems in which we show very little tendency for smells to be eradicated by developers; the second is an empirical study of a subsystem of a proprietary, C# web-based application where practical problems arise in smell identification and the third, a theoretical enumeration of smell-related refactorings to suggest why smells may be left alone from an effort perspective. Key findings of the study were that first, s...

Software reuse has been discussed in the literature for the past three decades and is widely seen as one of the major areas for improving productivity. Agile development techniques were first developed in the mid-1990s as a code-oriented method of software development that seeks to improve upon the traditional plan-based methodologies. Both approaches bring value to the software development process. The purpose of this chapter is to propose a framework that will integrate the strengths of code reuse into the Extreme Programming methodology. It is believed that this approach will lead to a more effective method of software development.

An Enterprise Resource Planning (ERP) system is an integrated software system, typically offered by a vendor as a package that supports the seamless integration of all the information flowing through Business Processes, Business Intelligence, Business Integrations, Collaborations, etc. However, ERP implementation projects rank among the slow-moving, costly and challenging business solutions in an organization. Many ERP implementation projects are still executed adapting waterfall or similar traditional methodologies. While the usage of waterfall methodology in IT projects is diminishing, agile approaches usage is mounting. Agile movements provide proactive, active and reactive alternatives to traditional approaches by responding unpredictability and rapid volatility with well-timed, flexible and incremental iterations and empirical feedbacks. There are many approaches for agility. Among them, agile process management or agile project management can be considered as a broad approach ...

The fast increase of mobile device users based on wider and easier internet access has detonated the development of mobile applications (APP) and web. Therefore, improvement and innovation have become a top priority for businesses and consumer relations. The functional quality and interface aspects in applications (software) drive companies to succeed in mobile apps market competition. This paper introduces an agile software development methodology denominated MDSIC and MDSIC-M focused on rapid application development as required by small and medium software enterprises (SMEs), and results in better quality and competitiveness. MDSIC and MDSIC-M proposes some levels with better practices that should be followed in software development projects. This article also aims to show matching indicators and results of MDSIC and MDSIC-M implementations in software projects, by assessing the needed parameters to generate quality software, and thus align technology with the goals of the organizations.