scholarly journals Survey on Risk Classification in Agile Software Development Projects in Latvia

2020 ◽  
Vol 25 (2) ◽  
pp. 105-116
Author(s):  
Oksana Ņikiforova ◽  
Kristaps Babris ◽  
Jānis Kristapsons
Keyword(s):  
Software Development ◽  
Survey Data ◽  
Evaluation Criteria ◽  
Agile Software Development ◽  
Agile Development ◽  
Development Projects ◽  
Development Method ◽  
Potential Risks ◽  
Agile Software ◽  
Development Methods

AbstractSoftware development method, which does not have any faults or gaps in project implementation, has not been elaborated so far. Due to this reason, the authors have decided to perform this study to make it easier for the companies, which use one of the agile development methods, to better foresee potential risks and to deal with their consequences. The aim of the research is to identify and classify risks in agile software development methods and the related projects based on the obtained survey data. To achieve the goal, the authors have developed evaluation criteria, as well as implemented practical questionnaire in various software development companies. From the obtained survey data, the risks are classified according to various factors, i.e., the changing highest and lowest priorities and needs in various projects. Thus, the obtained research results can be applied in various areas of project development, changing the order of priority factors.

A Coordination Perspective on Agile Software Development

2015 ◽  
pp. 64-96
Author(s):  
Diane E. Strode ◽  
Sid L. Huff
Keyword(s):  
Software Development ◽  
Critical Factor ◽  
Agile Software Development ◽  
Development Projects ◽  
It Project Management ◽  
Software Projects ◽  
Coordination Strategy ◽  
Agile Software ◽  
And Coping ◽  
Development Methods

Achieving success in software development projects is a perennial challenge, and agile software development methods emerged to tackle this challenge. Agile software development provides a way to organise complex multi-participant software development projects while achieving fast delivery of quality software, meeting customer requirements, and coping effectively with project change. There is little understanding, however, of how such projects achieve effective coordination, which is a critical factor in successful software projects. Based on evidence from four cases, this chapter presents a theory explaining coordination in agile software projects. This theory defines the concepts of coordination strategy and coordination effectiveness and propositions explaining their relationship. This theory contributes to coordination literature by presenting clearly delineated concepts and their relationships in the form of a variance theory. For IT project management, this theory contributes to knowledge of coordination and coordination effectiveness in the context of agile software development.

scholarly journals Sistem Monitoring Kinerja Sub Bagian Operator Scada Menggunakan Agile Development Methods Studi Kasus PT. Cladtek Bi Metal Manufacturing

2021 ◽  
Vol 5 (01) ◽  
pp. 43-51
Author(s):  
Indah Kusuma Dewi ◽  
Randa Amalta Saputra
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Agile Development ◽  
Weld Overlay ◽  
Agile Software ◽  
Development Methods

PT. Cladtek BI Metal Manufacturing merupakan perusahaan yang bergerak dibidang jasa industri untuk berbagai pekerjaan mengenai material logam, khususnya proses Cladding, Weld Overlay dan Lining pada pipa baja karbon untuk keperluan industri. Pada departement Production memiliki karyawan berjumlah 19 orang terdiri dari 1 orang supervisor, 3 orang foreman dan 15 orang pada sub bagian operator scada. Satu orang foreman membawahi 5 orang karyawan untuk memonitoring kinerja dan pemberian nilai. Namun sangat disayangkan, bahwa performa tim hanya dicatat secara manual pada sebuah buku catatan (log book) oleh setiap foreman (atasan) yang membuat sistem penilaian setiap karyawan menjadi lebih sulit karena tidak adanya visualisasi data yang mempermudahan manajemen mengambil keputusan. Dalam penelitian ini digunaka metode Agile Development untuk mempermudah proses pengambilan spesifikasi sistem dan alur bisnis dan keputusan. Metode agile software development adalah pengembangan perangkat lunak berdasarkan pengembangan iterative dan incremental dimana syarat dan solusi berubah melalui kolaborasi antara selft organizing dan cross functional tim. Sistem ini dibangun dengan Bahasa pemograman Bahasa php, database mysql yang berbasis web dengan tujuan menghasilkan suatu sistem informasi monitoring yang terstruktur dan dapat menampilkan data analisis dalam sebuah dashboard untuk mengendalikan kinerja sub bagian scada di PT. Cladtek BI Metal Manufacturing menggunakan model scrum dan mempermudah penilaian dan kontrol terhadap daftar kerja dan proyek yang masih manual

scholarly journals New Approach on the Agile Cycles Containment Effectiveness Metrics in Automotive SW Development

ACTA IMEKO ◽  
2019 ◽  
Vol 7 (4) ◽  
pp. 3
Author(s):  
Ionut Andrei Sandu ◽  
Alexandru Salceanu
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Agile Development ◽  
Extended Version ◽  
New Approach ◽  
Development Team ◽  
Real Application ◽  
Original Contribution ◽  
Agile Software

