Table of contents
Customer contact
Home pages
Mailing lists
Version number
Kristian Sandahl, IDA
krisa@ida.liu.se
Purpose
Prioritised goal(s), sub goals, internal goals
Limitations and constraints:
Hardware
Resources
Time
Technology
Knowledge
Stake-holders: primary, secondary, indirect
Project identity
Members: name, role, phone, email
2. Overview
1. Administrative information
Kristian Sandahl, IDA
krisa@ida.liu.se
Planning is about refining processes:
the worldly level assigns activities to the process
model, defines tasks and measures
the atomic level is detailed description of input and
output
Functions
Quality
Time
Resources
A temporal organisation with specific goals:
Planning is the processes for the processes
Planning is also a development perspective
What is a project?
Planning process
Kristian Sandahl, IDA
krisa@ida.liu.se
Kristian Sandahl, IDA
krisa@ida.liu.se
System development
phases
feasability study
prestudy
execution
construction
transition
elaboration
inception
3. Phase plan
Kristian Sandahl, IDA
krisa@ida.liu.se
Kristian Sandahl, IDA
krisa@ida.liu.se
Project managment
phases
the
Topic for
an
project pl
conculsion
plan with theory and recommendations.
We’ll go through some important parts of a project
project.
Shall be readable to all stakeholders of the
Shall always be written down.
The project plan
testing
execution
implementation
design
analysis
Kristian Sandahl, IDA
krisa@ida.liu.se
Kristian Sandahl, IDA
krisa@ida.liu.se
Project managment
phases
conculsion
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
Lead analyst
System development
phases
feasability study
prestudy
Same management, different
development
independent
Testers should be
Kristian Sandahl, IDA
krisa@ida.liu.se
Kristian Sandahl, IDA
krisa@ida.liu.se
Recommended roles:
Project leader
Lead analyst
Architect
Test leader
Librarian/Knowledge
manager
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
Architect
Documents
Communications
Authorities
Responsibilities
Roles
Teams
Place of the project
4. Organisation
Has the final word on all matters
Manages resources
Ensures goals
Makes staffing
Plans
Reports internally, externally
Leadership
Social skills
High technical skill
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
Test leader
Project manager
Kristian Sandahl, IDA
krisa@ida.liu.se
Kristian Sandahl, IDA
krisa@ida.liu.se
Kristian Sandahl, IDA
krisa@ida.liu.se
Kristian Sandahl, IDA
krisa@ida.liu.se
Participation
Process
Frequency
Type of meeting
People:
Expertise
Availability
Premises
Hardware
Software
Testing equipment
Travelling
Customer time
Budget
Internal:
Tools
Techniques
Methods
Maturity
External:
Customers
Users
Operation
8. Meeting plan
7. Resource plan
Kristian Sandahl, IDA
krisa@ida.liu.se
Internal:
Minutes of meetings
Meeting agendas
Time reports
Experience build-up
Inspection records
Accounting
Group contract
Mile-stone review
Toll-gate preparation
Promotion material
Kristian Sandahl, IDA
krisa@ida.liu.se
Kristian Sandahl, IDA
krisa@ida.liu.se
Economic communication
Manuals
Test report
Design specification
Requirements specification
External:
5. Documentation plan
6. Training and education
Course developer
Experience as developer
Kristian Sandahl, IDA
krisa@ida.liu.se
Technical writer
Deployment responsible
Quality coordinator
Economic controller
Very high sense for good order
Creates common experience
Identifies reusable components
Collects time-reports
Follow-up on administrative decisions’
Procurement manager
Development manager
Keeps documents in good order
Makes documents available
Other useful roles
Librarian/Knowledge manager
4
ö
T reb e r
s
Btn
f m ni
Iunf lä
Inngt ea v
1 d
3
U st vu t v ä
2 ä rd
8
f m n in g
2
Iunf lä
9
3 I nas va m lin
0 H
g aa lvv t i
3
d
5d0a
d1a
d
1
da
0
d
5a
g
d1 a
S ryast t e m
m ö te B
3d
u
S fyf s t e m m ö t e d
-1 a
4
A
d
2
R ve sdt ä m n in g
1
5
o
v
i
s
2 P r o je k
1d0
6
ä r m a n s t d7 a
2 t uSt va m
7
ä ll n in g a v
da
2
B
3
2
2
3
2
0
2
1
2
8
1
9
2
da
0
da
5
d
2a
n
K go
d ny is t e m m
S
ö tees -t f
T
4
1
5
1
6
1
7
1
d1 a
0d
1d0a
d1a
5d
u fyf s t e m m
S
e m
- ni
Iönt lä
2
1
3
1
d1 a
0d
u fef d o v .
R
a vms np .e c .
IKn rlä
2d8a
d5 a
da
5
da
2
d
2a
p er oc ji f i
P
ekt
B
9
1 HK
u rva v s p e c
dpr
0
1 uD
1
es
1
B
8
7
6
5
d1a
2d
Kristian Sandahl, IDA
krisa@ida.liu.se
krisa@ida.liu.se
Verifying sub-goal fulfilment.
Can be done internally. Kristian Sandahl, IDA
Mile-stone
' 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
Sr ea t i 2S2e 2 2 S
2 e0 0 0O0 c0t 1 O
1 1c t1 1O2 c2t 2 O
2 2c t3 0N0o0 0 N
1 o1 1 1N1o2 2 N
2 o
2 2 3D0e0 0 D
0 e
1 1 1D1e1 2
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
da
5
1d0a
lSinygs t e
m rm
K
a vöst e
I Tas
D k
1 För
p ro
2
I n le d a
3
Inndsea m
Gantt chart
Decision about the continuation of
the project by external committee
Toll-gate
9. Mile-stone and tollgate plan
Quality plan:
Tests:
unit test
system test
integration test
acceptance test
Inspections
Reviews
Measurements
Follow-up
Experience feed-forward
Kristian Sandahl, IDA
krisa@ida.liu.se
time
Follow-up
Kristian Sandahl, IDA
krisa@ida.liu.se
Configuration management
Documentation
Decision
Process
Request
Change plan:
12. Quality and Change
initial plan
outcome
follow-up
periods
10. Follow-up
K
M,K
spec
val
...
down per 3
4
person
...
delay
PL ill
risk
delay
PL ill
risk
4
6
risk
1
3
probability
...
0
0
5
4
2
remedy cost
4
2
severity
...
13. Risk analysis
Break
K,U
UML
2
Duration
50
who w1
A,K
interv
1
Resources
no descr
Name
Number
11. Activities
...
0
0
50
20
...
75
50
25
0
w4
16
12
threat
4
6
risk
...
0
50
50
5
w2 w3
Kristian Sandahl, IDA
krisa@ida.liu.se
Kristian Sandahl, IDA
krisa@ida.liu.se
...
75
100
130
75
time(h)
Library for documents and code
Definitions
Communication with stake-holders
Risk management
Task refinement
Routines for reporting
Reduced lead-time
First-hand information is spread
Workshops:
Constructive
Side-effects
Negotiations:
Kristian Sandahl, IDA
krisa@ida.liu.se
Main milestones
Philosophy
Hierarchy
Star
Democratic
Communication networks
Main deliverables
Priorities
Communication genres
Project overview
Staffing
Kristian Sandahl, IDA
krisa@ida.liu.se
Introduction of project plan
Project management process
Kristian Sandahl, IDA
krisa@ida.liu.se
Kristian Sandahl, IDA
krisa@ida.liu.se
Communication
Priorities
Credits
Assignments
Disciplinary actions
Kristian Sandahl, IDA
krisa@ida.liu.se
Kristian Sandahl, IDA
krisa@ida.liu.se
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
Effort = C1 EAF (Size)P1
COCOMO
something fun, too!
Make sure to do
focusing on:
Form a group contract
project plan
Gather to go through the
Kick-off and group contract
Kristian Sandahl, IDA
krisa@ida.liu.se
answer.
Kristian Sandahl, IDA
krisa@ida.liu.se
Make an initial role assignment, motivate your
friends
List and grade competencies of you and your
you and some friends.
Define a project you would like to take part in for
Exercise
Kristian Sandahl, IDA
krisa@ida.liu.se
Consumes about 10% of the budget
Has been around since 1976 at NASA
validation of hypotheses
Kristian Sandahl, IDA
krisa@ida.liu.se
Example of output: trends, similar project data,
Summary
Discussion and second round
Goal: reuse
software item components
Infrastructure for logging measurements and
Experience Factory
Independent, personal estimates
Meet to discuss a common view
Present information for expert panel
Time = C2 (Effort)P2
Time = total number of months
C2 = scaling constant
P2 = Inherent inertia and parallelism in
management
DELPHI
COCOMO