scholarly journals GAMIFICATION FRAMEWORK FOR SOFTWARE DEVELOPMENT PROJECT PROCESSES

2019 ◽  
Vol 2 ◽  
pp. 114
Author(s):  
Valerija Platonova ◽  
Solvita Berzisa
Keyword(s):  
Software Development ◽  
Product Quality ◽  
Positive Impact ◽  
Routine Activities ◽  
Development Project ◽  
Project Manager ◽  
Project Team ◽  
Daily Routine ◽  
Software Development Project ◽  
Quality Production

Gamification methodology has a positive impact on software development (SD) processes, contributes to better product quality production and team involvement. To show how gamification can be used to motivate the SD project team to carry out daily routine activities and document it in PM tool the gamification framework is proposed in this paper. With this gamification framework is also tried to solve project manager challenge to get actual information in PM tool entered by the project team for correct reporting of project status and process overview. A prototype of a gaming tool has been developed, which is based on Jira's app functionality and is implemented as a plugin.

Software Project Managers under the Team Software Process

2012 ◽  
pp. 115-126
Author(s):  
Marcos Ruano-Mayoral ◽  
Ricardo Colomo-Palacios ◽  
Ángel García-Crespo ◽  
Juan Miguel Gómez-Berbís
Keyword(s):  
Software Development ◽  
Software Process ◽  
Development Project ◽  
Project Managers ◽  
Project Manager ◽  
Software Project ◽  
Software Projects ◽  
Software Development Project ◽  
Team Software Process ◽  
Definition Of

Despite the clear relevance of the Information and Communications Technologies (ICT) market in world economics and the evident lack of success of software projects, organizations devote little effort to the development and maturity of the software project manager profession. This work analyzes the figure of project manager from the perspective of the Team Software Process (TSP), and it considers the required skills, attitudes and knowledge for a software development project. The basis for the study is the analysis of relevant references from the literature for their subsequent categorization into different competency concepts. The results of the analysis are compared with the contributions which the Guide to the SWEBOK® and the PMBOK® Guide models provide of the profiles of the project manager. The results indicate that the literature relating to the Team Software Process is focused on the definitions of skills and attitudes, and to a lesser extent on knowledge components. The lack of the definition of the components which comprise competency constitutes a challenge for software development organizations that use TSP, whose project managers should confront the task with full capacities, and without the help of established and recognized competencies. The current work attempts to establish the competencies for project managers identified in the literature, in the environment of the use of TSP for software development, using a study based on content analysis.

scholarly journals PERFORMANCE EVALUATION OF SOFTWARE DEVELOPMENT PROJECT TEAM

2017 ◽  
Vol 2 ◽  
pp. 118
Author(s):  
Inga Podjavo ◽  
Solvita Berzisa
Keyword(s):  
Decision Making ◽  
Performance Evaluation ◽  
Project Management ◽  
Software Development ◽  
Team Performance ◽  
Development Project ◽  
Project Team ◽  
Software Development Project ◽  
Planning Decision ◽  
Performance Demonstration

The necessity of finding the connection between the planning, decision making, actions and results create project management interest to an evaluation of the project team performance. By analyzing the team performance, determining successful projects and assessing results, members of such project will have the necessary information to avoid failures, to monitor the progress, to compare similar projects and move to defined goals. The objective of this paper is to provide guidelines for evaluation of the project team performance in the software development project. This paper summarizes measures for evaluation of the team performance, an evaluation objectives and it benefits as well as factors that may have an influence on the team performance. Demonstration example of the guideline usage has been provided.

Key Software Metrics and its Impact on each other for Software Development Projects

2016 ◽  
Vol 6 (1) ◽  
pp. 242
Author(s):  
Mridul Bhardwaj ◽  
Ajay Rana
Keyword(s):  
Software Development ◽  
Software Metrics ◽  
Development Project ◽  
Project Manager ◽  
Software Project ◽  
Team Size ◽  
Font Size ◽  
Project Duration ◽  
Software Development Project ◽  
Software Estimation

