To see the other types of publications on this topic, follow the link: The agile manifesto.
Journal articles on the topic 'The agile manifesto'
Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles
Consult the top 50 journal articles for your research on the topic 'The agile manifesto.'
Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.
You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.
Browse journal articles on a wide variety of disciplines and organise your bibliography correctly.
1
Hattendorf, Mareike. "Die Aktualität des Agilen." Agile Organisationen – Versuch einer kritischen Bestandsaufnahme 29, no. 1 (June 2021): 93–119. http://dx.doi.org/10.30820/0942-2285-2021-1-93.
Full textAbstract:
Die Anwendbarkeit des Agilen Manifestes in digitalen Dienstleistungsunternehmen ist bisher kaum in den Fokus einer praxisorientierten Theorie genommen worden, Gleiches gilt in diesem Kontext auch für die Aktualität agiler Werte und Prinzipen. Im Rahmen meiner Forschung untersuche ich deshalb, wie digitale Dienstleistungsunternehmen das Agile Manifest der Softwareentwicklung anwenden und ob und wie sie sich auf dieser Basis agil transformieren können. Die Beantwortung meiner Forschungsfrage ist für die Praxis sehr bedeutsam. Viele Unternehmen spüren die transformatorischen Anforderungen der Digitalisierung und suchen, teilweise verzweifelt, neue Wege. Mit Blick auf die agile Welt fehlt ihnen allzu oft das Handwerkszeug, gerade wenn es darum geht, erste agile Schritte zu wagen. Eine Anleitung, wie Agilität auf Basis des Agilen Manifests der Softwareentwicklung in Unternehmen umgesetzt werden kann, könnte für viele Unternehmen eine Hilfestellung darstellen.
2
Чуланова, Оксана, Oksana Chulanova, А. Меркулова, and A. Merkulova. "Methodical Instrumentation of Scrum Application as the Variety of the Methodology of Flexibility of Agile Manifesto Projects in the Management of Project Activity." Management of the Personnel and Intellectual Resources in Russia 7, no. 2 (June 13, 2018): 61–66. http://dx.doi.org/10.12737/article_5afedb6a7bdfa3.22810979.
Full textAbstract:
Project management includes many approaches and tools. The article presents the main principles of Agile as a methodology for flexible project management Agile manifesto. The main varieties of Agile manifesto are presented and the results of the author’s assessment of the possibilities and expediency of using each of the varieties are presented. More in detail in the article is considered Scrum. This methodology is popular in the development of complex projects. The essence of Scrum is to divide the entire process of the project into a lot of sprints, which require approximately the same amount of time to complete. Each sprint must combine an established number of specific tasks. The article notes that the ideological foundations of SCRUM are more clearly reflected in the Agile manifesto. This technology allows you to get the desired effect with minimal resources. Scrum allows you to correctly form resources and maximize the potential of the team. The article explores in detail the opportunities and risks that entail the use of one of the varieties of a flexible methodology for project management — Scrum. The author’s development of the methodological toolkit for implementing Scrum in project management of the organization is presented.
3
Naicker, Nalindren, and Manoj Maharaj. "Investigating Agile Requirements Engineering Practices in the South African Software Development Market." Journal of Computing and Information Technology 28, no. 1 (July 13, 2020): 33–58. http://dx.doi.org/10.20532/cit.2020.1004868.
Full textAbstract:
The aim of this research study was to assess Agile RE practices in the South African software development industry and investigate secure Agile RE initiatives towards developing secure products. This qualitative research study was contextualized in seventeen South African software development companies. The researchers used structured interviews and document reviews as the primary data collection instruments. Qualitative data was analyzed inductively using content analysis. Emanating from the research were recommendations to guide a regular software developer on good Agile RE practices. The study concluded that although Agile Software Development is practiced in the South African software industry, there needs to be stricter adherences to the Agile Manifesto and Agile Security Manifesto in requirements engineering.
4
George, Joey F., Kevin Scheibe, Anthony M. Townsend, and Brian Mennecke. "The amorphous nature of agile: no one size fits all." Journal of Systems and Information Technology 20, no. 2 (May 14, 2018): 241–60. http://dx.doi.org/10.1108/jsit-11-2017-0118.
Full textAbstract:
Purpose This paper aims to investigate the extent to which newly agile organizations followed 2001’s Agile Manifesto, especially in terms of the 12 principles of the agile approach, as included in the Manifesto. Design/methodology/approach The authors conducted in-depth case studies of groups in three large business organizations that had recently adopted agile. Two researchers spent one day at each site, attending daily standups and conducting interviews with managers, developers and customers. Findings Across the three organizations, developers were faithful to two agile principles: the primacy of delivering valuable software continually and regular reflections on the process with an eye toward improvement. The developers were uniformly unfaithful to the principle that requires face-to-face communication. Each organization varied in their adherence to the remaining nine principles. Obstacles to faithful adoption included the experience of the organization with agile, the extent to which the industry was regulated and the extent to which developers and customers were physically dispersed. Originality/value While past research on agile development is extensive, this paper examines perspectives on the method and its adoption through the lens of the original Agile Manifesto and its 12 principles. The principles were grouped into three broader categories – software delivery, people and process – to provide additional insights and to sharpen the analysis.
5
Kompalla, Andreas, and Jan Kopia. "Evaluation of the Agile Manifesto within Business Strategies." Journal of Economics and Public Finance 2, no. 2 (July 6, 2016): 227. http://dx.doi.org/10.22158/jepf.v2n2p227.
Full textAbstract:
<p><em>Every institution, company or single person needs a guideline aligning specific actions, processes and assets to an overall target. Recent research shows that guidelines of enterprises within the manufacturing branch or more specific within the automotive industry are almost identical. But new and emerging competitors force the traditional industry to adapt its business strategy and especially to increase flexibility. The internal and external changes within the manufacturing environment support this trend. The lead times are constantly shrinking and an increasing variety in customer demands has to be handled via new platforms and models. In conclusion, enterprises within the automotive industry need to increase agility and flexibility in order to stay competitive.</em></p><p><em>Within IT-project management, agility has been a focus since the end of the 1990s. Beneath that the automotive industry has applied several principles on the core value chain, logistics and production. But on the highest strategic level of an enterprise these principles have not been analyzed yet. This research paper is evaluating case studies in order to derive core agile aspects as well as principles. Based on that business strategies within the automotive branch are broken down and compared with these principles.</em></p><p><em>The result is that most of the agile aspects are not yet considered on the highest strategic business levels although they could increase the performance of enterprises within the automotive branch. But they need to be adapted to the specific characteristics.</em></p>
6
Alruwaili, Fatimah, Muna Alrajhi, and Kawther Saeedi. "How Agile Development and Its Tools Support Digital Transformation." INTERNATIONAL JOURNAL OF COMPUTERS & TECHNOLOGY 18 (February 1, 2019): 7440–50. http://dx.doi.org/10.24297/ijct.v18i0.8060.
Full textAbstract:
Digital transformation is the enabler for new reform of businesses, socialites and governments. It is also the platform to the 2030 Vision in Saudi Arabia and in many other countries. Agile Manifesto succeeded to manage software development in a rapid and reliable fashion. Furthermore, incremental delivery of software release ensure that software audiences are engaged while delivering the product, their comments are considered in every function and any changes in requirements are based on imperial use of the software. This ensure the delivery of functionalities matching customer demands as well as reduce project failure risk. For this reason, Agility has been adopted in most software companies as a guaranteed and easy way to implement the digital solutions for their companies. This paper examines the characteristics of agile frameworks, such as Scrum and XP, and Agile tools, such as Jira, Agilo, and others, that facilitate digital transformation. Then compare productivity and efficacy of agile frameworks with traditional SDLC methods. The paper is concluded with the features of agile framework that enable digital transformation such as incremental development, flexible requirements and customer engagement.
7
Jabar, Marzanah A., Norhayati Mohd Ali, Yusmadi Yah Jusoh, Salfarina Abdullah, and S. Mohanarajah. "Adaptive and Dynamic Hybrid Model for Software Project Management: A Review on its Clarity and Usage to Improve Project Success." Applied Mechanics and Materials 892 (June 2019): 38–45. http://dx.doi.org/10.4028/www.scientific.net/amm.892.38.
Full textAbstract:
Software developers have shown a lot of interest in using agile approaches and methods to manage projects. The Agile Manifesto in 2001 provided a good basis to use this as it formulated its 4 values and 12 principles. Adaptability was a common feature in the Agile Manifesto to make agility happen and there appears a need to combine dynamism to ensure agility takes a more concrete and effective role. Whilst the term adaptability is discussed more often than dynamism by most researchers, the clarity in its meaning needs improvement as the terms are used interchangeably. This paper proposes a useful clarity on its differences and how it should be used. In addition, this approach would also facilitate the current research interest in mixing and combining software development methodologies to create hybrid versions as pure methods (traditional and agile) have not worked well in most software projects.
8
Шапошнікова, О. П., and В. В. Кірвас. "Application of the Agile methodology in the practice of project-based learning in the training of IT specialists." Системи обробки інформації, no. 4(163), (October 28, 2020): 94–100. http://dx.doi.org/10.30748/soi.2020.163.10.
Full textAbstract:
Theoretical and practical issues of the active learning methods application using the high-profile methodologies aimed at finding effective learning technologies have been considered. There have been analysed the educational methodologies based on the Agile methodology to solve educational problems, taking into account the values and principles of the Agile methodology formulated in the Agile Manifesto. The project-based learning practice introduction in the educational process with the adaptation of the Agile methodology for teaching the “Architecture and analysis of software requirements”, “Software quality and testing”, “IT projects management” disciplines has been suggested, and the results of this approach have been analyzed.
9
Hassan, Ali, Soayba Younas, and Amiya Bhaumik. "Agile Methodology in an SaaS Deployment Project." International Journal of Information Technology Project Management 12, no. 2 (April 2021): 1–29. http://dx.doi.org/10.4018/ijitpm.2021040101.
Full textAbstract:
Agile manifesto has proven its ability in managing and execution of projects in multiple industry sectors. Many researches have been conducted on the advantages and applicability of agile practices in software development and information technology industry. In this paper, empirical research has been conducted to identify the differences in agile management practices between software development and software as a service (SaaS) deployment projects. Case studies of a payment card industry (PCI) organization have been presented to identify key characteristics, tools, and methods of agile project management practices practically followed while implementing and managing of SaaS-based projects. Moreover, best suited agile management practices for pre- and post-deployment projects have also been discussed.
10
KÖSE, Büşra Özdenizci. "RECENT AGILE REQUIREMENT ENGINEERING PRACTICES IN IT PROJECTS: A CASE ANALYSIS." Business & Management Studies: An International Journal 7, no. 4 (September 24, 2019): 1776–805. http://dx.doi.org/10.15295/bmij.v7i4.1214.
Full textAbstract:
Today, the implementation of high quality and efficient Requirement Engineering (RE) practices in agile software development projects, is gaining great importance. Practitioners and researchers seeks for lighter RE practices that can handle the issues of abstract, unclear and changing requirements, and at the same time that can satisfy the Agile Manifesto philosophy. This study examines importance of RE practices in agile software development projects, and explores which aspects of the RE practices are perceived as most critical and how such aspects are adapted in practice today through two different agile software development projects of a case organization. This study aims to contribute agile RE literature by providing an interpretive analysis on perception of agile RE practices from different perspectives (agile team members, product owners, some top executives). Within this context, this study draws lessons from case studies and presents beneficial agile RE guidelines for practitioners and researchers.
11
Heimicke, J., R. Chen, and A. Albers. "AGILE MEETS PLAN-DRIVEN – HYBRID APPROACHES IN PRODUCT DEVELOPMENT: A SYSTEMATIC LITERATURE REVIEW." Proceedings of the Design Society: DESIGN Conference 1 (May 2020): 577–86. http://dx.doi.org/10.1017/dsd.2020.259.
Full textAbstract:
AbstractMore than 15 years after the publication of the agile manifesto of software development, agile development approaches have also reached the processes of physical product development. Because of the boundary conditions and requirements here, which differ strongly from those of pure software development, these approaches often reach their limits. However, research and practice have quickly recognized that hybrid approaches integrate the strengths of agile and plan-driven development. This paper presents 25 hybrid development approaches that have been identified in a Systematic Literature Review.
12
Khalid, Ayesha, Shariq Aziz Butt, Tauseef Jamal, and Saikat Gochhait. "Agile Scrum Issues at Large-Scale Distributed Projects." International Journal of Software Innovation 8, no. 2 (April 2020): 85–94. http://dx.doi.org/10.4018/ijsi.2020040106.
Full textAbstract:
The agile model is a very vast and popular model in use in the software industry currently. It changes the way software is developed. It was introduced in 2001 to overcome deficiencies of software development in a workshop arranged by researchers and practitioners who were involved with the agile concept. They introduced the complete agile manifesto. The agile model has main components that make it more viable for use in well-organized software development. One of these is scrum methodology. The reason for the agile-scrum popularity is its use for small-scale projects, making small teams and allows change requests at any stage of a project from the client. It works for client satisfaction. Instead of so much popularity and distinctive features, agile-scrum also has some limitations when used for large scale projects development that makes it less efficient for development. This article discusses the agile-scrum methodology and its limitations when using for large-scale project organization.
13
Batra, Dinesh, Debra VanderMeer, and Kaushik Dutta. "Extending Agile Principles to Larger, Dynamic Software Projects." Journal of Database Management 22, no. 4 (October 2011): 73–92. http://dx.doi.org/10.4018/jdm.2011100104.
Full textAbstract:
The article evaluates the feasibility of extending agile principles to larger, dynamic, and possibly distributed software development projects by uncovering the theoretical basis for agile values and principles for achieving agility. The extant literature focuses mainly on one theory – complex adaptive systems – to support agile methods, although recent research indicates that the control theory and the adaptive structuration theory are also applicable. This article proposes that at least three other theories exist that are highly relevant: transaction cost economics, social exchange theory, and expectancy theory. By employing these theories, a rigorous analysis of the Agile Manifesto is conducted. Certain agile values and principles find theoretical support and can be applied to enhance agility dynamic projects regardless of size; some agile principles find no theoretical support while others find limited support. Based on the analysis and the ensuing discussion, the authors propose a framework with five dimensions of agility: process, design, people, outcomes, and adaptation.
14
Et.al, Rosnani Shuib. "Towards Adopting Software Quality Assurance in Agile Development Methodology." Turkish Journal of Computer and Mathematics Education (TURCOMAT) 12, no. 3 (April 10, 2021): 2152–57. http://dx.doi.org/10.17762/turcomat.v12i3.1158.
Full textAbstract:
In agile software development methodology, software product is developed through a few iterations and delivered incrementally. In spite of the known benefits of the agile methodology, yet issue still exists in developing high-quality software product using this methodology. Hence, quality assurance mechanism should be in place in agile development to ensure quality adherence to the software product. However, taking up quality assurance in agile software development is not an easy task as it has its own manifesto and principles that need to be met. Thus, this paper highlights the issues and challenges towards adopting quality assurance in agile development methodology. Particularly, in aniteration where we need to assure that the product increment meets the requirements as well as to decide the requirements for next increment and iteration planning. Subsequently, few measuresare identifiedconcerning the issues. The discussion in this paper is based on Scrum case, yet still relevant to other types of agile methodologies.
15
Singh*, Kajal. "Agile Methodology for Product Development: A Conceptual Study." International Journal of Recent Technology and Engineering 10, no. 1 (May 30, 2021): 209–15. http://dx.doi.org/10.35940/ijrte.a5899.0510121.
Full textAbstract:
Agile is a software development life cycle (SDLC) methodology that is based on smarter and faster operating principles and techniques. The paper aims to review the agile processes, principles, characteristics, and frameworks for the continuous development of the product while controlling the integration, scope, schedule, cost, quality, resources, risk, procurement, and stakeholder management. Traditional product development methods are not much efficient to adjust the rapid changes of the requirements and provide quality products to the stakeholders. Using agile frameworks, the software development team, customers, and team leaders work more closely to produce high-quality products responding to the changes rapidly. This paper will also present the background analysis of the agile manifesto and will serve as a guide to indicate the characteristics and framework of Agile which places customer satisfaction at the highest priority. Additionally, it will focus on the advantages and disadvantages of the agile projects for faster and frequent delivery of the development.
16
Schmitt, Anna, and Sabrina Hörner. "Systematic literature review – improving business processes by implementing agile." Business Process Management Journal 27, no. 3 (January 14, 2021): 868–82. http://dx.doi.org/10.1108/bpmj-10-2019-0422.
Full textAbstract:
PurposeNumerous approaches from the field of economics already exist for the improvement of business processes. In the field of software development, work has been done on improving development processes. For years, the focus here has been on agile approaches. Although various approaches for improving business processes exist, it is becoming increasingly difficult to adapt business processes to the fast-moving conditions of the market and the business environment. Agile approaches address this issue. Thus, not only software development processes, but also business processes should benefit from agile approaches.Design/methodology/approachTo this end, values and principles of the Agile Manifesto, agile methods such as Scrum, and various agile practices such as the Kanban board should be applied in business processes. This paper examines the work already done on this topic. With the help of a systematic literature review (SLR), literature studies dealing with the implementation of the agile approach in business processes are identified.FindingsThis paper presents, investigates and contrasts 12 primary sources dealing with agile and business processes and shows how they are different/ equal regarding three research questions.Originality/valueWe provide an overview of existing approaches handling the combination of agile and business processes to improve business processes.
17
Batra, Dinesh, Weidong Xia, and Shekhar Rathor. "Agility Facilitators for Contemporary Software Development." Journal of Database Management 27, no. 1 (January 2016): 1–28. http://dx.doi.org/10.4018/jdm.2016010101.
Full textAbstract:
Agile software development generally refers to popular practices that are supposed to adhere to the Agile Manifesto with its values and principles. Empirical studies on agile software development have mainly focused on organizational adoption and impacts of agile practices. Furthermore, the literature on agile software development has mostly centered on small, co-located projects. However, agility is needed for software development projects of varied sizes in different organizations across industries. The general nature of agile values and principles and the procedure-driven nature of specific agile methods make it difficult for organizations to determine what they can do to effectively facilitate agility in their software development process. To bridge that literature gap and based on an evolved grounded-theory approach, this study identifies nine agility facilitators and their corresponding dimensions that extend beyond small, co-located projects to software projects of any size and distribution. These agility facilitators are further grouped into two categories: organizational foundation and project processes. In addition, the authors identify four dimensions of agility. The authors propose a framework that describes the organizational mechanisms through which the nine categories of facilitators lead to software development agility.
18
MATALONGA, SANTIAGO, MARTÍN SOLARI, and GERARDO MATTURRO. "FACTORS AFFECTING DISTRIBUTED AGILE PROJECTS: A SYSTEMATIC REVIEW." International Journal of Software Engineering and Knowledge Engineering 23, no. 09 (November 2013): 1289–301. http://dx.doi.org/10.1142/s021819401350040x.
Full textAbstract:
In the last decade we have witnessed a growth in outsourcing and outshoring development. Following the promise of reducing costs and round-the-clock development, software organizations have grown from local to global enterprises. In the same decade, agile software development methodologies have emerged as a viable alternative to produce software. There is a myriad of agile processes and methodologies now available for any software development organization to choose from. These agile processes follow the values signed in the Agile Manifesto that preaches the exaltation of the individual programmer, high feedback, customer interaction and just enough planning and documentation. But how does global distribution affect these values? Can agile software development be implemented under the global software development context? This paper presents a systematic literature review aimed at identifying factors that affect the adoption of agile factors in global distributed teams. Our findings show that the literature is still in its initial case study publication stage. But most notably, we have found that only a few of the factors found are related to the agile values. Even though more research is clearly needed, this can be a signal that the factors affecting team distribution has more impact on software development than the values and practices preached by the agile processes.
19
Haslinger, Lukas, Hermann Sikora, and René Riedl. "Problembereiche verteilter agiler Teams: Literaturanalyse und Praxisimplikationen." HMD Praxis der Wirtschaftsinformatik 57, no. 5 (October 2020): 1014–32. http://dx.doi.org/10.1365/s40702-020-00661-4.
Full textAbstract:
Zusammenfassung Seit Bestehen des Agilen Manifests 2001 bildeten sich vermehrt agile Softwareentwicklungs-Teams, die sich in Aufbau und Funktionsweise voneinander unterscheiden. Viele dieser Teams verteilen sich auf mehrere Standorte. Der Grad der Verteilung kann dabei von „in unterschiedlichen Gebäuden auf einem Firmengelände“ bis hin zu „anderer Kontinent“ reichen. Da das Agile Manifest auf stetige informelle Kommunikation (kurze, unbürokratische Wege) und vergleichsweise wenig Dokumentation setzt, sind bei verteilten Teams Schwierigkeiten und Probleme zu erwarten, wenn die Werte des Manifests konsequent verfolgt werden. Ein verteiltes Softwareentwicklungs-Projekt birgt an sich bereits Risiken (z. B. im Wissenstransfer zwischen den Entwicklern), wobei bei einem verteilten agilen Projekt zusätzliche Probleme auftreten können. Die Fachliteratur befasst sich seit rund 15 Jahren mit dieser Problematik. Befunde empirischer Studien beschreiben verschiedene Problembereiche; zudem werden Lösungswege erläutert. Im gegenständlichen Beitrag wird der aktuelle Stand der Literatur analysiert, um die wichtigsten Problembereiche herauszuarbeiten. Die Beschreibung dieser Problembereiche hilft insbesondere Handlungs- und Entscheidungsträgern in der Praxis, potenzielle Schwierigkeiten verteilter agiler Teams zu erkennen. Dies ist eine wesentliche Grundlage für proaktives Management, um die möglichen negativen Wirkungen zu vermeiden.
20
Žužek, Tena, Janez Kušar, Lidija Rihar, and Tomaž Berlec. "Agile-Concurrent hybrid: A framework for concurrent product development using Scrum." Concurrent Engineering 28, no. 4 (September 24, 2020): 255–64. http://dx.doi.org/10.1177/1063293x20958541.
Full textAbstract:
Agile development became very popular at the beginning of the 21st century when the Manifesto for Agile Software Development was released. Since then, it has been predominant in the software industry and has been increasingly transferred to the development of physical products due to its great success. There are many studies on Agile-Stage-Gate hybrids that combine agile Scrum and the traditional Stage-Gate model, however no research has been found that addresses a direct integration of Scrum into a concurrent product development model in a similar way. In this paper, we therefore examine the possibility of introducing Scrum into the concurrent product development and propose a Scrum framework for an Agile-Concurrent hybrid. We propose that the framework for concurrent development remains unchanged: the stages overlap and the track-and-loop approach is preserved, while Scrum is proposed for the execution of day-to-day work. The main advantage of the proposed hybrid is that after each iteration the customer reviews the results of an entire loop, not just of one stage, which enables a broader understanding of the progress and facilitates a more extensive feedback. A quicker resolution of discrepancies, and a faster and more effective response to change is thus ensured. In the paper, the needed organizational changes and potential implementation issues are also discussed.
21
Peterson, Matthew, and Joshua Summers. "WHEN WORLDS COLLIDE – A COMPARATIVE ANALYSIS OF ISSUES IMPEDING ADOPTION OF AGILE FOR HARDWARE." Proceedings of the Design Society 1 (July 27, 2021): 3451–60. http://dx.doi.org/10.1017/pds.2021.606.
Full textAbstract:
AbstractThe objective of this paper is to explore challenges identified for implementation of scrum for hardware development intersect with agile principles found in the literature. A series of comparative analyses are done at the textual level, through logical intersections, and through thematic analysis. It is shown that there are five underlying themes found across two sets of scrum challenges (constraints of physicality and the 13 principles). These five themes include: flexiblity, chunkability, scalability, endurability, and teamability. These five themes further are found related to the defining principles of the agile manifesto. Using this understanding, future efforts will include empirical case study work to determine the impact that these have on application of scrum methods and tools. Additionally, guidelines should be developed to help hardware product engineers in applying scrum.
22
Balijepally, VenuGopal, Gerald DeHondt, Vijayan Sugumaran, and Sridhar Nerur. "Agility in Software Development and Project Value." Journal of Database Management 28, no. 4 (October 2017): 40–59. http://dx.doi.org/10.4018/jdm.2017100103.
Full textAbstract:
Agile Development Methods, considered as an alternative to the traditional plan-based methods, have received much attention since their inception. These practices have evolved and developed over time, culminating in 2001 with the Agile Manifesto. Since that time, preferred methodologies, implementations, and best practices have continued to evolve with a focus on doing what works best for the individual company or project. However, the concept of agility in software development has remained quite nebulous, lacking in clarity particularly about its underlying dimensions. In this research the authors conceive agility in terms of four distinct dimensions. Drawing from the theoretical perspective of holographic organization, they develop a model explaining how each of these underlying dimensions of agility contributes to project value in software teams. The authors test the model using survey data collected from industry practitioners and discuss findings.
23
Et.al, Marzanah A. Jabar. "The Use of Repeatable Components in Hybrid Models to Enhance Software Project Management Success." Turkish Journal of Computer and Mathematics Education (TURCOMAT) 12, no. 3 (April 10, 2021): 2058–63. http://dx.doi.org/10.17762/turcomat.v12i3.1074.
Full textAbstract:
The management of software project development requires a dynamic and reactive environment to meet shorter time-to-market demands to address competition efficently in the software industry. This scenario requires the use of effective and robust methodologieswhere opportunities are not lost due to delays and failures in timely software project deliveries.The Agile Manifesto in 2001 which introduced 4 values and 12 principles was designed to develop and manage software projects in a more suitable and effective way to improvethe success rates of software projects. But, increase in overall success rates are still not significant with failure rates remaining plauteaued at about 30% over the last 10 years. Hybrids methodologies seem to have worked better as agile hybrid management methodshave shown more promise when compared to pure agile methods with an overall success rate increase of 16%. There is evidence too that by combining agile methodologies with traditional methodologies, there would be a further increase in success rates. Whilst many hybrid methodologies have been suggested and researched, the gaps in the literature review reveal there is a lack of hybrid models that have been empirically developed and studied as second order components. To build a robust hybrid model, it is important to gather the relevant information and careful consuideration must be given to the design of the questionnaireto fit second order components and models must incorporate and provide for the use repeatable ways to test models once the data is collected.This paper presents a review of the current gaps in hybrid methodologies and proposes a questionnaire design that supports the research methodology and empirical study to be undertaken with second order components (Constructs).Further it looks at the design approach in questionnaires which incorporates the use of repeatable constructs and the measures used and emphasizes this as an important ingredient for developing and testing hybrid models in research studies.
24
Englund, Markus, Mikko Heikkinen, and Lisa Sundström. "Involving Collection Staff in the DINA Software Development – An Agile Approach." Biodiversity Information Science and Standards 2 (May 18, 2018): e25580. http://dx.doi.org/10.3897/biss.2.25580.
Full textAbstract:
In order to ensure long-term commitment to the DINA project (“DIgital information system for NAtural history data”, https://dina-project.net), it is essential to continuously deliver features of high value to the user community. This is also what agile software development methods try to achieve by emphasizing early delivery, rapid response to changes and close collaboration with users (see for example the Manifesto for Agile Software Development at http://agilemanifesto.org). We will give a brief overview on how current development of the DINA collection management system core is guided by agile principles. The mammal collection at the Swedish Museum of Natural History will be used as an example. Developing a cross-disciplinary collection management system is a complex task that poses many challenges: Which features should we focus on? What kinds of data should the system ultimately support? How can the system be flexible but still easy to use? Since we cannot do everything at once, we work towards a minimum viable product (MVP) that contains just enough features at a time to bring value for selected target users. In the mammal collection case, the MVP is the simplest product that is able to replace the functions of the current system used for managing the collection. As we begin to work with other collections, new MVPs are defined and used to guide further development. Thus, the set of features available will increase with each MVP, benefiting both new and current users. Another big challenge is migration of legacy data, which is labor intensive and involves standardizing data that are not compatible with the new system. To address these issues, we aim to build a flexible data model that allows less structured data to coexist with more complex, highly structured data. Migration should thus not require extensive data standardization, transformation and cleaning. The plan is to instead offer tools for transforming and cleaning the data after they have been imported. With the data in place, it will be easier for the user to provide feedback and suggest new features.
25
Soueid, Mohamad Ismat, and Antonio Felipe Cora Martins. "Scrum and agility beyond it: evidences in the brazilian mining industry." Revista de Gestão e Projetos 12, no. 1 (March 11, 2021): 123–48. http://dx.doi.org/10.5585/gep.v12i1.17624.
Full textAbstract:
De acordo com o 14º Relatório do Estado do Agile (Versionone, 2020), a Gestão de Projetos Ágeis (GPA) apresenta resultados positivos para melhoria da produtividade, alinhamento, visibilidade e priorização das demandas. Embora seja aplicada na indústria de desenvolvimento de software, outros setores buscam sua adoção a fim de obter os resultados conhecidos pela metodologia, como nos segmentos financeiro, comercial, marketing e industrial. Por meio de uma abordagem qualitativa, o presente artigo teve como objetivo compreender como os valores do Manifesto Ágil e das ferramentas scrum poderiam gerar resultados positivos de eficiência na rotina de uma indústria de mineração brasileira, que desconhecia completamente a GPA e apresentava falhas de gestão. Como protocolo de pesquisa, a intervenção ocorreu por meio de um programa de treinamento (presencial) com 14 funcionários da organização de diversas áreas, no qual foi medida a variação do ganho de eficiência após a aplicação da GPA na rotina. Como resultados, foi possível observar que houve variações positivas no relacionamento entre as pessoas (colaboração), maior proximidade do cliente no processo de entrega de valores (percepção do valor do produto), melhor comunicação e interatividade entre os membros da equipe, melhor priorização de tarefas (viabilidade), geração de novos produtos (inovação) e adoção de uma reunião retrospectiva ao final de cada ciclo de entrega como procedimento formal de melhoria contínua.
26
Pérez, Luis Jurado, and Joaquín Salvachúa. "An Approach to Build e-Health IoT Reactive Multi-Services Based on Technologies around Cloud Computing for Elderly Care in Smart City Homes." Applied Sciences 11, no. 11 (June 2, 2021): 5172. http://dx.doi.org/10.3390/app11115172.
Full textAbstract:
Although there are e-health systems for the care of elderly people, the reactive characteristics to enhance scalability and extensibility, and the use of this type of system in smart cities, have been little explored. To date, some studies have presented healthcare systems for specific purposes without an explicit approach for the development of health services. Moreover, software engineering is hindered by agile management challenges regarding development and deployment processes of new applications. This paper presents an approach to develop health Internet of Things (IoT) reactive applications that can be widely used in smart cities for the care of elderly individuals. The proposed approach is based on the Rozanski and Woods’s iterative architectural design process, the use of architectural patterns, and the Reactive Manifesto Principles. Furthermore, domain-driven design and the characteristics of the emerging fast data architecture are used to adapt the functionalities of services around the IoT, big data, and cloud computing paradigms. In addition, development and deployment processes are proposed as a set of tasks through DevOps techniques. The approach validation was carried out through the implementation of several e-health services, and various workload experiments were performed to measure scalability and performance in certain parts of the architecture. The system obtained is flexible, scalable, and capable of handling the data flow in near real time. Such features are useful for users who work collaboratively in the care of elderly people. With the accomplishment of these results, one can envision using this approach for building other e-health services.
27
Gorobinskiy, Ilya S., Yulianna A. Demidova, Yuliya A. Prunova, and Irina S. Ptukhina. "The analysis of an integrative analytical method used for the initiation of an investment construction project." Vestnik MGSU, no. 9 (September 2020): 1297–307. http://dx.doi.org/10.22227/1997-0935.2020.9.1297-1307.
Full textAbstract:
Introduction. The mission of the research is to analyze the main principles and values of investment construction project management subject to each methodology.
In the late 20th century it became clear that the majority of products, manufactured back in the days of the USSR, had counterparts, made in the Western countries, and the characteristics of the Western counterparts were a lot better. This trend favours the consumer society; however, producers must set new objectives aimed at optimization, quality improvement, and effective management to stay in the market. This is how the need for alternative sources of optimization emerged.
The practical implementation of theoretical project management provisions was among the tools. It tightens control and improves the efficiency of all resources of an enterprise. The application of an advanced approach to projects, implemented by public and private partnerships, will boost interaction between the state and the business community as well as project implementation control. Project management has become an integral project development instrument, applied to software projects and many other types of business activities. The main goal is to decide upon the project methodology.
Materials and methods. The project is based on the analysis of earlier research undertakings performed using methods of theoretical research, based on the study and generalization of performance charts published by domestic and foreign authors in the past.
Conclusions. The co-authors have analyzed project management methodologies, including best practices and templates. A brief analysis of the methodology application track record is performed. The research digest encompasses three principal methodologies; their principles and values are analyzed in the work.
Project deliverables include a comparative analysis of principles underlying PMI, Prince 2, and Agile Manifesto standards. Each principle underlying most widely used international standards of project management is described.
28
Goswami, Mohit, and Gopal Kumar. "An investigation of agile manufacturing enablers in Indian automotive SMEs using structural equation model." Measuring Business Excellence 22, no. 3 (August 20, 2018): 276–91. http://dx.doi.org/10.1108/mbe-10-2017-0068.
Full textAbstract:
Purpose This paper aims to analyze the agile manufacturing practices in small and medium enterprises (SMEs) within the auto-ancillary sector spread across eastern India. Using statistical method, a number of crucial insights have been captured and discussed in detail. Design/methodology/approach A structural equation model (SEM) encapsulating pertinent agile manufacturing attributes and enablers as the focal construct is conceptualized and validated in this research. The SEM model is evolved in a manner that agile attributes and agile enablers are modeled as latent dependent and manifest variable, respectively. Findings A number of key hypothesis entailing interactions of key agility enablers, i.e. manufacturing responsiveness agility, manufacturing strategy agility, workforce agility, technology agility, manufacturing management agility, etc. are conceptualized and validated. Originality/value The authors specifically focus on evolving agile manufacturing framework (characterized by agility enablers and attributes) that lies at the intersection of SMEs, automotive sector and an emerging economy.
29
SKRZYPEK, Adam. "ZWINNE ZARZĄDZANIE ORGANIZACJĄ W WARUNKACH ZMIENNOŚCI OTOCZENIA." Nowoczesne Systemy Zarządzania 12, no. 1 (March 31, 2017): 283–93. http://dx.doi.org/10.37055/nsz/129467.
Full textAbstract:
W warunkach nasilającej się zmienności otoczenia rośnie znaczenie zwinnego zarządzania, które powinno być oparte na zwinnej strategii i elastycznych procedurach. Powinny być opracowane sposoby rozpoznawania i reagowania na pojawiające się na rynku szanse i zagrożenia. Agile to pewien rodzaj kultury, zwinność stwarza możliwości tworzenia czegoś nowego. Agile to szansa na minimalizowanie kosztów, zmianę wymagań, szybkie dostarczanie potencjalnie gotowych do użycia rozwiązań. To nowy sposób pracy opisany zgodnie z wartościami zawartymi w Manifeście Agile. Obejmują one relacje zachodzące pomiędzy ludźmi i interakcjami oraz procesami i narzędziami, działającym oprogramowaniem a szczegółową dokumentacją, współpracą z klientami a negocjacjami umów oraz reagowaniem na zmianę a realizacją założonego planu. W artykule wskazano na istotę, rolę i znaczenie zwinności w zarządzaniu organizacją, przedstawiono drogę prowadzącą do powstania manifestu zwinności oraz omówiono wybrane metodyki zwinności w zarządzaniu projektami, w tym Scrum.
30
Zlatev, Zlatko, Galina Veres, and Zoheir Sabeur. "Agile Data Fusion and Knowledge Base Architecture for Critical Decision Support." International Journal of Decision Support System Technology 5, no. 2 (April 2013): 1–20. http://dx.doi.org/10.4018/jdsst.2013040101.
Full textAbstract:
This paper describes the architecture and deployment of a software platform for information fusion, knowledge hosting and critical decision support. The work has been carried out under the TRIDEC project (www.tridec-online.eu), focusing on geo-information fusion and collaborative decision making. Four technologies underpin the architecture: 1) A message oriented middleware, for distributed communications; 2) A leveraged hybrid storage solution, for efficient storage of heterogeneous datasets and semantic knowledge; 3) A generic data fusion container, for dynamic algorithms control; and 4) A single conceptual model and schema, as systems’ semantic meta-model. Deployment for industrial drilling operations is described. Agility is manifested with the ability to integrate data sources from a proprietary domain, dynamically discover new datasets and configure and task fusion algorithms to operate on them, aided by efficient information storage. The platform empowers decision support by enabling dynamic discovery of information and control of the fusion process across geo-distributed locations.
31
Kompella, Lakshminarayana. "A Co-Evolution Framework Towards Stable Designs from Radical Innovations for IT Organizations." International Journal of Innovation and Technology Management 17, no. 01 (February 2020): 2050006. http://dx.doi.org/10.1142/s0219877020500066.
Full textAbstract:
The external triggers cause transitions; to stay competitive, organizations create, respond to change, and shape the environment they interact with. The interactions manifest their traits as characteristics. Like biological species, organizations possess memes (or genotypes), memes mature as ideas or innovations, their interactions with the environment manifest as characteristics (phenotypes). IT organizations experience fast changes, for better response to change adopted agile software development (ASD). When phenotypes involve the development of affordances and display plasticity (agility), apart from cost-benefit criteria, it contributes to co-evolution among organizations and the environment. To examine the phenomena of co-evolution with diverse analytic and heuristic views, the author used multiple ASD case-studies from IT product[Formula: see text]services organizations. The author noted that organizations increase the height of their fitness landscape, i.e., competitive advantage, by either developing and[Formula: see text]or acquiring phenotypes. Acquisition meets cost-benefit criteria, but does not assist in sustaining the height, co-evolution, and[Formula: see text]or cumulate as stable designs, thereby, there are inappropriate responses to external triggers.
32
Teoh, SayYen, and Calvin ML Chan. "Thriving on waves of change: Case study of an agile digital business in Singapore." Journal of Information Technology Teaching Cases 10, no. 2 (May 5, 2020): 48–53. http://dx.doi.org/10.1177/2043886920910436.
Full textAbstract:
Much has been written and said about the need to be agile for businesses to transform themselves and adapt in the dynamic digital economy. This case study traces the history of a Singaporean IT firm from its inception in 1993 to 2019. In particular, this case study illustrates how agility has enabled the company to grow from a start-up to be among the leading IT firms in Singapore albeit operating in the dynamic IT industry that has grown increasingly volatile with the emergence of disruptive digital technology and innovation. Apart from drawing insights on organizational agility and adaptation, this case study also provides illustration on the theme of entrepreneurship and leadership as manifested through the Founder and Chief Executive Officer.
33
Buchmann, Robert Andrei, and Dimitris Karagiannis. "A Semantic Approach to Deploying Product-Service Systems." International Journal of Information System Modeling and Design 8, no. 1 (January 2017): 24–42. http://dx.doi.org/10.4018/ijismd.2017010102.
Full textAbstract:
Conceptual modeling is commonly employed for two classes of goals: (1) as input for run-time functionality (e.g., code generation) and (2) as support for design-time analysis (e.g., in business process management). An inherent trade-off manifests between such goals, as different levels of abstraction and semantic detail is needed. This has led to a multitude of modeling languages that are conceptually redundant (i.e., they share significant parts of their metamodels) and a dilemma of selecting the most adequate language for each goal. This article advocates the substitution of the selection dilemma with an approach where the modeling method is agilely tailored for the semantic variability required to cover both run-time and design-time concerns. The semantic space enabled by such a method is exposed to model-driven systems as RDF knowledge graphs, whereas the method evolution is managed with the Agile Modeling Method Engineering framework. The argument is grounded in the application area of Product-Service Systems, illustrated by a project-based modeling method.
34
Dickinson, Simon. "Spaces of post-disaster experimentation: Agile entrepreneurship and geological agency in emerging disaster countercartographies." Environment and Planning E: Nature and Space 1, no. 4 (November 13, 2018): 621–40. http://dx.doi.org/10.1177/2514848618812023.
Full textAbstract:
This article explores emergent spaces of social and political experimentation after the Canterbury, New Zealand, earthquakes of 2010–2011. Acknowledging that disasters generate distinctive spaces which reveal and provoke potentially disruptive imaginations and actions, I explore how the earthquakes gave rise to political experiments through which uncertainties were sensed, ordered and negotiated in the hopeful enactment of both conservative and radically alternative futures. Namely, I argue that the ruptures afforded by the earthquakes opened up the possibility for the dominant practices of a complex political conservatism in Christchurch to be challenged through the emergence of new and previously restrained claims to the city that have manifested, in part, through an emergent community organisation – the Canterbury Communities' Earthquake Recovery Network (CanCERN). Despite the earthquakes fuelling these repressed claims, this article explores the ways that these visions, claims and disquiets were shaped by evolving understandings of the nature and potential of the earthquake event. Analysis of CanCERN's activity reveals a kind of agile social entrepreneurship that remained alert to the opening and closing spaces of possibility within the disaster recovery landscape. Subsequently, this account works to not only draw attention to the discordant temporalities of possibility post-disaster, but also opens up discussion about the ways in which post-disaster experiments are shaped by unfolding senses of geological agency and indeterminacy.
35
Swist, Teresa, Liam Magee, Judy Phuong, and David Sweeting. "The labour of communicating publics: Participatory platforms, socio-technical intermediaries and pluralistic expertise." Communication and the Public 2, no. 3 (August 3, 2017): 210–25. http://dx.doi.org/10.1177/2057047317719294.
Full textAbstract:
Kolorob is a participatory platform connecting informal settlement communities with services and informal jobs in Dhaka, Bangladesh. Alongside technological systems, expertise from community, non-government, private-sector, volunteer and academic fields has been integral to the platform’s development. These socio-technical connections and networks, manifest through participatory design, agile software development and collaborative knowledge practices, have become productively entangled in the labour of platform production. We introduce a framework, participatory platform analysis, through which distinct layers – in the form of audiences, intermediaries, interfaces and databases – of this labour can be distinguished and examined. Our analysis draws upon focus group discussions, conducted in Mirpur in 2016 with emergent experts: youth facilitators, field officers and developers. We argue that the interests and tensions of co-designing participatory platforms relating to matters of public concern in South Asian mega-cities are reflective of the rising hybridity of expertise, generated through both institutional training and grass-roots practice, in contemporary urban life. The ‘narrative of expertise in the future’ compels us to recode knowledge production in the here and now: how we are making participatory platforms, the role of socio-technical expertise and the labour of communicating publics.
36
Xie, Dingsu, Fei Wang, and Jun Chen. "Extended Target Echo Detection Based on KLD and Wigner Matrices." Sensors 19, no. 24 (December 6, 2019): 5385. http://dx.doi.org/10.3390/s19245385.
Full textAbstract:
With the development of airborne radar radio frequency stealth (RFS) technology, the method of improving the RFS performance of airborne radar by optimizing target detection performance has been extensively studied. However, for wideband radar signals, the traditional point target model appears as an extended target model in the range-dimension, which is unfavorable to the detection of target echoes. To overcome the existing drawbacks, this paper devises an efficient echo detection algorithm from the perspective of information theory and random matrix. Firstly, aperiodic agile wideband radar signals are utilized to observe targets. Then, one frame of echo signals in the same range gate is reconstructed into a data form conforming to the Wigner matrix spectral decomposition. Finally, according to the signal detection theory, Kullback-Leibler Divergence (KLD) is used as the test statistic to complete the echo detection of the stealthy extended targets. By statistical analysis and comparison with other established echo detection algorithms, simulation results manifest that the proposed algorithm has superior detection performance and strong robustness, which not only makes up for the deficiency of traditional narrowband radar detection algorithms, but also increases the detection probability of radar system when it is faced with stealthy extended targets.
37
Juwariyah, Anik. "‘’Langen Tayub Padang Bulan” As A Manifestation of Social and Cultural Change in Community." Harmonia: Journal of Arts Research and Education 18, no. 2 (January 3, 2019): 189–96. http://dx.doi.org/10.15294/harmonia.v18i2.14002.
Full textAbstract:
This study examines Langen Tayub’s artistic position in social and cultural changes in society, especially in Nganjuk Regency. Langen Tayub as a product of a society that has undergone a change, also made innovations in Nganjuk community, this innovation was manifested in the form of a performance called Langen Tayub Padang Bulan. The research methods used include: Qualitative research approaches, data collection techniques uses: interviews, observation, documentation and recording. Data analysis used is the Talcott Parsons theory abbreviated as AGIL (A (adaptation), Achievement Goals (G-goal attainment), I (Integration), and L (latency) or pattern maintenance. Results showed that as a traditional cultural product, Langen Tayub experienced the changing form of presentation: Social and cultural changes that have taken place in the community have shifted the old model of Langen Tayub to Langen Tayub Padang Bulan, with some special characteristics that are adapted to the present conditions of society.
38
Pinciara, Barbara. "Risvolti etici in psichiatria." CHILD DEVELOPMENT & DISABILITIES - SAGGI, no. 1 (January 2011): 33–42. http://dx.doi.org/10.3280/cdd2010-001004.
Full textAbstract:
Da sempre la Medicina sente il bisogno di darsi delle regole e dei codici di comportamento a protezione del paziente. Ciň richiede ad ogni operatore di mettersi in gioco con autenticitŕ, apertura e costanza nel tempo: compito non facile, come testimonia il fatto che spesso la comunicazione con il paziente affetto da malattia psichica č carente o assente. Le maggiori difficoltŕ in questo senso si manifestano nelle "zone grigie" del rapporto medico-paziente: ad esempio nelle situazioni di criminalitŕ connesse alla patologia psichiatrica, nelle quali la tutela del paziente č spesso in contrasto con la necessitŕ di attuare misure protettive a livello sociale. Il medico che lavora con pazienti psichiatrici si trova spesso a dover prendere decisioni che condizionano la sua libertŕ: pensiamo ad esempio ai casi a rischio di suicidio, alla prescrizione di farmaci in grado di influenzare la qualitŕ di vita in senso medico e sociale (come gli antipsicotici), all'allontanamento da famiglie maltrattanti. Anche eventi quali l'innamoramento e la sessualitŕ tra medico e paziente pongono in primo piano la questione del rapporto personale che si instaura all'interno di questa diade tanto complessa. Per far fronte a queste difficoltŕ č necessario promuovere la comunicazione e l'alleanza terapeutica, fondate sul rispetto e sulla fiducia tra i terapeuti e con il paziente. Questo richiede all'operatore sanitario non solo di agire in modo etico, ma di "essere etico" come persona.
39
Haaland, Torunn. "Le vie verso la ragione: i segni del nuovo realismo in Gomorra." Quaderni d'italianistica 37, no. 2 (January 27, 2018): 191–210. http://dx.doi.org/10.33137/q.i..v37i2.29235.
Full textAbstract:
Il saggio si concentra sui concetti di realtà e impegno etico e civile in Gomorra. Il romanzo-inchiesta di Roberto Saviano viene inserito nel contesto del ritorno al realismo e dell’emergere di “oggetti narrativi non-identificati” nella narrativa contemporanea, per poi essere associato al dibattito sul nuovo realismo sviluppatosi nell’ultimo decennio in campo filosofico. Costituiscono un punto di riferimento essenziale il Manifesto del nuovo realismo ed altri scritti di Maurizio Ferraris, così come La questione morale di Roberta de Monticelli. Il primo approfondisce la natura inemendabile della realtà ontologica, separandola nettamente dalla realtà epistemologica, mentre la seconda rivendica il valore della ragione pratica come base di conoscenza e giudizio. Entrambi i filosofi si oppongono allo scetticismo etico in favore di una rivalutazione della capacità della percezione d’accertare tutto ciò che non è socialmente costruito o che non è vero. Il fatto che ci sia una realtà esterna e indipendente dal sapere umano permette di formulare dei giudizi intesi a indirizzare l’agire umano. L’analisi di Gomorra mostra, precisamente, una tendenza a ricorrere ai sensi come prove dei fatti e alla ragione per acquisire una conoscenza approfondita dei fatti stessi. Le esperienze sensibili si trasmettono, inoltre, nella parola testimoniale e nella presenza fisica sul territorio dell’autore-testimone: due elementi chiave su cui si costruiscono le condanne delle realtà rivelate. I giudizi morali pronunciati suggeriscono che la libertà consiste nel dovere di portare a compimento i diritti civili e di rendere ragione e chiedere agli altri di rendere ragione del proprio agire. In fine, una tale concezione della scrittura e dell’impegno civile rivendica la capacità della parola scritta di documentare, come propone Ferraris, fatti e azioni, e la potenza della ragione quale fondamento per un dialogo critico con i lettori.
40
Milosavljevic, Tanja. "The lexical-semantic representation of the concept of abilities in the dialectical linguistic image of the world (the case adjectives of the Serbian speech of Prizren)." Juznoslovenski filolog 73, no. 1-2 (2017): 135–54. http://dx.doi.org/10.2298/jfi1702135m.
Full textAbstract:
A fragment of the dialectical linguistic image of the world which represents the concept of the human intellect is linguistically manifested through the lexical-semantic subfield of abilities, which with the subfields of temperament and character completes the lexical-semantic field of human psychological characteristics and gives a more comprehensive account of the psychological profile of the Prizren dialectical persona. Within the lexical-semantic subfield of abilities we identify two parameters for the classification of lexemes, one in the field of intellectual and one in the field of psychomotor abilities. The lexical paradigm, based on semantic fields theory, is represented as a system of units organized into smaller lexical groups: the LSG of adjectives with the hyperseme ?intellectual abilities? and the LSG of adjectives with the hyperseme ?psychomotor abilities?. The human intellectual abilities are primarily reflected in the smart - dumb opposition. The set of units used to represent the negative sphere of human intellectual abilities is disproportionately broader in comparison to the lexical groups whose constituents have a more positive connotation. The constituents of the lexical-semantic subfield abilities combine elements from the intellectual sphere of the human psyche (smart, sensible, wise, able, skillful, agile, resourceful, quickwitted, sharp; dumb, imprudent, distracted, foolish, witless, crazy, insane). Here we can clearly see the distinction between the opposites smart - dumb and smart - crazy, while on the negative axis we can note the gradual transition from a mental state into a psychological state (dumb - crazy; crazy - dumb). The number of lexical features which can be used to mark the human intellectual capacity, the choice of the lexeme used to mark a man as a bearer of these features, and the high production of expressives in the domain of human intellectual characterization indicate that the principles of the intellect have a significant role to play in the understanding of the conceptualization of an individual among various speakers of a particular dialect.
41
Bignamini, Angelo A. "La persona centro e misura di ogni sistema sanitario." Medicina e Morale 51, no. 1 (February 28, 2002): 81–99. http://dx.doi.org/10.4081/mem.2002.713.
Full textAbstract:
L’organizzazione sanitaria è l’insieme delle strutture, funzioni e responsabilità che dovrebbe garantire l’adeguata gestione della sanità in un ambito definito. I soggetti coinvolti nel sistema sanitario sono le persone afferenti (sane e malate); gli operatori (medici e operatori sanitari non medici); l’ambito in cui esso viene attuato (società).
Essa è quindi il punto di incontro di tre realtà eminentemente umane: la medicina, l’etica, la società. I requisiti per un’adeguata organizzazione sanitaria implicano perciò la coesistenza dei principi fondamentali della medicina, dell’etica, della convivenza sociale. La medicina pone al suo centro il bisogno dell’essere umano che incontra il limite ai propri diritti nativi alla vita (cioè la morte) e alla salvaguardia di salute e integrità (cioè la malattia). La convivenza sociale impone la ricerca di un equilibrio tra i bisogni di ciascuno e la capacità di risposta della collettività nel suo complesso, incluse anche le capacità spontanee di aggregazione e di servizio, secondo priorità dettate dalla natura del soggetto del bisogno (la persona umana malata) e non pregiudizialmente definiti dall’osservatore. L’etica tutela i diritti nativi del soggetto (quoad justum), quindi determina procedure coerenti con la natura di quanti implicati nella progettazione e gestione dell’organizzazione sanitaria.
In un approccio bioetico ontologicamente fondato, i criteri primi sono quelli che si riferiscono ai soggetti autonomamente esistenti, quindi alle persone. Subordinati e dialoganti con questi sono i criteri secondi, cioè quelli relativi alle entità per sé non esistenti se non in dipendenza dell’essere dei soggetti autonomi: la società e, in ulteriore subordine, il “governo”, sia esso regionale, sia nazionale.
Esistono visioni alternative, nelle quali i criteri principali sono invece quelli, di stampo illuminista, relativi alla “collettività”, allo “stato”, cui si debbono subordinare i singoli “individui”. Già l’utilizzo di “individuo” contrapposto a “persona” mette in luce come questo approccio sia ideologico (basato su ipotesi astratte definite a priori) anziché scientifico (basato sull’osservazione della realtà).
I due approcci originano sistemi organizzativi della sanità contrapposti tra loro, con ruoli diversi anche per gli operatori e soprattutto per il medico. Nel modello illuminista di stato etico gli strumenti matematico-statistici e matematico- economicisti (DRG, EBM, linee guida) diventano gabbie interpretative (ideologiche) della realtà. Nel modello sociale tutti gli strumenti disponibili vengono impiegati come uno dei mezzi possibili, insieme a scienza, coscienza e compassione, per descrivere la complessa realtà della singola persona che si pone in relazione con il medico portando i propri bisogni di salute, espressi ed inespressi.
Secondo la bioetica personalista il criterio giustificante di qualunque “sistema” e qualunque “organizzazione”, inclusa l’organizzazione della sanità, è il “bene” di tutti i soggetti (malati e operatori con pari dignità), che si manifesta nel rispetto dei loro diritti, primo fra tutti il diritto alla difesa di vita e integrità, alla salvaguardia della salute, al rispetto dei criteri morali e religiosi di ciascuno. In questo contesto la persona rimane l’elemento centrale di riferimento della “organizzazione”, il rispetto della natura della persona rimane la misura della sua validità, la possibilità del “bene” della persona resta il criterio di valore. Esperienze in atto con questa visione non sembra siano, peraltro, meno efficienti di quelle basate sulla visione opposta. In questo contesto il medico, essendo l’operatore più prossimo al soggetto, ha però anche la responsabilità di agire come difensore dei diritti del malato (funzione etica) nei confronti del sistema organizzativo, anziché essere semplicemente un “fornitore di servizi”, dato che la salute non può essere ricondotta a “prodotto” o “servizio”, né può comprimersi nella definizione di “cliente” o “utente” la persona malata.
42
Taylor, Bryan C., Lee P. Shulman, Malcolm G. Munro, Stephanie Martin, Anita L. Nelson, and Patricia A. Locantore-Ford. "Advancing OB/GYN Knowledge, Competence, and Performance Related to Abnormal Uterine Bleeding and Intravenous Iron Supplementation for Effective Management of Iron Deficiency Anemia: Outcomes Analysis from a 2019 Educational Initiative." Blood 136, Supplement 1 (November 5, 2020): 28–29. http://dx.doi.org/10.1182/blood-2020-133836.
Full textAbstract:
Background: Iron deficiency anemia (IDA) is a multifaceted condition associated with immense obstetrical morbidity and mortality, and is especially prevalent in female patients of reproductive age.Abnormal uterine bleeding (AUB), which often manifests clinically as heavy menstrual bleeding (HMB), is the leading cause of IDA among reproductive age women in the United States, with a prevalence ranging from ~30-50% in this patient population; further, HMB is estimated to account for nearly one-third of all IDA causes worldwide. For these reasons, AUB/HMB is generally accepted as the primary causal source of IDA in daily clinical practice.As frontline clinicians who routinely manage HMB, OB/GYNs are optimally positioned to subsequently recognize, diagnose, and treat the IDA precipitated by HMB. However, to ensure the provision of safe and effective care, adaptive educational initiatives with an emphasis on evolving iron supplementation strategies are needed. Methods: Creative Educational Concepts (CEC) conducted a literature review, needs assessment, and detailed gap analysis to identify prominent clinical and educational gaps that exist among OB/GYNs with regard to IDA sign and symptom recognition, epidemiology, clinical gravity and risk factors, formal diagnosis, and appropriate treatment.Consequently, our team at CEC composed a responsive, multi-pronged educational design targeted to obstetricians, gynecologists, and women's health professionals, in a tailored effort to bridge the aforementioned gaps in current practice and improve outcomes for patients.CEC consulted with top experts in obstetrics and gynecology, maternal fetal medicine, pelvic surgery, and hematology at every stage of the educational design and delivery continuum, from proposal ideation to content development to live, on-site presentation.To dynamically engage the target audience, especially at the community, grassroots level, this educational initiative was delivered at a series of five American College of Obstetricians and Gynecologists (ACOG) District Meetings across the United States; live meetings were held in Lake Geneva, WI; San Diego, CA; Kapalua, HI; Rockport, ME; and Manhattan, NY. Results: 203 total clinicians were educated across the initiative Profession MD/DO - 93%APRN/CNM - 3%RN - 2%Other - 2%Specialty General OB/GYN - 81%Maternal/fetal Medicine - 11%Reproductive endocrinology - 4%Pelvic medicine/surgery - 2%Other - 2%>5,000 IDA patients potentially impacted per month as a result of the initiativeStatistically significant advances in learning and knowledge were achieved from pre- to post-activity for all tested educational gaps: Identification of IDA risk factors (85% post vs. 46% pre; P<0.001)Clinical implications of AUB (95% post vs. 74% pre; P<0.001)Appropriate clinical utility of IV iron (93% post vs. 63% pre; P<0.001)Top intended practice changes: Consider IV iron supplementation in my patients with IDA for whom oral iron supplementation is ineffective or intolerableConsider IV iron supplementation as first-line treatment for my patients with severe IDA, ongoing bleeding, and/or absorption deficienciesShare information learned with colleagues and other members of my healthcare teamTop anticipated barriers to change: Limited experience with parenteral iron supplementation therapiesPatient non-adherenceInadequate care coordination between OB/GYNs and primary care physiciansGiven an HMB-associated IDA patient case, activity attendees demonstrated a significant retention of knowledge and clinical performance improvement from pre-test to 4-week follow-up related to appropriate initiation of IV iron 90% at 4-wk follow-up vs. 63% at pre-test (P=0.018) Conclusions: Our 2019 ACOG District Meeting educational initiative precipitated substantive practice advances in knowledge, competence, and performance among OB/GYNs and women's health professionals related to IDA management.Statistically significant performance improvements in appropriate initiation of IV iron for treatment of HMB-associated IDA were achieved at follow-up assessment.Learning and knowledge endpoints for IDA risk factor recognition and AUB clinical implications were not retained with statistical significance at follow-up assessment, thereby evidencing residual educational gaps and a need for ongoing education in this space. Disclosures Shulman: Bayer: Consultancy; AMAG: Speakers Bureau; Lupin: Speakers Bureau; Vermillion: Speakers Bureau. Munro:Vifor: Consultancy; Abbvie: Consultancy, Research Funding; American Regent: Consultancy; Boston Scientific: Consultancy; Daiichi Sankyo: Consultancy. Martin:Daiichi Sankyo: Consultancy. Nelson:Merck: Consultancy, Honoraria, Membership on an entity's Board of Directors or advisory committees, Research Funding, Speakers Bureau; Bayer: Consultancy, Honoraria, Membership on an entity's Board of Directors or advisory committees; AMAG: Consultancy; Agile Pharmaceutical: Consultancy, Research Funding; EvoFem: Research Funding; Sebela Pharmaceutica: Consultancy, Research Funding; TherapeuticsMD: Membership on an entity's Board of Directors or advisory committees; American Regent: Consultancy, Membership on an entity's Board of Directors or advisory committees.
43
Denning, Stephen. "Updating the Agile Manifesto." Strategy & Leadership 43, no. 5 (September 21, 2015). http://dx.doi.org/10.1108/sl-07-2015-0058.
Full text
44
Cottam, Michael E. "An Agile Approach to LMS Migration." Journal of Online Learning Research and Practice 8, no. 1 (July 4, 2021). http://dx.doi.org/10.18278/jolrap.8.1.5.
Full textAbstract:
Principles of the Agile Manifesto may guide academic and technology teams to lead learning management system (LMS) migration projects with inclusiveness, flexibility, and speed. Agile teams follow an iterative, rapid-cycle path to design, develop, evaluate, revise, and improve the LMS from project inception to completion. An agile approach values individuals and interaction, delivering working courses, collaboration, and responsiveness to changing environments. With attention to each of these values in LMS migration, the project runs with full stakeholder engagement, responsiveness, and speed.
45
Beerbaum Dr., Dirk. "RegSafe© manifesto - an agile management control methodology for regulatory - driven programs." SSRN Electronic Journal, 2021. http://dx.doi.org/10.2139/ssrn.3813699.
Full text
46
Hohl, Philipp, Jil Klünder, Arie van Bennekum, Ryan Lockard, James Gifford, Jürgen Münch, Michael Stupperich, and Kurt Schneider. "Back to the future: origins and directions of the “Agile Manifesto” – views of the originators." Journal of Software Engineering Research and Development 6, no. 1 (November 9, 2018). http://dx.doi.org/10.1186/s40411-018-0059-z.
Full text
47
Watfa, Mohamed, and Tarek Kaddoumi. "A foundational framework for agile enterprise architecture." International Journal of Lean Six Sigma ahead-of-print, ahead-of-print (June 10, 2021). http://dx.doi.org/10.1108/ijlss-03-2021-0057.
Full textAbstract:
Purpose The application of agility principles and methodologies on Enterprise Architecture (EA) is a promising field. This paper aims to provide an in-depth study of the Agile Enterprise Architecture (AEA) by studying EA practitioners’ perspectives to propose a foundational framework for AEA. Design/methodology/approach The authors formulate a foundational framework that defines the AEA motivators, enablers and blockers using the agile manifesto as one of the AEA enablers where a total of 156 EA stakeholders with at least one year of experience in enterprise architecture were surveyed, and a set of hypotheses was analyzed and tested based on the proposed framework. The authors also develop a quantitative method to evaluate the agility index of the EA based on the introduced framework. Findings The research results show with significance that enterprise architects perceive positively the application of the agility methodologies on the enterprise architecture. This perception is primarily affected by the enterprise size, the EA dependency and the agile methodologies awareness. The findings also indicate that AEA is primarily motivated by the Business and IT Change Ready and Responsive EA. Finally, an EA Agility Index (EAAI) was designed to assess the agility application of the EA based on the three forces, i.e. motivators, enablers and blockers. Research limitations/implications Because of the chosen research approach and the sample size, the research results may lack generalizability. Also, EAAI designed was not thoroughly tested. Practical implications The paper includes implications for the design and development of an EA Agility Index, and the need to increase the awareness of the agility methodologies to overcome the blocker of the unfamiliarity with the agile methodologies implying that the current business models in enterprise must be more aligned with the agile methodologies. Originality/value While there are efforts to develop AEA frameworks, one of the major findings of the literature review conducted is that there is evident research gap in the literature on the perception and associated factors of the EA stakeholders on having an agile enterprise architecture. This paper attempts to fill this gap.
48
Hernández, Giovanni, and Álvaro Martínez. "Cuspe: propuesta ágil para la construcción de software basada en TSP [Cuspe: Agile approach for software development based on TSP]." Ventana Informatica, no. 30 (September 5, 2014). http://dx.doi.org/10.30554/ventanainform.30.285.2014.
Full textAbstract:
Resumen El objetivo principal de este artículo es aportar a la forma de trabajo de las empresas de la industria de software en Nariño mediante una propuesta metodológica ágil basada en Team Software Process (TSP). Este trabajo se desarrolló bajo el paradigma cuantitativo, con un enfoque empírico-analítico de tipo descriptivo-propositivo. La población objeto de estudio fueron las metodologías para construir software basada en equipos de trabajo, de las que se seleccionó de manera intencional TSP. Como resultado, se estableció que el nivel de agilidad que posee TSP corresponde al 79.25%. Así mismo, se diseñó Cuspe, como una propuesta para intervenir los principios del manifiesto ágil que presentan el menor nivel de cumplimiento en TSP. El trabajo permite concluir que la propuesta Cuspe basada en TSP logra incrementar el nivel de agilidad de la metodología y busca la entrega temprana y frecuente de software con valor, a través del trabajo y compromiso de personas motivadas; y consigue medir el progreso. Palabras Clave: Construcción de software, Manifiesto por el Desarrollo Ágil de Software, Team Software Process Abstract The main goal of this article is to support Nariño’s’ Software industry’s way of work through a methodological proposal based on Team Software Process (TSP). This work was carried out under a quantitative paradigm and a descriptive-propositional-based empirical-analytical approach. The object populations were the methodologies for building software based on work teams, in which TSP was intentionally chosen. As a result, it was set that TSP’s level of agility reached 71.25%. Furthermore , It was designed Cuspe as an proposal in order to intervene the principles of the Agile Manifesto which shows the lowest level of accomplishment regarding TSP. This work allows concluding that the Cuspe proposal based on TSP increases the level of methodology’s agility and leads to an early and frequent valuable software production through the work and compromise of motivated people, and also progress measurement. Keywords: Manifest for Agile Software Development, Software Development, Team Software Process.
49
Noé, Nico. "An artisan approach to biodiversity software development." Biodiversity Information Science and Standards 3 (June 18, 2019). http://dx.doi.org/10.3897/biss.3.35382.
Full textAbstract:
In a discipline where interoperability is crucial, funding is limited and reinventing the wheel is frowned upon (and rightfully so), the development of data management tools and biodiversity data portals is generally approached in an industrial way: the same application - whose specifications are often written by a committee - is developed as a complex “one size fits all” tool to be used by various groups in different contexts. While this approach generally makes sense, for the last 15 years the Belgian Biodiversity Platform has sometimes tried a complementary approach where an artisan-minded software developer is assigned to a specific “customer” and is given a direct communication channel and tons of freedom to develop a simple, made-to-measure application. This empirical experience has shown some unexpected advantages but also, as always, some new challenges. It takes inspiration in things as diverse as the Agile software manifesto and the apprenticeship model of medieval Europe. This talk will present this unusual approach and reflect on this ongoing experience, hopefully extracting pieces of wisdom that is useful to the broader community. For example, the following questions will be discussed: How does this method help mobilize biodiversity data? Can it “convert” scientists to Open Data? Has it some effects on the team stability and developer retention? Aren’t you writing the same code again and again, resulting in an unmaintainable mess? Isn’t this an example of living in isolation? What about sharing data with global initiatives such as GBIF? How does this method help mobilize biodiversity data? Can it “convert” scientists to Open Data? Has it some effects on the team stability and developer retention? Aren’t you writing the same code again and again, resulting in an unmaintainable mess? Isn’t this an example of living in isolation? What about sharing data with global initiatives such as GBIF?
50
"The Development of Interview Protocol to Explore Hybrid Agile Software Development Phases." International Journal of Advanced Trends in Computer Science and Engineering 10, no. 3 (June 7, 2021): 1639–45. http://dx.doi.org/10.30534/ijatcse/2021/221032021.
Full textAbstract:
Agile practices are a development approach based on agile manifestos that value individuals and interactions, working software, customer collaboration and responding to change. Recently, Software Engineering (SE) team is combining agile with non-agile development approaches, which lead to hybrid agile. Hybrid agile is a mixture of a plan-driven development approach and agile practices. Hybrid agile has gained the interest of software engineering team as one of the development approaches for recent software development projects. However, there are uncertainties of security measures of hybrid agile. Therefore, the security strategies of a software project developed based on hybrid agile needs further investigations. This research is a proportion of a study on hybrid agile, in which this research focuses on the development of the data collection instrument to study hybrid agile. This research explores the development and validation of an interview protocol that will be the instrument for studying the hybrid agile approaches and methods implemented by the Software Engineering team and discovering the security strategies taken to ensure reliable software will be deployed to the end-users. This paper will discuss the questions designed for research, which involves the development of the interview protocol. This paper also explains the validation process and reliability examination of the interview protocol to ensure the interview protocol is reliable for the actual data collection process fromthe identified sample population