Editing Personal software process (section)

==PSP structure==
PSP training follows an evolutionary improvement approach: 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 their 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.

;Process
The input to PSP is the requirements; requirements document is completed and delivered to the engineer.

;PSP0, PSP0.1 (Introduces process discipline and measurement)
PSP0 has 3 phases: planning, development (design, code, compile, test) and a post mortem. 
A baseline is established for current process measuring: time spent on programming, faults injected/removed and size of a program.
In a post mortem, the engineer ensures all data for the projects has been properly recorded and analysed.  
PSP0.1 advances the process by adding a coding standard, a size measurement and the development of a personal process improvement plan (PIP). In the PIP, the engineer records ideas for improving his own process.

;PSP1, PSP1.1 (Introduces estimating and planning)
Based upon the baseline data collected in PSP0 and PSP0.1, the engineer estimates how large a new program will be and prepares a test report (PSP1).
Accumulated data from previous projects is used to estimate the total time.
Each new project will record the actual time spent.
This information is used for task and schedule planning and estimation (PSP1.1).

;PSP2, PSP2.1 (Introduces quality management and design)
PSP2 adds two new phases: design review and code review.  Defect prevention and removal of them are the focus at the PSP2. Engineers learn to evaluate and improve their process by measuring how long tasks take and the number of defects they inject and remove in each phase of development.
Engineers construct and use checklists for design and code reviews.
PSP2.1 introduces design specification and analysis techniques

(PSP3 is a legacy level that has been superseded by TSP.)