Software Project Managers under the Team Software Process

2010 ◽  
Vol 1 (1) ◽  
pp. 42-53 ◽  
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 ◽  
Information And Communications Technologies ◽  
Software Projects ◽  
Software Development Project ◽  
Team Software Process

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.

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.

Managing Software Projects with Team Software Process (TSP)

2013 ◽  
pp. 84-117
Author(s):  
Salmiza Saul Hamid ◽  
Mohd Hairul Nizam Md Nasir ◽  
Shamsul Sahibuddin ◽  
Mustaffa Kamal Mohd Nor
Keyword(s):  
Project Management ◽  
Software Development ◽  
Management Practices ◽  
Software Process ◽  
Development Project ◽  
Software Projects ◽  
Engineering Teams ◽  
Software Development Project ◽  
Software Failure ◽  
Team Software Process

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.

Managing Software Projects with Team Software Process (TSP)

2011 ◽  
pp. 149-182
Author(s):  
Salmiza Saul Hamid ◽  
Mohd Hairul Nizam Md Nasir ◽  
Shamsul Sahibuddin ◽  
Mustaffa Kamal Mohd Nor
Keyword(s):  
Project Management ◽  
Software Development ◽  
Management Practices ◽  
Software Process ◽  
Development Project ◽  
Software Projects ◽  
Engineering Teams ◽  
Software Development Project ◽  
Software Failure ◽  
Team Software Process

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.

Managing Software Projects with Team Software Process (TSP)

2014 ◽  
pp. 1550-1583
Author(s):  
Salmiza Saul Hamid ◽  
Mohd Hairul Nizam Md Nasir ◽  
Shamsul Sahibuddin ◽  
Mustaffa Kamal Mohd Nor
Keyword(s):  
Project Management ◽  
Software Development ◽  
Management Practices ◽  
Software Process ◽  
Development Project ◽  
Software Projects ◽  
Engineering Teams ◽  
Software Development Project ◽  
Software Failure ◽  
Team Software Process

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.

scholarly journals ROI Estimation in a Scrum Project: A case study

10.29007/nqq6 ◽  
2019 ◽  
Author(s):  
Rita Cortés ◽  
Fulvio Lizano
Keyword(s):  
Software Development ◽  
Return On Investment ◽  
Investment Decisions ◽  
Development Project ◽  
Project Managers ◽  
Future Research ◽  
Software Project ◽  
Software Development Project ◽  
Financial Metrics

Financial metrics are necessary to inform decisions about the beginning or continuity of a software development project to justify investments. This research discuses initial ROI (Return on Investment) estimates in a software project using Scrum and how to analyze variations in the initial calculations to make return on investment decisions during partial deliveries of the product. The case study included a survey, a review of documentation, two focus group sessions, and an exercise involving application of the proposed technique. Twenty-four professionals participated, of which 4 were Scrum trainers (17%), 4 were officials of the company where the estimation technique was applied (17%), and 16 were project managers of domestic and foreign software development companies (66%), all of whom had experience in project management. This study provides elements to be considered in future research on ROI calculation in projects using Scrum, and can be used as a guide to estimate and review financial metrics during the execution of an actual project.

AN INTEGRATED APPROACH TO FORMULATE A VALUE-BASED SOFTWARE PROCESS TAILORING FRAMEWORK

2016 ◽  
Vol 78 (12-3) ◽  
Author(s):  
Noor Azura Zakaria ◽  
Suhaimi Ibrahim ◽  
Mohd Naz’ri Mahrin
Keyword(s):  
Decision Making ◽  
Software Development ◽  
Software Process ◽  
Integrated Approach ◽  
Development Project ◽  
Software Project ◽  
Systematic Method ◽  
Software Development Project ◽  
A Value ◽  
Process Tailoring

Software process tailoring is an approach to customise the existing software development process or model that able to meet the software project’s needs. Software development project is unique and identical from one and another whereby the practices and decision should not be equally treated. Software process tailoring requires knowledge and intuition to make decision such as factors involved in the software project, selection of the suitable software process elements and tailoring operations. Software process tailoring practices focusing more on project characteristics factors and employs ad hoc approach in making the decision. In the absent of value-based factors and systematic method in software process tailoring, subjectivity is embedded in decision making process and the software development project suffers from satisfying the stakeholder. This study presents an integrated approach to formulate a Value-Based Software Process Tailoring Framework (VBSPTF) to overcome this problem. The framework is a combination of value-based factors, MoSCoW rules, Quality Functional Deployment (QFD), Activity-Based Costing (ABC), Priority Map, Value Index and Value Graph. This study perhaps can contribute to the software process tailoring practitioners to be exposed with a systematic method to conduct software process tailoring as well as improving the practices and reducing subjectivity in decision making.

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>

Automated Framework for Software Process Model Selection Based on Soft Computing Approach

2017 ◽  
pp. 395-418
Author(s):  
Swati Dhingra ◽  
Mythili Thirugnanam ◽  
Poorvi Dodwad ◽  
Meghna Madan
Keyword(s):  
Software Engineering ◽  
Model Selection ◽  
Software Development ◽  
Process Model ◽  
Development Project ◽  
Project Managers ◽  
Software Project ◽  
Rule Engine ◽  
Software Development Project ◽  
Software Companies

Software engineering is an engineering approach for software development. It is a discipline whose aim is the production of fault-free, delivered on-time and within budget software that satisfies the user's needs. Software engineering principles need to be followed to ensure a successful software development project. Within organizations that are involved in software development, the challenge is to select the appropriate process model for the software project. The objective of this chapter is to determine the factors which influence the process model selection. This chapter presents an automated framework for selection of process model using fuzzy-based rule engine and to bring more accuracy for choice of process model, J-48 decision tree was used considering factors as inputs. The user has to give characteristic value of the prioritized factor as input and on the basis of the rules, model is anticipated. The developed framework will be profitable for project managers, experts and venture pioneers in software companies.

Automated Framework for Software Process Model Selection Based on Soft Computing Approach

2021 ◽  
pp. 1367-1390
Author(s):  
Swati Dhingra ◽  
Mythili Thirugnanam ◽  
Poorvi Dodwad ◽  
Meghna Madan
Keyword(s):  
Software Engineering ◽  
Model Selection ◽  
Software Development ◽  
Process Model ◽  
Development Project ◽  
Project Managers ◽  
Software Project ◽  
Rule Engine ◽  
Software Development Project ◽  
Software Companies

Software engineering is an engineering approach for software development. It is a discipline whose aim is the production of fault-free, delivered on-time and within budget software that satisfies the user's needs. Software engineering principles need to be followed to ensure a successful software development project. Within organizations that are involved in software development, the challenge is to select the appropriate process model for the software project. The objective of this chapter is to determine the factors which influence the process model selection. This chapter presents an automated framework for selection of process model using fuzzy-based rule engine and to bring more accuracy for choice of process model, J-48 decision tree was used considering factors as inputs. The user has to give characteristic value of the prioritized factor as input and on the basis of the rules, model is anticipated. The developed framework will be profitable for project managers, experts and venture pioneers in software companies.

Sign in / Sign up

Export Citation Format

Share Document