Agile Scrum Issues at Large-Scale Distributed Projects

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.

Download Full-text

Agile Transformation at Scale: A Tertiary Study

10.1007/978-3-030-88583-0_1 ◽

2021 ◽

pp. 3-11

Author(s):

Suddhasvatta Das ◽

Kevin Gary

Keyword(s):

Large Scale ◽

Software Industry ◽

Future Research ◽

Small Scale ◽

Agile Processes ◽

Current State ◽

Research Findings ◽

State Of Research ◽

Agile Software ◽

Tertiary Study

AbstractDue to the fast-paced nature of the software industry and the success of small agile projects, researchers and practitioners are interested in scaling agile processes to larger projects. Agile software development (ASD) has been growing in popularity for over two decades. With the success of small-scale agile transformation, organizations started to focus on scaling agile. There is a scarcity of literature in this field making it harder to find plausible evidence to identify the science behind large scale agile transformation. The objective of this paper is to present a better understanding of the current state of research in the field of scaled agile transformation and explore research gaps. This tertiary study identifies seven relevant peer reviewed studies and reports research findings and future research avenues.

Download Full-text

E-Banking Project Management

E-Banking Management ◽

10.4018/978-1-60566-252-7.ch009 ◽

2010 ◽

pp. 167-189

Author(s):

Mahmood Shah ◽

Steve Clarke

Keyword(s):

Information Technology ◽

Project Management ◽

Large Scale ◽

Business Development ◽

Small Scale ◽

Important Concept ◽

Managing Change ◽

Management Techniques ◽

Project Portfolios ◽

Large Scale Project

Project management is an important concept in business development. Often, the development of information technology or managing change will be run as projects, and managed using various well established project management techniques and tools. E-banking is often treated like a large scale project and broken into several small scale projects to manage various different aspects (called project portfolios), ranging from BPR to make the organization ready for online operations, to actual implementation of e-banking technologies.

Download Full-text

Model Simulasi Rational Unified Process (RUP) Pada Pegembagan Perangkat Lunak

Repositor ◽

10.22219/repositor.v2i4.390 ◽

2020 ◽

Vol 2 (4) ◽

pp. 485

Author(s):

Tuti Tia ◽

Ilyas Nuryasin ◽

Maskur Maskur

Keyword(s):

Software Development ◽

Simulation Model ◽

Large Scale ◽

Simulation Models ◽

Project Manager ◽

Small Scale ◽

Software Companies ◽

Unified Process ◽

Role Based ◽

Engineering Projects

Abstract Pada pengembangan perangkat lunak terdapat beberapa jenis metodologi yang dapat digunakan, salah satunya adalah Rational Unified Process (RUP). RUP merupakan salah satu jenis proses pengembangan perangkat lunak yang digunakan di berbagai perusahaan perangkat lunak. Terdapat berbagai jenis proyek pada pengembangan perangkat lunak RUP, yaitu proyek yang dibangun dari awal dan memiliki skala kecil, proyek yang memiliki skala besar dan proyek pengembangan dari sistem yang sudah dibangun sebelumnya. Setiap jenis proyek memiliki kebutuhan yang berbeda, terutama dalam penggunaan setiap peran. Pada RUP terdapat beberapa peran penting yang tidak dapat dilakukan oleh satu individu karena harus bekerja pada saat bersamaan. Pada dasarnya tujuan dari RUP adalah dapat menghasilkan perangkat lunak yang berkualitas tinggi. Hal tersebut tidak dapat tercapai apabila penggunaan peran yang kurang tepat. Penelitian ini mengusulkan jumlah peran yang dibutuhkan untuk pengembangan perangkat lunak menggunakan RUP dengan membuat model simulasi. Tujuan dari pembuatan model simulasi ini adalah untuk mengetahui peran yang sesuai berdasarkan setiap jenis proyek. Hasil dari model simulasi yaitu berupa persentase dari setiap peran yang dibutuhkan, project manager memiliki persentase terbesar dibandingkan dengan peran lainnya, yaitu sebesar 76% pada proyek skala kecil dan 60% pada proyek skala besar.AbstractIn software development there are several types of methodologies that can be used, one of which is Rational Unified Process (RUP). RUP is of software development process used in various software companies. There are various types of projects in RUP software development, small scale project, large-scale projects and re-engineering projects. Each type of project has different needs, especially in the use of each role. In RUP there are several important roles that cannot be done by an individual because they have to work at the same time. Basically the purpose of the RUP is to be able to produce high quality software. This cannot be achieved if the inappropriate role is used. This study proposes the number of roles needed for software development using RUP by creating simulation models. The purpose of simulation model is to determine the appropriate role based on each type of project. The results of the simulation model are in the form of a percentage of each role needed, the project manager has the largest percentage compared to other roles, which is 76% in small-scale projects and 60% in large-scale projects.

Download Full-text

SIMULATION MODEL FOR RATIONAL UNIFIED PROCESS (RUP) SOFTWARE DEVELOPMENT LIFE CYCLE

SISTEMASI ◽

10.32520/stmsi.v8i1.420 ◽

2019 ◽

Vol 8 (1) ◽

pp. 176

Author(s):

Tuti Karen Tia

Keyword(s):

Software Development ◽

Simulation Model ◽

Large Scale ◽

Simulation Models ◽

Small Scale ◽

Software Companies ◽

Development Life Cycle ◽

Unified Process ◽

Role Based ◽

Engineering Projects