<p class="MsoNormal" style="margin: 0in 0in 10pt; text-align: justify;"><span style="line-height: 115%; font-size: 9pt; mso-bidi-font-size: 12.0pt;"><span style="font-family: Calibri;"><span style="mso-spacerun: yes;"><span style="font-size: small;"><span style="line-height: 115%; mso-bidi-font-size: 12.0pt;">Every software development project is unique and different from repeatable manufacturing process. Each software project share different challenges related to technology, people and timelines. If every project is unique, how project manager can estimate project in a consistent way by applying his past experience. One of the major challenges faced by the project manager is to identify the key software metrics to control and monitor the project execution. Each software development project may be unique but share some common metric that can be used to control and monitor the project execution. These metrics are software size, effort, project duration and productivity. These metrics tells project manager about what to deliver (size), how it was delivered in past (productivity) and how long will it take to deliver with current team capability (time and effort). In this paper, we explain the relationship among these key metrics and how they statistically impact each other. These relationships have been derived based on the data published in book “Practical Software Estimation” by International Software Benchmarking Group. This paper also explains how these metrics can be used in predicting the total number of defects. Study suggests that out of the four key software metrics software size significantly impact the other three metrics (project effort, duration and productivity). Productivity does not significantly depend on the software size but it represents the nonlinear relationship with software size and maximum team size, hence, it is recommended not to have a very big team size as it might impact the overall productivity. Total project duration only depends on the software size and it does not depend on the maximum team size. It implies that we cannot reduce project duration by increasing the team size. This fact is contrary to the perception that we can reduce the project duration by increasing the project team size. We can conclude that software size is the important metrics and a significant effort must be put during project initiation phases to estimate the project size. As software size will help in estimating the project duration and project efforts so error in estimating the software size will have significant impact on the accuracy of project duration and effort. All these key metrics must be re-calibrated during the project development life cycle. </span><strong style="mso-bidi-font-weight: normal;"></strong></span></span></span></span></p><p class="MsoNormal" style="margin: 0in 0in 10pt; text-align: justify;"> </p>

scholarly journals Key Software Metrics and its Impact on each other for Software Development Projects

2016 ◽  
Vol 6 (1) ◽  
pp. 242
Author(s):  
Mridul Bhardwaj ◽  
Ajay Rana
Keyword(s):  
Software Development ◽  
Software Metrics ◽  
Development Project ◽  
Project Manager ◽  
Software Project ◽  
Team Size ◽  
Font Size ◽  
Project Duration ◽  
Software Development Project ◽  
Software Estimation

<p class="MsoNormal" style="margin: 0in 0in 10pt; text-align: justify;"><span style="line-height: 115%; font-size: 9pt; mso-bidi-font-size: 12.0pt;"><span style="font-family: Calibri;"><span style="mso-spacerun: yes;"><span style="font-size: small;"><span style="line-height: 115%; mso-bidi-font-size: 12.0pt;">Every software development project is unique and different from repeatable manufacturing process. Each software project share different challenges related to technology, people and timelines. If every project is unique, how project manager can estimate project in a consistent way by applying his past experience. One of the major challenges faced by the project manager is to identify the key software metrics to control and monitor the project execution. Each software development project may be unique but share some common metric that can be used to control and monitor the project execution. These metrics are software size, effort, project duration and productivity. These metrics tells project manager about what to deliver (size), how it was delivered in past (productivity) and how long will it take to deliver with current team capability (time and effort). In this paper, we explain the relationship among these key metrics and how they statistically impact each other. These relationships have been derived based on the data published in book “Practical Software Estimation” by International Software Benchmarking Group. This paper also explains how these metrics can be used in predicting the total number of defects. Study suggests that out of the four key software metrics software size significantly impact the other three metrics (project effort, duration and productivity). Productivity does not significantly depend on the software size but it represents the nonlinear relationship with software size and maximum team size, hence, it is recommended not to have a very big team size as it might impact the overall productivity. Total project duration only depends on the software size and it does not depend on the maximum team size. It implies that we cannot reduce project duration by increasing the team size. This fact is contrary to the perception that we can reduce the project duration by increasing the project team size. We can conclude that software size is the important metrics and a significant effort must be put during project initiation phases to estimate the project size. As software size will help in estimating the project duration and project efforts so error in estimating the software size will have significant impact on the accuracy of project duration and effort. All these key metrics must be re-calibrated during the project development life cycle. </span><strong style="mso-bidi-font-weight: normal;"></strong></span></span></span></span></p><p class="MsoNormal" style="margin: 0in 0in 10pt; text-align: justify;"> </p>

Analisis Keberkesanan Sistem Penyelarasan Kos Projek Pembangunan Perisian Menggunakan Model Reka Bentuk Awalan COCOMO II

