Professional Documents
Culture Documents
2004
P1
The Project
What is a project?
Restricted in time
Starting time
Ending time!!!
Own organization
Project personnel
2004
P2
P3
History ...
1960s
long planning horizons
project administration was in
1970s
leadership
team-work, independent teams
1980s
PC revolution: Project planning tools
1990s
throughput optimization
interaction between teams
2000s
projects today and tomorrow will be formed by you
2004
P4
The Project
When is a project successful?
keeps on schedule
produces what expected
keeps on budget
people feel happy about the project
customers
project personnel
other stakeholders
P5
2004
minimal defects
maximum user satisfaction
minimal response time
maintainability
extendibility
robustness
short schedule
predictable delivery date
low cost
P6
Project success
What is the most important to make
project work successful?
People?
Time?
Budget?
Product / deliverables?
Communication?
Marketing?
2004
P7
2004
-31,5
-14,9
-3,8
-3,8
-2,3
P8
P9
P 10
Company
management
Management
Project
contact
Project
manager
Customer
Boss(es)
Family /
friends
2004
Leader
Leader
Database
team
User
interface
team
P 11
Project organization
Orderer
Orderer
Steering group
Team Leader /PM
Quality assurance
Quality assurance
Team
Project manager
Consults
Team Leader
2004
Secretary
Team Leader
Team Leader
P 12
matrix organization
2004
2004
P 14
Management...
Estimation and scheduling
estimate the size of project
estimate the effort needed to build a product
estimate the schedule
accurate estimation increases effective
planning, which increases efficient
development
2004
P 15
Management..
planning activities
estimation and scheduling
people (how many, skills, when, who)
organization of the team(s)
lifecycle model
risk management
strategic decisions
features
develop or buy
2004
P 16
Management
tracking
a project to follow the plan
schedule, cost, quality, targets, features
management level
tasks lists, status meetings & reports, milestone
reviews, budget reports, management by walking
around
technical level
technical audits & reviews, quality gates
2004
P 17
Project management
controls three corners of trade-off triangle
schedule, cost, product
Schedule
Pick 2 of 3
consists of determining
Cost
Product
P 18
Project timeline
Feasibility
study
pre-project
2004
Project
startup
Main process
time
P 19
2004
P 20
The people
Project manager
The one that should make all happy...
Motivation, organization, ideas and innovation
Team leaders
People-intensive activity (good practitioners
might make poor team leaders)
2004
P 21
Team/project manager
Set realistic project goals
Wisely allocate tasks to team members
Run meetings
Manage time
Communicate
Manage shared group documents
Roles of team leaders / team members
2004
P 22
P 23
2004
P 25
P 26
The team
The software team
What teams to form, size, structure?
Distribution of skills
2004
P 27
2004
P 28
About communication
verbal communication
language, quality of spoken lang. , tempo
rhythm, pitch articulation
nonverbal communication
appearance, facial expressions
written
books, journals, daily papers, memos etc,
emails
2004
P 29
2004
P 30
2004
P 31
Telephone
fast problems solving
no automaticdocumentation
P 32
Types of communication
Formal, impersonal approaches Informal interpersonal
Documents
procedures
Project milestones
Error tracking reports
Source code
Repository data
Project control tools
Formal, interpersonal
procedures
2004
Group meetings
Electronic communication
Electronic mail
Project bulletins
Interpersonal network
Discussions with peers
Design reviews
Requirements reviews
Status reviews
Code inspections
P 33
P 34
2004
P 35
Simple AGENDA
GROUP A MEETING, DC 3101 Nov 7. at 10.15
Present: NN, NN, NN, NN
AGENDA:
* Code status (dev manager)
* Decision on testing tools
* The documentation templates (process manager)
* Test plan (testing manager)
* Next meeting
Agenda distributed 1-10 days before meeting
2004
P 36
The process
Some process is normally ;) used for generating
software
2004
linear
prototyping
RAD
incremental
spiral
WINWIN
component-based
formal methods
P 37
Process / product
Example: Software process involving
Customer communcation
Planning
Risk analysis
Engineering
Construction and relase
Customer evaluation
P 38
Sales process
Software process
2004
P 39
Finally
My personal favorit methodology:
Keep
It
Simple
Stupid!
2004
P 40