Why software projects escalate: The importance of project management constructs

2003 ◽  
Vol 50 (3) ◽  
pp. 251-261 ◽  
Author(s):  
M. Keil ◽  
A. Rai ◽  
J.E. Cheney Mann ◽  
G.P. Zhang
Author(s):  
Aravindhan K

Cost estimation of software projects is risky task in project management field. It is a process of predicting the cost and effort required to develop a software applications. Several cost estimation models have been proposed over the last thirty to forty years. Many software companies track and analyse the current project by measuring the planed cost and estimate the accuracy. If the estimation is not proper then it leads to the failure of the project. One of the challenging tasks in project management is how to evaluate the different cost estimation and selecting the proper model for the current project. This paper summarizes the different cost estimation model and its techniques. It also provides the proper model selection for the different types of the projects.


Author(s):  
Muhammad Aliyya Ilmi ◽  
Fajar Pradana ◽  
Widhy Hayuhardhika Nugraha Putra

Reducing the risk of failure in working on software projects is one of the successes for the company. It can be done by implementing project planning management properly. One important aspect of project management planning is scheduling. Scheduling includes recording human resources and tasks in the project. The Kanban method is one of the methods used to overcome problems in controlling project schedules. This study aims to develop a project scheduling system that applies the Kanban method. In this research, project management and scheduling system will be developed using the Kanban method. This system expected to be able to assist companies in handling projects. Kanban was chosen because it can easily respond to project changes, easily implemented, and company needs. In this study, unit testing was performed on the system's three main features and tested the validity of the system's 49 functional requirements. The usability test produces a value of 76. Based on the validation and usability test results, it can be concluded that the system is included in the acceptable category.


2014 ◽  
Vol 9 (2) ◽  
pp. 101
Author(s):  
Alusyanti Primawati ◽  
Dewi Mustari

The software is an intermediary between system hardware computer with user as human. Based on the emerging software projects because of the importance of the functions already affects many functions in various aspects. Software projects that have become this need ultimately require management actions to manage the process in the project. Project management is necessary for the success of the project. Bereau Information System PT. X is one part of a company that provides software for functional PT. X. Analysis results from the concept of software project management information systems Bureau at PT. X when the process of designing application systems information accounting PT. X aims to answer how concept of project management Information Systems Bureau in designing the Accounting Information System applications. The methods used in this research is the study of the library with a general empirical approach based on experience and theories related to project management especially in software projects. The conclusions obtained that the activity of the management software on System Information Bureau is in compliance with the application of existing theory, but science is constantly evolving so as to do the development management activities after conducting evaluation regularly for the maintenance of long-term software project.


2013 ◽  
pp. 84-117
Author(s):  
Salmiza Saul Hamid ◽  
Mohd Hairul Nizam Md Nasir ◽  
Shamsul Sahibuddin ◽  
Mustaffa Kamal Mohd Nor

Despite the widespread use of sound project management practices and process improvement models over the last several years, the failure of software projects remains a challenge to organisations. As part of the attempt to address software industry challenges, several models, frameworks, and methods have been developed that are intended to improve software processes to produce quality software on time, under budget, and in accordance with previously stipulated functionalities. One of the most widely practised methods is the Team Software Process (TSP). The TSP was designed to provide an operational framework for establishing an effective team environment and guiding engineering teams in their work. This chapter provides an overview of the TSP and its associated structures and processes. It also highlights how the TSP operational framework can assist project manager and software development team to deliver successful projects by controlling and minimizing the most common software failure factors. Comparative analysis between the TSP and conventional project management has also been presented. Additionally, the results of TSP implementation in industrial settings are highlighted with particular reference to scheduling, quality, and productivity. The last section indicates additional advantages of TSP and comments on the future of TSP in the global software development project.


Author(s):  
Subhas C. Misra ◽  
Vinod Kumar ◽  
Uma Kumar

Successful software systems development is a delicate balance among several distinct factors (Jalote, 2002) such as enabling people to grow professionally; documenting processes representing the gained experiences and knowledge of the organization members; using know how to apply the suitable processes to similar circumstances; and refining processes based on achieved experience. Software projects have two main dimensions: engineering and project management. The engineering dimension concerns the construction of a system, and focuses mainly on issues such as how to build a system. The project management dimension is in charge with properly planning and controlling the engineering activities to meet project goals for optimal cost, schedule, and quality. For a project, the engineering processes specify how to perform activities such as requirement specification, design, testing, and so on. The project management processes, on the other hand, specify how to set milestones, organize personnel, manage risks, monitor progress, and so on (Jalote, 2002). A software process may be defined as “a set of activities, methods, practices, and transformations that people use to develop and maintain software, and the associated products and artifacts.”1 This is pictorially depicted in Figure 1 (Donaldson & Siegel, 2000).