2012 ◽  
Author(s):  
Siti Nurkhadijah Aishah Ibrahim ◽  
Ali Selamat
Keyword(s):  
Software Development ◽  
Cost Model ◽  
Development Project ◽  
Project Manager ◽  
Design Model ◽  
Prototype Model ◽  
Economic Market ◽  
Early Design ◽  
Software Development Project ◽  
Cocomo Ii

Pada masa kini terdapat pelbagai perisian yang digunakan untuk membuat pengiraan anggaran kos projek pembangunan perisian. Kebiasaannya organisasi yang terlibat dengan projek pembangunan perisian akan menggunakan perisian tersebut untuk memudahkan mereka menganggarkan kos sesebuah projek pembangunan perisian yang dilaksanakan. Namun begitu, dengan wujudnya pelbagai model anggaran menyebabkan pengurus projek sukar menentukan model yang sesuai digunakan oleh organisasi untuk membuat pengiraan anggaran kos projek pembangunan perisian. Oleh itu, satu perisian dikenali sebagai Sistem Penyelarasan Kos Projek Pembangunan Perisian (SPKPPP) telah dibangunkan menggunakan model reka bentuk awalan yang terdapat dalam Constructive Cost Model (COCOMO) II. SPKPPP dibangunkan secara prototaip kerana model prototaip mempunyai beberapa kelebihan selain perisian dapat dibangunkan dengan cepat. Setiap model, teknik dan kaedah yang digunakan dalam SPKPPP ini telah diuji dan dapat memenuhi keperluan pengiraan anggaran kos projek pembangunan perisian dan memudahkan pengurus projek membuat pengiraan anggaran kos awalan projek pembangunan perisian yang akan dilaksanakan. Kata kunci: Constructive Cost Model (COCOMO) II, SPKPPP, anggaran, model reka bentuk awalan, prototaip Recently, there are many software tools that have been used to estimate software development project. Conventionally, most organization that involved in developing software development project used the software to ease the estimation problems. However, project manager has faced some difficulties in finding the convenient software for their needs because of the availability of many estimation software projects in the market and the cost are very expensive. In order to achieve local economic market in budgeting, this research has focused on the analysis of System Estimation of Software Development Project (SESDP) using early design model in Constructive Cost Model (COCOMO) 2.0. The software development prototype model has been used to develop the SESDP as it can be rapidly developed. At the end, each type of model, technique and method involved in the development software has been tested for estimating the measurement in latest software development project. From the analysis, the project manager has found that the tool has been easily used to estimate the early software cost development project. Key words: Constructive Cost Model (COCOMO) II, SESDP, estimation, early design model, prototype

scholarly journals A Study on Requirement Specifications and Modifications During the Software Development Life Cycle in M/S Kakunje Software Private Limited

2021 ◽  
pp. 142-161
Author(s):  
Nethravathi P. S. ◽  
P. S. Aithal
Keyword(s):  
Project Management ◽  
Software Development ◽  
Development Project ◽  
Project Manager ◽  
Second Phase ◽  
Management Process ◽  
Project Schedule ◽  
Management Software ◽  
Software Development Project ◽  
Project Management Software

Background/Purpose: In order to face the challenge of optimization and allocation of necessary requirements to complete a project with in the allocated time period, the project manager must be efficient in applying different technical skills and managerial strategies to the project management process. In order to develop a software and mobile application product, a company schedules different process as per the specified order and unique requirements. As the history of project management reminds that most of the industries started to implement this concept by observing the success of mega engineering projects because of the effective utilization of project management concept. Objective: This work is carried to understand the concepts of project management in software firms. To investigate the implementation and importance of these concepts and to know the role of project manager in managing the process in software development. Design/Methodology/Approach: Kakunje Software Private Limited, Mangalore, provides excellent and state-of-the-art customized software and hardware solutions as per the necessities of customers. In order to manage the project activities CEO, CFO and CTO all together acts as project manager. The software development project management process starts by identifying needs and recommending solutions, which can be delivered to value its stakeholders. At the second phase the actual development will begin and the developed software will be tested according to customer requirements. Findings/Results: Budgeting, cost management, finance planning etc., represented by CPM and PERT charts by using Microsoft Project and Atlassian JIRA project management software. The project resources, which are used to manage the project and allocation of technical staff are represented by histogram. With the help of Gantt Chart software development project schedule of 5 month are shown. Conclusion: To manage Kakunje business in an effective and gainful manner, the company managed overall internal and external risks of the project. By using the project management software, the company condensed the project manager’s efforts and human errors to manage multiple projects. Paper Type: Case study-based Research Analysis

Sign in / Sign up

Export Citation Format

Share Document