What is a project?
A temporal organisation with specific goals:
Project planning
Functions
Quality
Time
Resources
Kristian Sandahl
krs@ida.liu.se
Kristian Sandahl, IDA
krisa@ida.liu.se
The project plan
Administrative information
Shall always be written down.
Project identity
Shall be readable to all stakeholders of the
Members: name, role, phone, email
project.
We’ll go through some important parts of a
project plan with theory and
recommendations.
Version number
Mailing lists
Home pages
Customer contact
Table of contents
Kristian Sandahl, IDA
krisa@ida.liu.se
Overview
Kristian Sandahl, IDA
krisa@ida.liu.se
Phase plan
Purpose
Prioritised goal(s), sub goals, internal goals
Limitations and constraints:
Hardware
Resources
Time
Technology
Knowledge
Stake-holders: primary, secondary, indirect
prestudy
feasability study
System
development
phases
inception
elaboration
transition
construction
conculsion
the
Topic for
n
la
p
t
ec
proj
Project
managment
phases
execution
Kristian Sandahl, IDA
krisa@ida.liu.se
Kristian Sandahl, IDA
krisa@ida.liu.se
1
Same management, different
development
prestudy
analysis
Organisation
Place of the project
conculsion
Teams
Roles
feasability study
Responsibilities
design
testing
Authorities
Communications
System
development
phases
implementation
Project
managment
phases
Documents
Recommended roles:
Project leader
Lead analyst
Architect
Test leader
Librarian/Knowledge
manager
Testers should be
independent
execution
Kristian Sandahl, IDA
krisa@ida.liu.se
Project manager
Kristian Sandahl, IDA
krisa@ida.liu.se
Lead analyst
Has the final word on all matters
Manages resources
Ensures goals
Makes staffing
Plans
Reports internally, externally
Leadership
Social skills
High technical skill
Defines services provided
Captures requirements
Models the forthcoming system
Handles contacts with customer and users
Has the final word on requirements interpretations
Assists marketing
Writes requirements specification
Very good communication skills
High analytical skills
Good domain and business knowledge
Kristian Sandahl, IDA
krisa@ida.liu.se
Kristian Sandahl, IDA
krisa@ida.liu.se
Architect
Test leader
Has the final word in technical matters
Decide and specifies:
target environment
high-level architecture
sourced components
external interfaces
Ensures requirements
Highest possible technical skills
Leadership
Social skills
Kristian Sandahl, IDA
krisa@ida.liu.se
Evaluates requirements
Creates and selects test cases
Creates and maintains a test environment
Feed-back test results
Decides the status of the product
Very high analytical skills
Very high technical skills
Skills in statistics
Sometimes the default deputy PL
Kristian Sandahl, IDA
krisa@ida.liu.se
2
Librarian/Knowledge manager
Other useful roles
Keeps documents in good order
Development manager
Makes documents available
Procurement manager
Follow-up on administrative decisions’
Economic controller
Collects time-reports
Quality coordinator
Identifies reusable components
Creates common experience
Deployment responsible
Very high sense for good order
Technical writer
Experience as developer
Course developer
Kristian Sandahl, IDA
krisa@ida.liu.se
Kristian Sandahl, IDA
krisa@ida.liu.se
Documentation plan
Training and education
Internal:
Minutes of meetings
Meeting agendas
Time reports
Experience build-up
Inspection records
Accounting
Group contract
Mile-stone review
Internal:
Tools
Techniques
Methods
Maturity
External:
Requirements specification
Design specification
Test report
Manuals
Economic communication
Promotion material
Toll-gate preparation
Kristian Sandahl, IDA
krisa@ida.liu.se
External:
Customers
Users
Operation
Kristian Sandahl, IDA
krisa@ida.liu.se
Resource plan
Meeting plan
People:
Expertise
Availability
Premises
Hardware
Software
Testing equipment
Travelling
Customer time
Budget
Type of meeting
Frequency
Process
Participation
Kristian Sandahl, IDA
krisa@ida.liu.se
Kristian Sandahl, IDA
krisa@ida.liu.se
3
Communication genres
Mile-stone and tollgate plan
Toll-gate
Mile-stone
Negotiations:
•Constructive
•Side-effects
Workshops:
•Reduced lead-time
•First-hand information is spread
Decision about the continuation of Verifying sub-goal fulfilment.
the project by external committee Can be done internally.
Kristian Sandahl, IDA
krisa@ida.liu.se
Plan and follow-up
Kristian Sandahl, IDA
krisa@ida.liu.se
Activities
follow-up
periods
Number
Name
outcome
Resources
Duration no descr who w1 w2 w3 w4 time(h)
Break
1
down per 2
person
3
initial plan
time
interv
A,K 50
20 5
UML
K,U 5
50 50 25 130
I Tas
D k
1 För
2 p rI no le d a
3
spec
K
0
0
50 50 100
val
M,K 0
0
0
75 75
...
...
...
...
...
...
...
4
6
m rm
K
a vöst e
p er oc jif i
P
7
ekt
B
5
u
R fef d o v .
a vms np .e c .
9
IKnrlä
1 HK
u rva v s p e c
0
1 ud
Dp r
1
e
1
Bs
2
u
f
f
1
S y s te m m
3
ö
- ni
1
I nt e
lä m
8
4
1
5
1
6
1
7
1
8
1
9
2
0
2
1
2
2
2
n go
K
d ny is t e m m
S
ö tees -tf
T
ö reb e r
T
s tn
B
f m ni
Iunf lä
Inngt ea v
g
S ryast t e m
m
B ö te -
3
u fyf s t e m m ö t e
2
S
4
A
2
R ve sdt ä m n in g
5
r ov jise k
2 Po
6 t uSt a
vä
2
mr m a n s t
7
2
8
2
1d0a
d1a
2d
da
2
da
2
d1a
0d
2d8a
d5a
d
5a
d1a
0d
1d0a
d1a
5d
d
5a
da
2
da
0
da
5
d1a
3d
d
-1a
Quality plan:
Tests:
unit test
system test
integration test
acceptance test
Inspections
Reviews
Measurements
Follow-up
Experience feed-forward
Change plan:
Request
Process
Decision
Documentation
Configuration management
Follow-up
d
1
1d0
d7a
ä l ln in g a v
B
da
3
u
f m n in g
I nf lä
9 I nasva m lin
3
0
g aa lv
v ti
3 H
1
3 d
U st vu t v ä
da
0
5d0a
d1a
2
3 ä
K ri d
3 cK ki
3
4 ck
...
Kristian Sandahl, IDA
krisa@ida.liu.se
Quality and Change
'0D3u '0 3
'0 3
'0 3
'0 3
'0 3
'0 3
'0 3
'0 3
'0 3
'0 3
'0 3
'0 3
'0 3
2 e0 0 0O0c0t 1 O
1 1c t1 1O2c2t 2 O
2 2
1 o
1 1 1N1o2 2 N
2 o
2 2 3D0e0 0 D
0 e
1 1 1D1e1 2
Sr ea t i 2S2e 2 2 S
c t3 0N0o0 0 N
24 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0
d5a
n
I ndsea m
lin
S ygs t e
75
4
Kristian Sandahl, IDA
krisa@ida.liu.se
Gantt chart
0
d
1
d
1
Kristian Sandahl, IDA
krisa@ida.liu.se
Kristian Sandahl, IDA
krisa@ida.liu.se
d
1
d
4
Risk analysis
Introduction of project plan
Project overview
risk
probability
severity
risk
Main deliverables
PL ill
3
2
6
Main milestones
delay
1
4
4
Library for documents and code
risk
risk
remedy cost
threat
PL ill
6
2
12
delay
4
4
16
Definitions
Communication with stake-holders
Kristian Sandahl, IDA
krisa@ida.liu.se
Kristian Sandahl, IDA
krisa@ida.liu.se
Kick-off and group contract
Communication genres
Gather to go through
Negotiations:
the project plan
Form a group contract
focusing on:
Constructive
Side-effects
Workshops:
Communication
Priorities
Credits
Assignments
Disciplinary actions
Reduced lead-time
First-hand information is spread
Make sure to do
something fun, too!
Kristian Sandahl, IDA
krisa@ida.liu.se
Communication networks
Kristian Sandahl, IDA
krisa@ida.liu.se
Project management process
Staffing
Priorities
Philosophy
Risk management
Task refinement
Hierarchy
Star
Routines for reporting
Democratic
Kristian Sandahl, IDA
krisa@ida.liu.se
Kristian Sandahl, IDA
krisa@ida.liu.se
5
COCOMO
COCOMO
Effort = C1 EAF (Size)P1
Time = C2 (Effort)P2
Effort = number of staff months
C1 = scaling constant
EAF = Effort Adjustment Factor
Size = number of delivered, human produced
source code instructions (KDSI)
P1 = exponent describing the scaling inherent
of the process
Time = total number of months
C2 = scaling constant
P2 = Inherent inertia and parallelism in
management
Kristian Sandahl, IDA
krisa@ida.liu.se
Kristian Sandahl, IDA
krisa@ida.liu.se
DELPHI
Present information for expert panel
Meet to discuss a common view
Independent, personal estimates
Summary
Discussion and second round
Kristian Sandahl, IDA
krisa@ida.liu.se
6