<p class="Abstract"><span lang="EN-US">In an ideal Agile Development Team, defects should not exist. But in reality and especially in Automotive Agile Software Development, we need to have a mechanism for defects handling and tracking to closure. In this paper we describe the benefits and principles for measuring the defects handling metrics in automotive programs and organizations which adopted Agile SW Development. We are presenting the Iteration Containment Effectiveness, Program Increment Containment Effectiveness and Defect Debt Trend metrics. The acquired advantages are demonstrated by a detailed example of real application on how to measure the classical Phase Containment Effectiveness metric on Iteration (Sprint) and Program Increment (Scum of Scrums / Scaled Agile) Level. This paper is an extended version of the original contribution to the IMEKO TC 4 2017 symposium in Iasi, Romania.</span></p>

Agile Enablers and Adoption Scenario in Industry Context

2015 ◽  
pp. 157-178
Author(s):  
Vinay Kukreja ◽  
Amitoj Singh
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Agile Development ◽  
User Requirements ◽  
Distributed Environment ◽  
Team Members ◽  
Agile Methodologies ◽  
Software Development Methodologies ◽  
Agile Software

In the globalization of fast changing business and technology environment, it becomes very important to respond quickly to changing user requirements. Traditional methodologies are not appropriate for the projects where user requirements are not fixed. Agile methodologies have been developed to cope up with user changing requirements and emphasize more on working software and customer collaboration. Agile is an umbrella term and it is used for many software development methodologies which shares common characteristics. This chapter mainly focuses on the working methodology of agile development and the usage areas of industry where agile development is implemented. Agile software development is difficult in distributed environment as the team members are at distributed locations. This chapter discusses agile industry applicability enablers which are useful for agile software development in distributed environment.

Agile Software Development

2012 ◽  
pp. 1-15
Author(s):  
Torstein Nicolaysen ◽  
Richard Sassoon ◽  
Maria B. Line ◽  
Martin Gilje Jaatun
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Agile Development ◽  
Implementation Team ◽  
Agile Methodologies ◽  
Development Organizations ◽  
Development Lifecycle ◽  
Software Development Lifecycle ◽  
Agile Software

In this article, the authors contrast the results of a series of interviews with agile software development organizations with a case study of a distributed agile development effort, focusing on how information security is taken care of in an agile context. The interviews indicate that small and medium-sized agile software development organizations do not use any particular methodology to achieve security goals, even when their software is web-facing and potential targets of attack. This case study confirms that even in cases where security is an articulated requirement, and where security design is fed as input to the implementation team, there is no guarantee that the end result meets the security objectives. The authors contend that security must be built as an intrinsic software property and emphasize the need for security awareness throughout the whole software development lifecycle. This paper suggests two extensions to agile methodologies that may contribute to ensuring focus on security during the complete lifecycle.

Fixed Priced Projects in Agile

2016 ◽  
pp. 222-236
Author(s):  
Anuradha Chaminda Gajanayaka
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Development Model ◽  
Software Development Model ◽  
Responding To Change ◽  
The One ◽  
Agile Software ◽  
Development Methods ◽  
Software Development Methods

Agile software development has established as a reliable alternative to waterfall software development model. Unfortunately the use of agile software development has been limited to time based contracts and not for time limited contracts. The main reason for this limitation is the “Agile manifesto” itself. The forth value of the manifesto states that agile believers find more value in “Responding to change over following a plan”. This is the one of the main reasons why agile software development methods are not preferred for a fixed priced contract or time limited contract. The following case study provides an example on how the agile software development can be used for fixed priced software development contracts even when operating in offshore context. The agile software development concepts were used throughout to plan, execute, monitor, report, etc. for the project documented in this case study.

A Framework for Analyzing Structural Mechanisms Deployed to Support Traditional and Agile Methods

2021 ◽  
pp. 205-227
Author(s):  
Michal Dolezel ◽  
Alena Buchalcevova
Keyword(s):  
Software Development ◽  
Classification Scheme ◽  
Organizational Structures ◽  
Agile Software Development ◽  
Agile Methods ◽  
Two Dimensional ◽  
Dimensional Classification ◽  
Agile Software ◽  
Structural Mechanisms ◽  
Development Methods

People rely on structures to make their worlds orderly. This chapter conceptually probes into the problem of the differences between organizational structures deployed in traditional and agile environments. The authors develop an argument that all common forms of organizational entities can be classified by involving a two-dimensional classification scheme. Specifically, they constructed a typology to examine the issues of formal vs. informal authority, and disciplinarity vs. cross-functionality in terms of their significance for traditional and agile software development workplaces. Some examples of concrete organizational forms—including traditional project team, independent test team, self-organizing agile team and developers' community of practice—are discussed. In sum, they argue that by employing this classification scheme, they can theorize the nature of the on-going structural shift observed in conjunction with deploying agile software development methods. They acknowledge that the structures have fundamentally changed, terming the move “democratization” in the software development workplace.

Sign in / Sign up

Export Citation Format

Share Document