What is Personal and Team Software Process ?

Personal Software Process :

The Personal Software Process (PSP) is a structured software development process that is intended to help software engineers better understand and improve their performance by tracking their predicted and actual development of code. 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.

The PSP process consists of a set of methods, forms, and scripts that show software engineers how to plan, measure, and manage their work. By using the PSP concepts and methods in their work, individuals in almost any technical field can improve their estimating and planning skills, make commitments that they can meet, manage the quality of their work, and reduce the number of defects in their products. The PSP helps software engineers to:
  • Improve their estimating and planning skills.
  • Make commitments they can keep.
  • Manage the quality of their projects.
  • Reduce the number of defects in their work.

PSP training follows an evolutionary improvement approach, which are divided in four levels : 

PSP 0.0 & PSP 0.1  : Introduces process discipline and measurement

PSP 1.0 & PSP 1.1 : Introduces estimating and planning

PSP 2.0 & PSP 2.1 : Introduces quality management and design

Each level contains all the activities in the prior level plus some new ones. An engineer learning to integrate the PSP into his or her process begins at the first level – PSP0 – and progresses in process maturity to the final level – PSP2.1. Each Level has detailed scripts, checklists and templates to guide the engineer through required steps and helps the engineer improve her own personal software process. Humphrey encourages proficient engineers to customize these scripts and templates as they gain an understanding of their own strengths and weaknesses.

Team Software Process :

In combination with the personal software process (PSP), the team software process (TSP) provides a defined operational process framework that is designed to help teams of managers and engineers organize projects and produce software products that range in size from small projects of several thousand lines of code (KLOC) to very large projects greater than half a million lines of code. The TSP is intended to improve the levels of quality and productivity of a team's software development project, in order to help them better meet the cost and schedule commitments of developing a software system. 

The Team Software Process (TSP) guides engineering teams that are developing software-intensive products. Using TSP helps organizations establish a mature and disciplined engineering practice that produces secure, reliable software in less time and at lower costs. The TSP was introduced in 1998, and builds upon the foundation of PSP to enable engineering teams to build software-intensive products more predictably and effectively.

In practice, PSP skills are used in a TSP team environment. TSP teams consist of PSP-trained developers who volunteer for areas of project responsibility, so the project is managed by the team itself. Using personal data gathered using their PSP skills; the team makes the plans, the estimates, and controls the quality. Using PSP process methods can help TSP teams to meet their schedule commitments and produce high quality software. Successfully meeting schedule commitments can be attributed to using historical data to make more accurate estimates, so projects are based on realistic plans – and by using PSP quality methods, they produce low-defect software, which reduces time spent on removing defects in later phases, such as integration and acceptance testing.



Next Topic :

No comments:

Post a Comment