Introduction To PSP and TSP: Personal Software Process For Engineers: Part I
Introduction To PSP and TSP: Personal Software Process For Engineers: Part I
SM
Lecture Topics
The need for change
PSPSM and TSPSM principles and objectives
What is the TSP?
The need for management support
What is the PSP and how does it help?
Course results
Personal Software Process, PSP, Team Software Process, and TSP are service marks
of Carnegie Mellon University.
SM
January 2006
January 2006
Size in KLOC
10,000,000
1,000,000
100,000
10,000
1,000
100
10
1
19
60
19
65
19
70
19
75
19
80
19
85
19
90
19
95
20
00
Years
2006 by Carnegie Mellon University
January 2006
Moores Law:
2X in 18 months
10X in 5 years
People
6
12
25
40
+250
+500
January 2006
January 2006
January 2006
January 2006
Management Support -1
The initial TSP objective is to convince management to let
your team be self directed.
A self-directed team
sets its own goals
establishes its own roles
decides on its own development strategy
defines its own processes
develops its own plans
measures, manages, and controls its own work
Self-directed teams do the best work.
January 2006
Management Support -2
Management will support you as long as you
strive to meet their needs
provide regular reports on your work
convince them that your plans are sound
do quality work
respond to changing needs
come to them for help when you have problems
January 2006
Management Support -3
Self-directed teams are a bargain.
Management will agree to your managing your own work
as long as they believe that you are doing a superior job.
To convince them of this, you must
maintain precise and accurate plans
measure and track your work
regularly show management that you are doing superior
work
The PSP shows you how to do this.
January 2006
PSP Principles -1
The quality of a software system is determined by the quality
of its worst components.
The quality of a software component is governed by the
individual who developed it.
The quality of a software component is governed by the
quality of the process used to develop it.
The key to quality is the individual developers skill,
commitment, and personal process discipline.
January 2006
PSP Principles -2
As a software professional, you are responsible for your
personal process.
You should measure, track, and analyze your work.
You should learn from your performance variations.
You should incorporate lessons learned into your personal
practices.
January 2006
January 2006
January 2006
January 2006
January 2006
January 2006
January 2006
January 2006
January 2006
At Course Conclusion
You will have practiced the key elements of an industrialstrength software process.*
You will understand which methods are most effective for you.
You will do better work.
You will have long-term improvement goals.
January 2006
Course Results
We now have data on over 30,000 programs written using
the PSP.
The following charts show how others have improved during
the PSP course.
effort estimating
compile and test time
productivity
January 2006
PSP 0
20
0
-200%
40
-100%
0%
100%
-100%
0%
100%
0%
100%
PSP 1
20
0
-200%
40
PSP 2
20
0
-200%
January 2006
-100%
Effort
PSP I - Introduction
Estimation
Accuracy to PSP and TSP - 24
Upper
25
20
15
10
Average
Lower
5
0
1
10
Program Number
2006 by Carnegie Mellon University
January 2006
January 2006
Messages to Remember
The PSP is a defined process that helps you do better
work.
Once you have completed the course, you will know how
to apply the PSP to your personal needs.
You will have the knowledge and skill to be on a TSP
team.
With PSP0, the objective is to gather accurate and
complete data on your work.
January 2006