0% found this document useful (0 votes)
35 views27 pages

Introduction To PSP and TSP: Personal Software Process For Engineers: Part I

PSP
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
35 views27 pages

Introduction To PSP and TSP: Personal Software Process For Engineers: Part I

PSP
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 27

Pittsburgh, PA 15213-3890

Personal Software Process


for Engineers: Part I

SM

Introduction to PSP and TSP


This material is approved for public release. Distribution is limited by the
Software Engineering Institute to attendees.
Sponsored by the U.S. Department of Defense
2006 by Carnegie Mellon University
January 2012

PSP I - Introduction to PSP and TSP - 1

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

2006 by Carnegie Mellon University

January 2006

PSP I - Introduction to PSP and TSP - 2

The Changing World of Software


Software now controls most business, government, and
military systems.
Factories are managed by software.
Most advanced products are controlled by software.
Finance, administrative, and business operations are
largely run by software.
The cost, schedule, and quality of software is now a critical
business concern.

2006 by Carnegie Mellon University

January 2006

PSP I - Introduction to PSP and TSP - 3

Software Products are Bigger

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

PSP I - Introduction to PSP and TSP - 4

Big Software Projects Usually Fail


With increased size, projects are more troubled.
Project Size
Less than $750K
$750K to $1.5M
$1.5M to $3M
$3M to $6M
$6M to $10M
Over $10M

People
6
12
25
40
+250
+500

Time (Months) Success Rate


6
55%
9
33%
12
25%
18
15%
+24
8%
+36
0%

This is a problem of scale: current software practices do not scale


up.

Standish: Chaos Reports, 1999


2006 by Carnegie Mellon University

January 2006

PSP I - Introduction to PSP and TSP - 5

Why Projects Fail -1


Large and small software projects fail for four reasons.
Project commitments are often unrealistic.
The larger the project, the less influence we have.
If we dont have anything to say, nobody will listen.
Larger projects are harder to control.
Today, few developers have personal plans.
Without a plan, you cannot know job status.
If you dont know where you are, management cant
understand job status.
If management doesnt understand job status, they
cant manage projects.
2006 by Carnegie Mellon University

January 2006

PSP I - Introduction to PSP and TSP - 6

Why Projects Fail -2


Quality problems get worse with project size.
In software systems, if any part has quality problems,
the system will have quality problems.
If the developers do not manage quality, their teams
cannot manage quality.
When unmanaged, quality will always be poor.
To be effective, teams need leadership and coaching.
Leaders build team motivation and commitment.
Coaching develops team cohesion.
Cohesive, motivated, and committed teams do the best
work.

2006 by Carnegie Mellon University

January 2006

PSP I - Introduction to PSP and TSP - 7

The Need for Change


Many lives and businesses now depend on software.
We now need larger, more complex, and safer software
systems on predictable schedules.
Without different software practices, this will not happen.
The Team Software Process (TSP) addresses this need.
The PSP provides the knowledge and skill that
developers need to work on TSP teams.

2006 by Carnegie Mellon University

January 2006

PSP I - Introduction to PSP and TSP - 8

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.

2006 by Carnegie Mellon University

January 2006

PSP I - Introduction to PSP and TSP - 9

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

2006 by Carnegie Mellon University

January 2006

PSP I - Introduction to PSP and TSP - 10

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.

2006 by Carnegie Mellon University

January 2006

PSP I - Introduction to PSP and TSP - 11

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.

2006 by Carnegie Mellon University

January 2006

PSP I - Introduction to PSP and TSP - 12

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.

2006 by Carnegie Mellon University

January 2006

PSP I - Introduction to PSP and TSP - 13

What Does a PSP Provide?


A stable, mature PSP allows you to
estimate and plan your work
meet your commitments
resist unreasonable commitment pressures
You will also
understand your current performance
be better equipped to improve your capability

2006 by Carnegie Mellon University

January 2006

PSP I - Introduction to PSP and TSP - 14

What Does the PSP Provide?


The PSP provides
a proven basis for developing and using an industrialstrength personal process
a discipline that shows you how to improve your
personal process
the data to continually improve the productivity, quality,
and predictability of your work

2006 by Carnegie Mellon University

January 2006

PSP I - Introduction to PSP and TSP - 15

What is the PSP?


The PSP is a personal process for developing software or
for doing any other defined activity. The PSP includes
defined steps
forms
standards
It provides a measurement and analysis framework for
characterizing and managing your personal work.
It is also a defined procedure that helps you to improve your
personal performance.

2006 by Carnegie Mellon University

January 2006

PSP I - Introduction to PSP and TSP - 16

The PSP Process Flow

2006 by Carnegie Mellon University

January 2006

PSP I - Introduction to PSP and TSP - 17

The Personal Software Process


The PSP process is designed for individual use.
It is based on scaled-down industrial software practice.
The PSP course demonstrates the value of using a defined
and measured process.
It helps you and your organization meet the increasing
demands for high quality and timely software.

2006 by Carnegie Mellon University

January 2006

PSP I - Introduction to PSP and TSP - 18

Learning the PSP -1


The PSP is introduced in six upward-compatible steps.
You write one or more module-sized programs at each step.
You gather and analyze data on your work.
You use the results to improve your personal performance.

2006 by Carnegie Mellon University

January 2006

PSP I - Introduction to PSP and TSP - 19

Learning the PSP -2

2006 by Carnegie Mellon University

January 2006

PSP I - Introduction to PSP and TSP - 20

Learning the PSP -3


PSP0: You establish a measured performance baseline.
PSP1: You make size, resource, and schedule plans.
PSP2: You practice defect and yield management.

2006 by Carnegie Mellon University

January 2006

PSP I - Introduction to PSP and TSP - 21

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.

*These are generally called CMMI level 5 processes.


2006 by Carnegie Mellon University

January 2006

PSP I - Introduction to PSP and TSP - 22

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

2006 by Carnegie Mellon University

January 2006

PSP I - Introduction to PSP and TSP - 23

PSP Effort Estimating Accuracy


40

Majority are underestimating

Balance of over- and


underestimates

Much tighter balance


around zero

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%

2006 by Carnegie Mellon University

January 2006

-100%

Effort

PSP I - Introduction
Estimation
Accuracy to PSP and TSP - 24

Compile and Test Time as % of


Development Time

Compile and Test Time 810 Engineers


50
45
40
35
30

Upper

25
20
15
10

Average
Lower

5
0
1

10

Program Number
2006 by Carnegie Mellon University

January 2006

PSP I - Introduction to PSP and TSP - 25

Size and LOC/hour 810 Engineers

2006 by Carnegie Mellon University

January 2006

PSP I - Introduction to PSP and TSP - 26

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.

2006 by Carnegie Mellon University

January 2006

PSP I - Introduction to PSP and TSP - 27

You might also like