Managing Incremental Development: Combining Flexibility and Control

The current demand for flexible software development makes software development organizations consider iterative and incremental development approaches as alternatives to the classical waterfall software development model. This, however, may jeopardize process visibility and manageability as well as product quality. Therefore, modern software development organizations need to find ways to install flexible development processes without sacrificing project overview and control. This paper reports experiences from a real life project that used timeboxing as the basic organizing principle in an incremental and iterative design and construction process. The project’s experiences show that such a process is indeed both flexible and manageable but that it requires periodic planning and replanning, explicit concern for coordination and synchronization activities, high process discipline and organizational readiness to accept fluctuating requirements

Identifying Suitable Projects For Rapid Development: Some Proposed Selection Criteria

The use of rapid development techniques allows building high quality systems in short timeframes while reducing project costs and adding flexibility to the development process so it can be easily adapted to meet customer needs in a volatile market. In order to obtain the benefits of implementing rapid development methods, the development organization and the processes utilized need to be congruent with rapid development methodologies and techniques. A problem encountered by product development organizations is how to identify which projects are suitable for the rapid development approach. An extensive academic research about the implementation of rapid development techniques in Systems Development Life Cycle (SDLC) processes resulted in the identification of selection criteria for the determination of project suitability for rapid development methods. The selection criteria identified by this research are essential elements that must be present in every rapid development environment in order to obtain the benefits of implementing rapid development techniques

On the Adaptation of an Agile Information Systems Development Method

Little specific research has been conducted to date on the adaptation of agile information systems development (ISD) methods. This article presents the work practice in dealing with the adaptation of such a method in the ISD department of one of the leading financial institutes in Europe. Two forms of method adaptation, static adaptation and dynamic adaptation, are introduced and discussed in detail. We provide some insights plus an instrument that the ISD department studied uses to deal with the dynamic method adaptation. To enhance our understanding of the observed practice, we take into account two complementary perspectives: the engineering perspective and the socio-organizational perspective. Practical and theoretical implications of this study are discussed.Keywords: agile method; information systems development; method adaptation; method engineerin

Quality Management System Admin Module Development: A Study in the Department of Computer Science

Elevating the quality of learning is central to ensuring academic programs align with national standards. One crucial aspect of this process is the semester-based learning planning. Traditionally, the Department of Computer Science orchestrates this planning by creating separate documents for various data points, including courses, CPL (Graduate Learning Outcomes), and CPMK (Course Learning Outcomes), which are then integrated into the RPS (Semester Learning Plan) document each term. This study seeks a solution to enhance the efficiency of such data management through the development of an admin module. The system, designed using the Rapid Test Development (RAD) approach and the Laravel framework, offers a more effective data management solution, subsequently elevating the pedagogical quality of the Department of Computer Science. In conclusion, an integrated approach to data management can make a significant contribution to educational quality. Through this research, the scholarly contribution provided is the introduction of a systematic model in educational data management to boost the efficiency and effectiveness of the learning process in higher education institution

SCRUM-PSP: Embracing Process Agility and Discipline

Abstract—With the research and debates on software process, the mainstream software processes can be grouped into two categories, the plan-driven (disciplined) processes and the agile processes. In terms of the classification, personal software process (PSP) is a typical plan-driven process while SCRUM is an agile-style instance. Although they are distinct from each other per se, our research found that PSP and SCRUM may also complement each other when SCRUM provides an agile process management framework, and PSP provides the skills and disciplines that a qualified team member needs to estimate, plan and manage his/her job. This paper proposes an integrated process model, SCRUM-PSP, which combines the strengths of each. We also verified that this integrated process by adopting it into a real project environment where typical agile processes are favored, i.e. change-prone requirements, rapid development, fast delivery, etc. As a result, manageability and predictability which traditional plan-driven processes usually benefit can also be achieved. The work described in this paper is a worthy attempt to embrace both process agility and discipline. Keywords- PSP SCRUM Integratio

Rapid Software Development Life Cycle in Small Projects

Small software projects are becoming more usual nowadays. Whether a small project is conducted privately or professionally, the management of the project and its phases is much easier with proper tools and frameworks. The research target of this thesis is to find out a proper life cycle model for small software projects. This thesis is conducted for Softwarehouse, a professional division of IT services in the University of Turku. The official guide for Scrum framework is adhered in software development but when it comes to formally managing various phases of a software project (planning, design, implementation, testing, reviewing etc.) there is room for improvement. Managing software projects with a proper set of tools and procedures would be beneficial as Softwarehouse works on many projects concurrently. The intended life cycle model has to be formal and heavy enough so that the benefits of agile project management can be received. However too rigid a model can be too arduous and exhausting to use, which could result in the decrease of Softwarehouse’s production volume. Therefore the model has to be light enough to maintain rapid software development and creative atmosphere within the Softwarehouse. This thesis begins by giving outline of existing software development life cycle models and followed by relevant literary exploration. After this the research case is explained in greater detail. These give the foundation and rationale to propose a suitable model. The model is experimented empirically and reviewed by partaking personnel. The results are reviewed and discussed. Finally topics for future research are suggested

An investigation into the applicability of the RAD methodology when applied to the development of an information system

Within any software-related environment many tools, techniques and SDMs (Software Development Methodologies) can be applied to help control the software development lifecycle. The aim of this thesis is to assess the applicability of the RAD (Rapid Application Development) SDM to software development when designing an MIS (Management Information System) for Philips Components Washington. Both positive and negative characteristics of the approach were examined. This thesis provides detailed conclusions on each of the identified characteristics together with more general analysis of the use of SDMs. Research into several SDMs has been carried out in parallel with the development of the MIS, however the RAD SDM was predominantly used throughout the project. This study has been carried out through the analysis of information requirements around the Philips factory with an aim to providing one central system by which all production figures can be collated and reported upon. Prior to this study no standards for the choice of SDM were in place for software design, however previous SDMs used tended to be more traditional and structured in nature. Through this study, additional areas of analysis have been identified in order to further investigate the RAD SDM. Recommendations have also been provided for any future software projects that Philips may undertake with the application of the RAD methodology