Author(s):  
Roy Gelbard ◽  
Jeffrey Kantor ◽  
Liran Edelist

This study proposes and prototypes a model that integrates these three aspects of software projects by automatically mapping SE objects and accounting–costing objects into PM objects. To validate the feasibility of the model and without loss of generality, it is demonstrated using former research platform focused on conversion of data flow diagrams (DFD), which are actually full enterprise set of use cases diagrams reflecting entire system-software project into Gantt charts.


2020 ◽  
Vol 13 (36) ◽  
pp. 3785-3800
Author(s):  
Kamal Uddin Sarker ◽  

Objectives: This research addresses the causal relationship among processes, tasks, resources, and stakeholders of the software projects to improve the success rate that is 31% only now (CHAOS report 2019). Methods: A software project management framework is developed based on the findings of an empirical study on recent commonly used methodologies and root cause analysis on the reasons for project failure. The causeeffect relationship is prioritized by Structural Equation Modeling (SEM) to develop the Explicit Specification Framework (ESF). The framework is tied to the pinpointing with ontology for formal presentation, descriptive logic for unambiguous information specification, and ikigai for decision-making.Findings: The proposed framework is evaluated by a group of experts and their average scope is evaluated by a group comparison mechanism called Grey Rational Analysis (GRA). The evaluation process considered 6 parameters and compared it with 4 commonly used project management approaches. The highest GRA rank is found for the average of six distinct parameters though it is comparatively more complex for explicit documentation. The three-layer architecture of ESF remarks on roles, functions, and respective stakeholders in each layer presented by a comprehensive comparison study with literature and found that it enhances formal practice, sustainability, and management capability. ESF is easy to implement for distributed project management and improving automation facilities in the software industries.Novelty/Application: Artificial intelligence, the Internet of things, and big data would be common elements of a software project and ESF would meet the demand for project information specification, management, and control. Keywords: Software Project Management; Software Quality Control; methodology; multi- criteria decision making; structural educational modeling; ontology


2020 ◽  
Vol 6 (3) ◽  
pp. 27-34
Author(s):  
E.J. Robles Gómez ◽  
J.A. Flores Lara ◽  
J.C. Ontiveros Neri

El juego getKanban es una herramienta para enseñar la metodología Kanban y SCRUM de una manera divertida. Facilita la enseñanza de la gestión de proyectos de software a través de un juego de mesa, donde los jugadores aprenden a formular estrategias de gestión de proyectos y las implementan para elaborar proyectos de calidad en tiempo y forma. El presente artículo muestra los resultados de la implementación del juego en una institución educativa de nivel superior, con alumnos de Ingeniería en Sistemas Computacionales de octavo semestre. Se puede apreciar que al utilizar este juego ayuda de manera efectiva a la enseñanza de Kanban y SCRUM, para la gestión de proyectos de software. Por lo cual se recomienda poder implementar este tipo de juegos como estrategia didáctica para la enseñanza/aprendizaje de Ingeniería de Software aplicada a la Gestión de Proyectos de Desarrollo de Software. The game Kanban is a tool to teach the methodology in a fun way. It facilitates the teaching of software project management through where players learn to formulate strategies and implement them to develop quality projects on time Delivery. This article shows the results of the implementation of the game in an educational institution of higher level, with students of Computer Systems Engineering eighth semester. It can be seen that by using this game it helps in an effective way to teach Kanban for the management of software projects. Therefore, it is recommended to be able to implement this type of games as a didactic strategy for the teaching / learning of Software Engineering applied to the Management of Software Development Projects


Author(s):  
Kitti Photikitti ◽  
Kitikorn Dowpiset ◽  
Jirapun Daengdej

It has been well-known that the chance of successfully delivering a software project within an allocated time and budget is very low. Most of the researches in this area have concluded that “user's requirements” of the systems is one of the most difficult risks to deal with in this case. Interestingly, until today, regardless of amount of effort put into this area, the possibility of project failure is still very high. The issue with requirement can be significantly increased when developing an artificial intelligence (AI) system, where one would like the systems to autonomously behave. This is because we are not only dealing with user's requirements, but we must also be able to deal with “system's behavior” that, in many cases, do not even exist during software development. This chapter discusses a preliminary work on a framework for risk management for AI systems development projects. The goal of this framework is to help project management in minimizing risk that can lead AI software projects to fail due to the inability to finish the projects on time and within budget.


Sign in / Sign up

Export Citation Format

Share Document