In software development there are several types of methodologies that can be used, one of which is Rational Unified Process (RUP). RUP is of software development process used in various software companies. There are various types of projects in RUP software development, small scale project, large-scale projects and re-engineering projects. Each type of project has different needs, especially in the use of each role. In RUP there are several important roles that cannot be done by an individual because they have to work at the same time. Basically the purpose of the RUP is to be able to produce high quality software. This cannot be achieved if the inappropriate role is used. This study proposes the number of roles needed for software development using RUP by creating simulation models. The purpose of simulation model is to determine the appropriate role based on each type of project. The results of the simulation model are in the form of a percentage of each role needed, the project manager has the largest percentage compared to other roles, which is 70% in small-scale projects and 65% in large-scale projects.

Download Full-text

Large-Scale Rig for the Characterization of DCC at Sub-Atmospheric Pressure

Volume 2: Nuclear Policy; Nuclear Safety, Security, and Cyber Security; Operating Plant Experience; Probabilistic Risk Assessments; SMR and Advanced Reactors ◽

10.1115/icone2020-16662 ◽

2020 ◽

Author(s):

R. Lo Frano ◽

A. Pesetti ◽

D. Aquaro ◽

M. Olcese

Keyword(s):

Atmospheric Pressure ◽

Large Scale ◽

Fusion Reactor ◽

Scale Up ◽

Small Scale ◽

Vacuum Vessel ◽

Steam Condensation ◽

Main Components ◽

Under Construction ◽

Experimental Rig

Abstract The Direct Contact Condensation (DCC) is the main phenomenon characterizing the steam condensation. It plays an important role for the operation of Vacuum Vessel Pressure Suppression System (VVPSS) tanks, particularly for managing the Ingress of Coolant Event (determining fusion reactor overpressurization). It is safety relevant (key) system of the fusion reactor because by condensing the steam generated during such accident event allows to damp the overpressure. This paper deals with experimental and theoretical analyses of the DCC at sub-atmospheric pressure. The similitude analysis was elaborated to scale up the experimental results obtained in the reduced scale facility: similitude laws are used for the design of large experimental rig. Correlations are defined starting from the water temperature and pressure variation already obtained in the small-scale rig. Furthermore, the experimental rig and its main components accordingly designed (and under construction at the University of Pisa) allow to study at large scale the steam condensation. The testing conditions are presented and discussed.

Download Full-text

Practices of Motivators in Adopting Agile Software Development at Large Scale Development Team from Management Perspective

Electronics ◽

10.3390/electronics10192341 ◽

2021 ◽

Vol 10 (19) ◽

pp. 2341

Author(s):

Rashid Ali Khan ◽

Muhammad Faisal Abrar ◽

Samad Baseer ◽

Muhammad Faran Majeed ◽

Muhammad Usman ◽

...

Keyword(s):

Scale Development ◽

Software Development ◽

User Satisfaction ◽

Large Scale ◽

Low Cost ◽

Rapid Development ◽

Agile Software Development ◽

Agile Development ◽

Small Scale ◽

Agile Software

Agile software development methodologies have become the most popular software development methods in the last few years. These methodologies facilitate rapid development. The low cost and prioritized user satisfaction make these methodologies more attractive. These methodologies were also intended for small scale developmental teams. Therefore, challenges were encountered when these methodologies were used in large-scale development teams. This study was based on the identification of factors which were discovered in our previous study. Some of the factors included “leadership strong commitment and team autonomy”, “cooperative organizational culture”, and “team competency—agile development expertise”. A total of 147 practices were identified in this study via a systematic literature review. These practices will help practitioners and project managers to adopt agile software methodologies and encourage them to the enhance them.

Download Full-text

Agile SPI

Software Process Improvement for Small and Medium Enterprises ◽

10.4018/978-1-59904-906-9.ch009 ◽

2011 ◽

pp. 177-192 ◽

Cited By ~ 2

Author(s):

Julio A. Hurtado ◽

Francisco J. Pino ◽

Juan C. Vidal ◽

César Pardo ◽

Luís Eduardo Fernández

Keyword(s):

Software Development ◽

Process Improvement ◽

Software Industry ◽

Software Process ◽

Software Process Improvement ◽

Medium Size ◽

Development Processes ◽

Main Components

This chapter presents Agile SPI, a framework in which the main goal is to motivate small and medium size enterprises (SMEs) towards improving and certifying their software development processes. This framework was born in the SIMEP-SW project where a software process improvement model for supporting process improvement in the Colombian software industry context was built. We present Agile SPI, its origin, development, principles, architecture, main components, and the initial experiences.

Download Full-text

Large scale project organization networks and operational mechanism

2011 IEEE International Conference on Computer Science and Automation Engineering ◽

10.1109/csae.2011.5952641 ◽

2011 ◽

Author(s):

Jing Yang ◽

Sen Chen ◽

Yingwu Chen

Keyword(s):

Large Scale ◽

Project Organization ◽

Operational Mechanism ◽

Organization Networks ◽

Large Scale Project

Download Full-text

Agile SPI

Software Applications ◽

10.4018/978-1-60566-060-8.ch191 ◽

2009 ◽

pp. 3308-3324

Author(s):

Julio A. Hurtado ◽

Francisco J. Pino ◽

Juan C. Vidal ◽

César Pardo ◽

Luís Eduardo Fernández

Keyword(s):

Software Development ◽

Process Improvement ◽

Software Industry ◽

Software Process ◽

Software Process Improvement ◽

Medium Size ◽

Development Processes ◽

Main Components

This chapter presents Agile SPI, a framework in which the main goal is to motivate small and medium size enterprises (SMEs) towards improving and certifying their software development processes. This framework was born in the SIMEPSW project where a software process improvement model for supporting process improvement in the Colombian software industry context was built. We present Agile SPI, its origin, development, principles, architecture, main components, and the initial experiences.

Download Full-text