Planning process
„ Planning is the processes for the processes
Project planning
„ Planning is also a development perspective
„ 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
„
Kristian Sandahl
krs@ida.liu.se
Kristian Sandahl, IDA
krisa@ida.liu.se
What is a project?
The project plan
„ A temporal organisation with specific goals:
„ Shall always be written down.
Functions
„ Quality
„ Time
„ Resources
„ Shall be readable to all stakeholders of the
„
project.
„ We’ll go through some important parts of a
project plan with theory and
recommendations.
Kristian Sandahl, IDA
krisa@ida.liu.se
Kristian Sandahl, IDA
krisa@ida.liu.se
1
Administrative information
Overview
„ Project identity
„ Purpose
„ Prioritised goal(s), sub goals, internal goals
„ Limitations and constraints:
„ Hardware
„ Resources
„ Time
„ Technology
„ Knowledge
„ Stake-holders: primary, secondary, indirect
„ Members: name, role, phone, email
„ Version number
„ Mailing lists
„ Home pages
„ Customer contact
„ Table of contents
Kristian Sandahl, IDA
krisa@ida.liu.se
Same management, different
development
Phase plan
prestudy
feasability study
System
development
phases
Kristian Sandahl, IDA
krisa@ida.liu.se
inception
elaboration
prestudy
conculsion
the
Topic for
n
project pla
transition
construction
Project
managment
phases
execution
Kristian Sandahl, IDA
krisa@ida.liu.se
feasability study
System
development
phases
analysis
conculsion
design
testing
implementation
Project
managment
phases
execution
Kristian Sandahl, IDA
krisa@ida.liu.se
2
Organisation
„ Place of the project
„ Teams
„ Roles
„ Responsibilities
„ Authorities
„ Communications
„ Documents
Project manager
„ Recommended roles:
„ Project leader
„ Lead analyst
„ Architect
„ Test leader
„ Librarian/Knowledge
manager
„ Testers should be
independent
„
„
„
„
„
„
„
„
„
Has the final word on all matters
Manages resources
Ensures goals
Makes staffing
Plans
Reports internally, externally
Leadership
Social skills
High technical skill
Kristian Sandahl, IDA
krisa@ida.liu.se
Lead analyst
„
„
„
„
„
„
„
„
„
„
Kristian Sandahl, IDA
krisa@ida.liu.se
Architect
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
„ 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
3
Test leader
„
„
„
„
„
„
„
„
„
Librarian/Knowledge manager
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
„ Keeps documents in good order
„ Makes documents available
„ Follow-up on administrative decisions’
„ Collects time-reports
„ Identifies reusable components
„ Creates common experience
„ Very high sense for good order
„ Experience as developer
Kristian Sandahl, IDA
krisa@ida.liu.se
Kristian Sandahl, IDA
krisa@ida.liu.se
Other useful roles
Documentation plan
„ Development manager
Internal:
„ Minutes of meetings
„ Meeting agendas
„ Time reports
„ Experience build-up
„ Inspection records
„ Accounting
„ Group contract
„ Mile-stone review
„ Procurement manager
„ Economic controller
„ Quality coordinator
„ Deployment responsible
„ Technical writer
„ Course developer
Kristian Sandahl, IDA
krisa@ida.liu.se
External:
„ Requirements specification
„ Design specification
„ Test report
„ Manuals
„ Economic communication
„ Promotion material
„ Toll-gate preparation
Kristian Sandahl, IDA
krisa@ida.liu.se
4
Training and education
Resource plan
„ Internal:
„ Tools
„ Techniques
„ Methods
„ Maturity
„ People:
„ Expertise
„ Availability
„ Premises
„ Hardware
„ Software
„ Testing equipment
„ Travelling
„ Customer time
„ Budget
„ External:
„ Customers
„ Users
„ Operation
Kristian Sandahl, IDA
krisa@ida.liu.se
Meeting plan
Kristian Sandahl, IDA
krisa@ida.liu.se
Communication genres
„ Type of meeting
„ Frequency
Negotiations:
•Constructive
•Side-effects
Workshops:
•Reduced lead-time
•First-hand information is spread
„ Process
„ Participation
Kristian Sandahl, IDA
krisa@ida.liu.se
Kristian Sandahl, IDA
krisa@ida.liu.se
5
Mile-stone and tollgate plan
Toll-gate
Plan and follow-up
follow-up
periods
Mile-stone
outcome
Decision about the continuation of Verifying sub-goal fulfilment.
the project by external committee Can be done internally.
initial plan
time
Kristian Sandahl, IDA
krisa@ida.liu.se
Activities
Gantt chart
I
„ Number
„ Name
„ Resources
„ Duration no descr who w1 w2 w3 w4 time(h)
„ Break
Kristian Sandahl, IDA
krisa@ida.liu.se
1
down per 2
person
3
interv
A,K 50
20 5
UML
K,U 5
50 50 25 130
spec
K
0
0
0
75
50 50 100
4
val
M,K 0
0
0
75 75
...
...
...
...
...
...
...
...
Kristian Sandahl, IDA
krisa@ida.liu.se
Tas
' 0D3u
1 För
I n le d a
24
d5
In s a m
10
2
3
4
S y s te
5
K ra v s
2
6
P ro j
2
7
B
2
8
R e dov.
9
I n lä m n .
1 Huv
d
D
1
1
1
0
28
d5
1
B
1
S y s te m m
1
I n lä m n i
0
1
Ko
10
1
S y s te m m
1
T e s tf
1
Te
5
1
B
2
2
I n lä m n i
0
2
In te
2
5
1
1
5
5
S y s te m
1
2
B
3
2
S y s t e m m ö t e -1
2
Red
2 P r o je k
2 t St a ä
m m anst
2
B
2
I n lä m n in g
3 I n s a m lin
3 H a lv t i
'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 2 2 2 2 0 0 0 0 0 1 1 1 1 1 2 2 2 2 2 3 0 0 0 0 1 1 1 1 1 2 2 2 2 2 3 0 0 0 0 1 1 1 1 1 2
1
10
d7
3
0
50
1
3 U tv
1
3 Ki
1
3 Ki
1
Kristian Sandahl, IDA
krisa@ida.liu.se
6
Quality and Change
Quality plan:
„ Tests:
„ unit test
„ system test
„ integration test
„ acceptance test
„ Inspections
„ Reviews
„ Measurements
„ Follow-up
„ Experience feed-forward
Risk analysis
Change plan:
„ Request
„ Process
„ Decision
„ Documentation
„ Configuration management
„ Follow-up
risk
probability
severity
risk
PL ill
3
2
6
delay
1
4
4
risk
risk
remedy cost
threat
PL ill
6
2
12
delay
4
4
16
Kristian Sandahl, IDA
krisa@ida.liu.se
Kristian Sandahl, IDA
krisa@ida.liu.se
Introduction of project plan
Project management process
„ Project overview
„ Staffing
„ Main deliverables
„ Priorities
„ Main milestones
„ Philosophy
„ Library for documents and code
„ Risk management
„ Definitions
„ Task refinement
„ Communication with stake-holders
„ Routines for reporting
Kristian Sandahl, IDA
krisa@ida.liu.se
Kristian Sandahl, IDA
krisa@ida.liu.se
7
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
8