Personal Software Process was proposed by Watts Humphrey in the 90s. This method focus on the self development and excellence of software engineers by estimating and measuring time and resources that are use for tasks. Although this is an about 30 years old method it is still a valuable guide for programmers.

1. Personal Software Process
Zsolt Tóth
zsolt.toth@coeus-consulting.eu
Coeus Consulting
18.06.2020.
Zsolt Toth (Coeus Consulting) Personal Software Process 18.06.2020. 1 / 12

2. Introduction
Personal Software Process
Watts Humphrey (1990s)
Team Software Process
Capability Maturity Model
Quality of product
test–find–fix
early finding, lean
prevent defects
your work, responsibility
Personal performance
planning
time measuring
job size
quality of work
analyze & improve
Zsolt Toth (Coeus Consulting) Personal Software Process 18.06.2020. 2 / 12

3. Introduction
Personal Software Process
Personal Waterfall Model
Scripts
Measures, forms
Standards
Zsolt Toth (Coeus Consulting) Personal Software Process 18.06.2020. 3 / 12

4. Introduction
Process Planning
Zsolt Toth (Coeus Consulting) Personal Software Process 18.06.2020. 4 / 12

5. Phases
Conceptual Design
Entry Criteria
Problem Description
Size estimating template
Historical estimate
Tasks
Planning
Cost estimation
PROBE Method
Proxy–based Estimation
Personal history
Similar Task → Similar Cost
Task "database"
size VS→VL
category
Effort
line of code
time (min, fuzzy min)
Zsolt Toth (Coeus Consulting) Personal Software Process 18.06.2020. 5 / 12

6. Phases
PROBE Method
Category Very Small Small Medium Large Very Large
Computation 30 45 100 200 600
I/O 20 35 60 120 430
DAO 30 45 90 180 500
Web End Point 30 45 100 200 600
Zsolt Toth (Coeus Consulting) Personal Software Process 18.06.2020. 6 / 12

7. Phases
Development & Measures
Time
Only working + interrupts
No breaks, phone calls etc.
Size
Lines of code (base, added,
modified, reused, etc.)
Joins in SQL
Server installation
Any other
Be consistent!
Quality
Defects you injected
Related to
requirements, specification
design, implementation
documentation
Metrics
Defect Density
Review Rate
Development Time Ratios
1:1 design–to–coding
1:2 design review–to–design
1:2 code review – to coding
Zsolt Toth (Coeus Consulting) Personal Software Process 18.06.2020. 7 / 12

8. Phases
Postmortem
AKA
lessons learned
debriefing
retrospective
Analyze project elements
successful
okay
unsuccessful
Feed backs
Colleagues
Code review in team
Estimation vs Actual Cost
accounting
Process Improvement Proposals
Huge time cost and
commitment
Elements
situation / problem
proposed solution
steps
benefits
risks, challenges
Zsolt Toth (Coeus Consulting) Personal Software Process 18.06.2020. 8 / 12

9. Phases
PSP Introduction
Zsolt Toth (Coeus Consulting) Personal Software Process 18.06.2020. 9 / 12

10. Discussion
Other Methodologies
Carnegie Mellon University – SEI
Personal Software Process
individual skills
discipline
Team Software Process
built upon PSP
team performance
Capability Maturity Model
organization level
Agile Methodologies
Popular, buzzword
Set of principles
"Continuous attention to
technical excellence and
good design enhances
agility."
"At regular intervals, the
team reflects on how to
become more effective,
then tunes and adjusts its
behavior accordingly."
Rong, Guoping, Dong Shao, and He Zhang. "SCRUM-PSP:
Embracing process agility and discipline." 2010 Asia Pacific Software
Engineering Conference. IEEE, 2010.
Zsolt Toth (Coeus Consulting) Personal Software Process 18.06.2020. 10 / 12

11. Discussion
Personal Experience
I barely work on a single task.
tons of interrupts
multitasking
Time
net
gross
elpased
Simple tasks may take
serious time.
Not only for software
development!
Personal Quality
Management sometimes.
This presentation
Est: 1 day = 8h gross
Net: 3h 30min
Review: 15min
Defects: 20
Zsolt Toth (Coeus Consulting) Personal Software Process 18.06.2020. 11 / 12

12. Discussion
Thank you for your attention!
Zsolt Toth (Coeus Consulting) Personal Software Process 18.06.2020. 12 / 12