PSP Performance Analysis Report

The Personal Software Process (PSP) is a structured software development process that is intended to help software engineers understand and improve their performance, by using a disciplined, data-driven procedure. The PSP was created by Watts Humphrey to apply the underlying principles of the Software Engineering Institute’s (SEI) Capability Maturity Model (CMM) to the software development practices of a single developer. It gives software engineers the process skills necessary to work on a Team Software Process (TSP) team. PSP training includes eight assignments in two courses – PSP Fundamentals and PSP Advanced. The report includes final analysis of all the data that was gathered during the training

Team-oriented process programming

Team-oriented process programming promises to provide significant support for the planning, directing, and controlling of software engineering projects. In this paper we apply process programming to software engineering teams and show how this can provide powerful new capabilities for the management of software projects. We identify key issues which must be addressed to apply process programming to teams, and present our vision for team-oriented process programming

Implementation of Software Process Improvement Through TSPi in Very Small Enterprises

This article shows an experience in a very small enterprise related to improving software quality in terms of test and process productivity. A customized process from the current organizational process based on TSPi was defined and the team was trained on it. The pilot project had schedule and budget constraints. The process began by gathering historical data from previous projects in order to get a measurement repository. Then the project was launched and some metrics were collected. Finally, results were analyzed and the improvements verified

Evaluating the Impact of Critical Factors in Agile Continuous Delivery Process: A System Dynamics Approach

Continuous Delivery is aimed at the frequent delivery of good quality software in a speedy, reliable and efficient fashion – with strong emphasis on automation and team collaboration. However, even with this new paradigm, repeatability of project outcome is still not guaranteed: project performance varies due to the various interacting and inter-related factors in the Continuous Delivery 'system'. This paper presents results from the investigation of various factors, in particular agile practices, on the quality of the developed software in the Continuous Delivery process. Results show that customer involvement and the cognitive ability of the QA have the most significant individual effects on the quality of software in continuous delivery

The Importance of Conflict Resolution Techniques in Autonomous Agile Teams

Today, software companies usually organize their work in teams. Social science research on team development has shown that for a team to reach a productive and autonomous stage, it has to be able to manage internal conflicts and disagreements efficiently. To better facilitate the team development process, we argue that software engineers' needs additional training in negotiation skills and conflict resolution. In this position paper, we outline ideas for what aspects to consider in such training. As an example, we argue that a majority of the conflicts originate from team-level factors and that they, therefore, should be managed on the team-level instead of in relation to dyads.Comment: Accepted at 1st International Workshop on Autonomous Teams (A-TEAMS), 201

GOES-R Algorithms: A Common Science and Engineering Design and Development Approach for Delivering Next Generation Environmental Data Products

GOES-R, the next generation of the National Oceanic and Atmospheric Administration’s (NOAA) Geostationary Operational Environmental Satellite (GOES) System, represents a new technological era in operational geostationary environmental satellite systems. GOES-R will provide advanced products that describe the state of the atmosphere, land, oceans, and solar/ space environments over the western hemisphere. The Harris GOES-R Ground Segment team will provide the software, based on government-supplied algorithms, and engineering infrastructures designed to produce and distribute these next-generation data products. The Harris GOES-R Team has adopted an integrated applied science and engineering approach that combines rigorous system engineering methods, with modern software design elements to facilitate the transition of algorithms for Level 1 and 2+ products to operational software. The Harris Team GOES-R GS algorithm framework, which includes a common data model interface, provides general design principles and standardized methods for developing general algorithm services, interfacing to external data, generating intermediate and L1b and L2 products and implementing common algorithm features such as metadata generation and error handling. This work presents the suite of GOES-R products, their properties and the process by which the related requirements are maintained during the complete design/development life-cycle. It also describes the algorithm architecture/engineering approach that will be used to deploy these algorithms, and provides a preliminary implementation road map for the development of the GOES-R GS software infrastructure, and a view into the integration of the framework and data model into the final design

Guidelines Towards Better Participation of Older Adults in Software Development Processes using a new SPIRAL Method and Participatory Approach

This paper presents a new method of engaging older participants in the process of application and IT solutions development for older adults for emerging IT and tech startups. A new method called SPIRAL (Support for Participant Involvement in Rapid and Agile software development Labs) is proposed which adds both sustainability and flexibility to the development process with older adults. This method is based on the participatory approach and user empowerment of older adults with the aid of a bootstrapped Living Lab concept and it goes beyond well established user-centered and empathic design. SPIRAL provides strategies for direct involvement of older participants in the software development processes from the very early stage to support the agile approach with rapid prototyping, in particular in new and emerging startup environments with limited capabilities, including time, team and resources