Cost of Quality (COQ)
Introduction
The personal software process, PSP, is a set of disciplined practices for time management and improvement of the personal productivity of programmers or software engineers, in system development and maintenance tasks, by monitoring predicted performance versus actual performance. It is aligned and designed for use in organizations with CMMI or ISO 15504 process models. It was proposed by Watts Humphrey in 1995 and was aimed at students. Starting in 1997 with the launch of the book "An introduction to the Personal Software Process" it is now aimed at junior engineers.
With PSP, software engineers can acquire the skills necessary to work on a TSP team software process.
It can be considered as the personal work guide for software engineers in organizations that use a CMMI model with a level of maturity or process capability that involves qualitative measurement and process improvement.
One of the biggest problems it has is the large amount of data that must be collected. The PSP is obsessed with collecting data and preparing tables. The PSP addresses the set of key process areas that a developer must manage when working individually.
Goals
PSP aims to train software engineers with disciplined methods to improve their personal software development. PSP helps developers:
• - Improve your estimating and planning skills.
• - Make commitments that can be fulfilled.
• - Manage the quality of your processes.
• - Reduce the number of defects in your products.
Guys
PSP training follows an evolutionary improvement methodology: whoever begins to integrate PSP into their process begins at level PSP0 and progresses until reaching level PSP2.1, which is the maximum level of maturity.
Each level has detailed scripts, checklists and templates. Humphrey, creator of the methodology, encourages experienced engineers to customize them so they can increase understanding of their strengths and weaknesses.
The input of PSP is the requirements; The requirements document is completed and delivered to the engineer.
PSP0 has 3 phases: planning, development (design, coding, testing) and a .