Team Software Process (TSPI) Web-Based Support Tool

One of the goals as a system or software developer that need to be achieved is to produce a product or system that can be considered as a high-level quality of a product. To help the developer produce a good quality of a product, a tool that will help them make their work easier and efficient is needed. TSPi Tool is one of the methods that can be used by the developer to plan their project, record the project progress, record defect and solve the defects. Currently, FCSIT students who're taking the Software Engineering and Laboratory are using the TSPi Support Tool (Excel Version). However, there are problems exists such as time-consuming which affects the progress of the project. The proposed solution for arising problems was the Team Software Process (TSPi) Tool Web-Based System, a web-based management system to manage and monitor the progress of the product development.

The Adoption of Agile Software Methodology with Team Software Process (TSPI) Practices in the Software Engineering Undergraduate Course

In computer science, software engineering courses expose the undergraduate students to both the technical and methodological aspects of software development. The traditional software development methods and techniques represent a huge proportion of the courses and hence contribute an essential part of software engineering students’ development process. This plan-driven development is dependent on a set of predefined phases and ongoing documentation which found to be problematic; such as time-consuming, slipped requirements and complicated processes. The main aim of this paper is to study and review the adoption of Agile Software Methodology and Team Software Process (TSPi) practices in the undergraduate course focus on software development. The framework and course plan will be designed to apply and observe the implementation. Furthermore, this study will help to gather the teams’ viewpoint regarding the importance of Agile and TSPi practices in handling small projects with real clients.

Cuspe: propuesta ágil para la construcción de software basada en TSP [Cuspe: Agile approach for software development based on TSP]

Resumen El objetivo principal de este artículo es aportar a la forma de trabajo de las empresas de la industria de software en Nariño mediante una propuesta metodológica ágil basada en Team Software Process (TSP). Este trabajo se desarrolló bajo el paradigma cuantitativo, con un enfoque empírico-analítico de tipo descriptivo-propositivo. La población objeto de estudio fueron las metodologías para construir software basada en equipos de trabajo, de las que se seleccionó de manera intencional TSP. Como resultado, se estableció que el nivel de agilidad que posee TSP corresponde al 79.25%. Así mismo, se diseñó Cuspe, como una propuesta para intervenir los principios del manifiesto ágil que presentan el menor nivel de cumplimiento en TSP. El trabajo permite concluir que la propuesta Cuspe basada en TSP logra incrementar el nivel de agilidad de la metodología y busca la entrega temprana y frecuente de software con valor, a través del trabajo y compromiso de personas motivadas; y consigue medir el progreso. Palabras Clave: Construcción de software, Manifiesto por el Desarrollo Ágil de Software, Team Software Process Abstract The main goal of this article is to support Nariño’s’ Software industry’s way of work through a methodological proposal based on Team Software Process (TSP). This work was carried out under a quantitative paradigm and a descriptive-propositional-based empirical-analytical approach. The object populations were the methodologies for building software based on work teams, in which TSP was intentionally chosen. As a result, it was set that TSP’s level of agility reached 71.25%. Furthermore , It was designed Cuspe as an proposal in order to intervene the principles of the Agile Manifesto which shows the lowest level of accomplishment regarding TSP. This work allows concluding that the Cuspe proposal based on TSP increases the level of methodology’s agility and leads to an early and frequent valuable software production through the work and compromise of motivated people, and also progress measurement. Keywords: Manifest for Agile Software Development, Software Development, Team Software Process.

Towards an Integrated Personal Software Process and Team Software Process Supporting Tool

Personal Software Process (PSP) and Team Software Process (TSP) have been developed and used to help individual developers and teams make high-quality products through improving their personal and team software development processes. For the PSP and TSP practices, data collection and analysis of software metrics need to be done at fine-grained levels. These tasks are not trivial, requiring tool support. This chapter aims to discuss issues to building such a tool, and introduce our on-going endeavor towards an integrated PSP and TSP supporting tool. In particular, features of sensor-based automated data collection for PSP, utilization of Six Sigma techniques into PSP and TSP activities, and incorporation of electronic process guide will be paid attention.

Managing Software Projects with Team Software Process (TSP)

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)

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.

Software Project Managers under the 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.

Team Software Process in GSD Teams

Distributed software development is becoming the norm for the software industry today as an organizational response to globalization and outsourcing tendencies. In this new environment, centralized models for software development team building models have to be reanalyzed. Team Software Process (TSP) guides engineering teams in developing software-intensive products and is intended to improve the levels of quality and productivity of a team’s software development project. In this paper, the authors assess the difficulty of using TSP in distributed software development environments. The objective of this assessment is twofold; firstly, know the general difficulty for using TSP in these environments, and secondly, know the caveats to be addressed in future software development team building models designed specifically for distributed environments.