SOFTWARE PROJECT MANAGEMENT MANAGING THE THREE PS by: Mikael Brjeson, CDT - PowerPoint PPT Presentation

1 / 22
About This Presentation
Title:

SOFTWARE PROJECT MANAGEMENT MANAGING THE THREE PS by: Mikael Brjeson, CDT

Description:

Motivation, true respect and appreciation come together ... fasten seat-belts! PURPOSE. System functions. Reliability & Performance. Flexibility of Design ... – PowerPoint PPT presentation

Number of Views:53
Avg rating:3.0/5.0
Slides: 23
Provided by: jmikael
Category:

less

Transcript and Presenter's Notes

Title: SOFTWARE PROJECT MANAGEMENT MANAGING THE THREE PS by: Mikael Brjeson, CDT


1
SOFTWAREPROJECTMANAGEMENTMANAGING THE THREE
PSby Mikael Börjeson, CDT
2
  • The three Ps to be managed...PEOPLEPROBLEMPROC
    ESS

3
I'm an old manI've had many problems...Most of
them never happened!
4
Start climbing the learning ladder,and become a
star!Enable a culture of feed-back and
reflection.
5
Overloaded? - Identify the "vital few"!The
"Pareto Principle" (80/20)generally applies.
6
ProjectManager
ConfigurationManagement
Quality Assurance
System Team
Test Team
Design Team
Design Team
7
Motivation, true respect and appreciation come
together
8
Using waterfall model, maybe is for
cowards.Using no model, is for kamikaze's only!
9
Put the customer in the driving-seat
and...fasten seat-belts!
10
REQUREMENT SPECIFICATION...
  • PURPOSE
  • System functions
  • Reliability Performance
  • Flexibility of Design
  • USAGE
  • Operational aspects
  • Environmental aspects
  • Maintenance aspects
  • USER PROFILE
  • Age, sex
  • Education and experience
  • Culture aspects
  • CONSTRUCTION
  • Tools constraints
  • Components
  • Architectural constraints
  • DEPLOYMENT
  • Distribution
  • Installation

11
Code code where's the code ?
12
Decomposition likesnumbers between 4 and 7.
13
Be serious - Have Fun!
14
  • EstimationI swear to say the truth,and
    nothing but the truth,so help me Lichtenberg
  • Even a good estimation is a lie, and there
  • is but one way to make it become the truth
  • Decisive project management!

15
Lichtenberg - An Estimation Technique...
Propability
95,5
Resources( Effort / Cost )
2,25
2,25
Likely
Best Case
Worst Case
2 ?
2 ?
16
Lichtenberg continued
x 2

-
? 4
? 2
Best case
Guess
Worst case
Likely
Uncertainty
Activity
25 h
75 h
125 h
75 h
50 h
Activity
40 h
100 h
200 h
110 h
90 h
Activity
200 h
400 h
1000 h
500 h
500 h
Activity
20 h
40 h
60 h
40 h
20 h
Activity
Subject for breakdown andestimation of
components
17
The best way to predict the future, is
to invent it!
18
Doing well? - No, so far poor but
improving!Try CMM or SPICE
19
Software errors, that doesn't come unexpected,
we call sabotage!Do root cause analysis!
20
The quickest way to end a task isto skip it!
21
Trouble shooting approach - step 1...Struggling
with a hard problem?Find something to
remove!Lex Öbrink
22
Mistakes I did - and do, anyway.What
did I learn today?Feed-back and
Reflectionclimb the learning ladder and become a
star
Write a Comment
User Comments (0)
About PowerShow.com